GNOME Bugzilla – Bug 743017
nautilus crashes in nautilus_window_sync_location_widgets when closing with >=2 tabs
Last modified: 2015-01-19 15:35:10 UTC
nautilus-3.14.2-1.fc21.x86_64 crashes (tested on two different systems (hw.)) when closing nautilus window with >=2 tabs. I tested this few times and it happened with every test, now it mostly crashes but not always (or there is something wrong with abrt ...) gtk3-3.14.6-1.fc21.x86_64 How to reproduce: Open nautilus window, open new tabs (from favorites (right click, "scroll_wheel_click", or right click/scroll_wheel_click on folder "Open in New Tab")) close nautilus window. GNU gdb (GDB) Fedora 7.8.1-36.fc21 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/nautilus...Reading symbols from /usr/lib/debug/usr/bin/nautilus.debug...done. done. [New LWP 2595] [New LWP 2603] [New LWP 3480] [New LWP 2604] [New LWP 2601] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/nautilus --gapplication-service'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 234557
Thread 1 (Thread 0x7f944f8cca00 (LWP 2595))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 741952 ***