GNOME Bugzilla – Bug 756342
Crash after opening Preferences when Other Locations is opened
Last modified: 2016-11-17 20:06:17 UTC
OS: Arch Linux, Linux 4.2.2 64bit Gnome Files 3.18.0 Steps to reproduce: 1) Open Nautilus window 2) Choose "Other Locations" in left column and click on it 3) Open the application menu by clicking on "Files" in Gnome top bar 4) Choose "Preferences" from the application menu -> Crash. I don't know how to compile Nautilus with debugging symbols, so the gdb output is not detailed. ---- Reading symbols from nautilus...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffe8527700 (LWP 15741)] [New Thread 0x7fffe7d26700 (LWP 15742)] [New Thread 0x7fffe5df3700 (LWP 15743)] [New Thread 0x7fffe53e5700 (LWP 15744)] [New Thread 0x7fffd6897700 (LWP 15746)] [New Thread 0x7fffd563d700 (LWP 15747)] [Thread 0x7fffd563d700 (LWP 15747) exited] [Thread 0x7fffd6897700 (LWP 15746) exited] ** ERROR:nautilus-file.c:6984:nautilus_file_is_in_trash: assertion failed: (NAUTILUS_IS_FILE (file)) Program received signal SIGABRT, Aborted. 0x00007ffff41725f8 in raise () from /usr/lib/libc.so.6
fixed in 3.18.2
@Carlos, your fix seems to not be enough, the Ubuntu bug trackers is receiving similar issues from 3.18.2 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1524008 "#0 0x00007fb35ddbb227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 resultvar = 0 pid = 3374 selftid = 3374
+ Trace 235799
Sebastien, can you reproduce it personally? can you reproduce not using templates or any plugin? Thanks
I was able to reproduce once yesterday, I don't use templates but I have some of the standard plugin installed (e.g gnome-user-share), I'm going to try without those but since I can't easily reproduce I'm unsure if that's going to work. What other info do you need if I manage to reproduce?
No other info is required. If you can reproduce with the code living in nautilus alone, it's more than enough (also I guess you are using the desktop right?) This problem happens when a view is leaked, then when requesting preferences it goes through all the views, and tries to access one that has invalid data. Afaik the only one currently that has ownership of the view is the window-slot, (templates menu items were also having it, which is what I fixed in 3.18 branch for 3.18.3).
Ok, do you plan to roll a 3.18.3 tarball? The easiest way to test is probably to get the update out and see if we still get reports
(In reply to Sebastien Bacher from comment #6) > Ok, do you plan to roll a 3.18.3 tarball? The easiest way to test is > probably to get the update out and see if we still get reports yes, but later on since we want some other changes as well.
I see that 3.18.3 has eventually been released. Is that still an issue?
This seems to be fixed. I can't reproduce it anymore. (I'm running Nautilus 3.20.3 on Fedora 24.)