1.7.2git-dbbfa326 I've had crashes giving different end results when right clicking on files owned by root. I can successfully right click on some - example files in /etc Right click on anything in /dev and it crashes. I tried running it through gdb: first time - everything hung and in the end had to reisub ... Second time - gdb gave me very little: Starting program: /usr/bin/thunar [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffec80c700 (LWP 1775)] [New Thread 0x7fffe7fff700 (LWP 1776)] [New Thread 0x7fffe7520700 (LWP 1787)] [Thread 0x7fffe7fff700 (LWP 1776) exited] [Thread 0x7fffec80c700 (LWP 1775) exited] [Thread 0x7ffff7fb1280 (LWP 1771) exited] [Inferior 1 (process 1771) exited normally] (gdb) backtrace full No stack. (gdb) info registers The program has no registers now. (gdb) x/16i $pc No registers. (gdb) thread apply all backtrace (gdb) quit I do have a large crash file from Xubuntu - that appears to have a stack trace at least - however as it's 2.8Mb - I can't attach it (hence the e-mail)
additional information: just tried again - this time I get this popup
Created attachment 7717 crash popup
Humm, for me files in /dev work fine .. just some items are grayed out, like it is supposed to be. Just a long-shot: Which thunar-plugins did you install ? ( I quess a plugin could be the cause, since plugins can contribute to the context-menu ) A screenshot of the context menu on some file from /etc possibly could help. ... will now check if I can get out something from this .crash file
Created attachment 7718 context menu Didn't specifically install any plugins. To be honest I didn't know you could ... Ran autogen Additional Plugins: * Advanced Properties: yes * Simple Builtin Renamers: yes * Trash Panel Applet: yes * User Customizable Actions: yes * Wallpaper support: yes Did screenshot right click on a folder - includes all I see. However, I'd not waste too much time - I can no longer replicate the issue :(
Thanks! Nothing suspicious :( "open folder as root" and "open file as root" probably are user custom actions, should have no impact I think. Ok, not that easy to use this .crash file. According to https://stackoverflow.com/questions/22418508/how-can-i-read-a-crash-file-on-ubuntu-12-04 I need to call "apport-unpack" to get the core-dump out of it. However it looks like that's not available for my distro (debian) On top, this answer claims that the coredump is not inside the .crash file, but somewhere else https://serverfault.com/a/873673 ( however IMO the size of 2.6 MB pretty much could be a zipped coredump ) If you are willing to further check for the cause, possibly you could take a try to debug it yourself: 1) Somehow get the coredump out of that .crash file E.g. apport-unpack _usr_bin_thunar.1000.crash 2) Use gdb on it: gdb <program> <core> E.g. gdb /path/to/thunar/thunar/.libs/thunar _usr_bin_thunar.1000.core Than you should be able to call "backtrace full"
Can't reproduce either. Please tell us the output of: find /usr/lib/thunarx-3/*.so -exec ldd {} + | grep "thunar\|gtk"
Created attachment 7719 backtrace attached find: ‘/usr/lib/thunarx-3/*.so’: No such file or directory
Great, you got the coredump! I hope you ares still motivated ;) In order to get a meaningful stacktrace(instead of just memory addresses), you need to compile thunar with debug-symbols: ./autogen.sh --enable-debug make ... and than gdb <program> <core> again
As reported by flocculant at #xfce-dev, he can't reproduce the crash anymore. Let's close the bug, but reopen if you (flocculant) are able to reproduce it again.