GNOME Bugzilla – Bug 158506
Nautilus crashed on simple folder click [fm_tree_model_unref_node]
Last modified: 2007-04-26 10:22:27 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-utils Severity: normal Version: GNOME2.8.0 2.8.1 Gnome-Distributor: Red Hat, Inc Synopsis: Nautilus crashed on simple folder click. Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Simply clicked on folder "filesystem". Nautilus had been running for hours. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151152960 (LWP 17085)] [New Thread -182309968 (LWP 27253)] [Thread debugging using libthread_db enabled] [New Thread -151152960 (LWP 17085)] [New Thread -182309968 (LWP 27253)] [Thread debugging using libthread_db enabled] [New Thread -151152960 (LWP 17085)] [New Thread -182309968 (LWP 27253)] [New Thread -171414608 (LWP 25091)] [New Thread -170939472 (LWP 25062)] [New Thread -164529232 (LWP 17174)] [New Thread -164262992 (LWP 17173)] [New Thread -153760848 (LWP 17142)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x008017a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52083
Thread 7 (Thread -153760848 (LWP 17142))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-16 16:28 ------- Unknown version 2.8.1 in product gnome-utils. Setting version to "2.8.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was rchimera@vcommerce.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace, according to the simple-dup-finder. Moving to nautilus, where it belongs.
I think this is the 2.8 version of bug 146297. *** This bug has been marked as a duplicate of 146297 ***
On second thoughts, I'm not sure about it being the same bug. So please file exact dups here, not at bug 146297.
*** Bug 161440 has been marked as a duplicate of this bug. ***
*** Bug 165767 has been marked as a duplicate of this bug. ***
*** Bug 167891 has been marked as a duplicate of this bug. ***
Plenty of dups, reopening.
*** Bug 171907 has been marked as a duplicate of this bug. ***
*** Bug 172402 has been marked as a duplicate of this bug. ***
*** Bug 163998 has been marked as a duplicate of this bug. ***
*** Bug 300008 has been marked as a duplicate of this bug. ***
*** Bug 301408 has been marked as a duplicate of this bug. ***
*** Bug 301899 has been marked as a duplicate of this bug. ***
*** Bug 308327 has been marked as a duplicate of this bug. ***
*** Bug 304853 has been marked as a duplicate of this bug. ***
a comment on #145789 has a backtrace matching this bug:
+ Trace 61517
Thread 6 (Thread 1082132832 (LWP 7329))
*** Bug 310511 has been marked as a duplicate of this bug. ***
The last dup is 2.10.1 , adjusting version field
*** Bug 313334 has been marked as a duplicate of this bug. ***
It just happened for me : unfortunatly I've no bt , just this messages : (nautilus:11033): Gtk-CRITICAL **: file gtktreeview.c: line 3871 (gtk_tree_view_bin_expose): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. ** ERROR **: file fm-tree-model.c: line 1508 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0) aborting...
*** Bug 315857 has been marked as a duplicate of this bug. ***
Comments from bug 315857 "While using nautilus (when copying files or when viewing a directory with avi in it or when closing a nautilus window) sometimes it segfaults.." "ah, i'm using nautilus in "browse" mode." Should we bump the version on this since people with 2.12 are still seeing the crash?
Yes. And given the number of dups, make this a stopper for 2.12.1.
*** Bug 316374 has been marked as a duplicate of this bug. ***
*** Bug 316629 has been marked as a duplicate of this bug. ***
Ubuntu bugzilla has a similar bug opened: http://bugzilla.ubuntu.com/show_bug.cgi?id=15651 "Description of the crash: Nautilus not the active window. Closed a window in Firefox and was given a message that Nautilus has closed/crashed. It is not possible to re-create the crash with any consistency. It seems to happen randomly under different circumstances, but in all cases Nautilus is not the active window. How often does this happen? Intermittently, several times a day ... > Thanks for the backtrace. That seems to be the same bug as http://bugzilla.gnome.org/show_bug.cgi?id=158506. Can you get an another one with libglib2-0-dbg and libgtk2.0-0-dbg the packages installed? Could also run nautilus from a command line with "gnome-session-remove nautilus && nautilus" and not the assertion printed? ... OK. Installed that additional dbg packages you suggested. Running from command-line as suggested. The crash produces the following: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1225414976 (LWP 7051)] [New Thread -1236071504 (LWP 7058)] [New Thread -1235805264 (LWP 7057)] [New Thread -1235539024 (LWP 7056)] [New Thread -1235272784 (LWP 7055)] [New Thread -1235006544 (LWP 7054)] [New Thread -1234089040 (LWP 7053)] [New Thread -1227244624 (LWP 7052)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63084
Thread 8 (Thread -1227244624 (LWP 7052))
If you need any other information the bug submitter is responsive
another ubuntu user has the same issue, let me know if there some other information are required on the topic
I just have a crash with nautilus (garnome 2.10.2) My bt seems related to this bug BACKTRACE : Using host libthread_db library "/lib/tls/libthread_db.so.1". Core was generated by `/opt/STools/gnome-2.10/bin/nautilus'.
+ Trace 63115
Thread 15 (process 5015)
*** Bug 316887 has been marked as a duplicate of this bug. ***
Clearly there is some sort of double unref of one of the rows in the tree sidebar. It would be interesting to hear what this was showing during the crash.
Alex: I could imagine that this is related to bug 123051. Maybe the internal GTK+ code made assumptions on the models that made it not repick a row, since it sorting results.
"it sorting results" should have been "it expected particular sorting results".
*** Bug 318221 has been marked as a duplicate of this bug. ***
*** Bug 318232 has been marked as a duplicate of this bug. ***
Created attachment 53449 [details] Nautilus screenshot while crashing screenshot related to #30 : "It would be interesting to hear what this was showing during the crash"
I applied the patch from bug 123051 (the dummy row one) but unfortunatly I still have the crash (but less often than before having applied it). This is 2.10 but I post anyway as informational purpose. (nautilus:18837): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `GTK_TREE_MODEL_SORT (tree_model)->stamp == iter->stamp' failed ** ERROR **: file fm-tree-model.c: line 1512 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0) aborting... BACKTRACE : Using host libthread_db library "/lib/tls/libthread_db.so.1". Core was generated by `/opt/STools/gnome-2.10/bin/nautilus'.
+ Trace 63646
Thread 10 (process 18837)
*** Bug 319802 has been marked as a duplicate of this bug. ***
*** Bug 320671 has been marked as a duplicate of this bug. ***
*** Bug 320712 has been marked as a duplicate of this bug. ***
*** Bug 320698 has been marked as a duplicate of this bug. ***
*** Bug 320653 has been marked as a duplicate of this bug. ***
*** Bug 319920 has been marked as a duplicate of this bug. ***
*** Bug 319907 has been marked as a duplicate of this bug. ***
*** Bug 319825 has been marked as a duplicate of this bug. ***
*** Bug 319589 has been marked as a duplicate of this bug. ***
We need to come up with a reproducible test case for this one and get it fixed before our next stable release.
Finally I found it: 2005-11-08 Martin Wehner <martin.wehner@gmail.com> * src/file-manager/fm-tree-view.c: (create_tree): Connect the compare function before root nodes are added. Prevents the internal sort model of GtkTree from going out of sync with the tree view after a root node resort. Fixes #158506. You can reproduce it almost 100% by expanding a root node (one that will get a different position after the reordering) and then changing the theme.
Thanks for tracking this down Martin! You rock! :) I wonder whether there is another GTK+ bug involved, though. Shouldn't the model be resorted instantly after setting a sort function, thus avoiding that the model is out of sync?
Yes! Good stuff Martin!
*** Bug 321477 has been marked as a duplicate of this bug. ***
*** Bug 321566 has been marked as a duplicate of this bug. ***
*** Bug 322123 has been marked as a duplicate of this bug. ***
*** Bug 322450 has been marked as a duplicate of this bug. ***
Just thought I'd add some observations to this issue seeing as it is happening quite often. I'm running Ubuntu 5.10 on a Dell Inspiron 1100 w/750MB, 80GB HD, dual boot with WXPHm on NTFS, 2 FAT32 parts and Linux on an extended 4th part. Nautilus version is 2.12.1 here. -Change the "open with" property of a JPEG file residing on a FAT32 partition crashes the program. -Tried this on a CSV file on the linux partition and the sidebar tree view crashes, bringing down the whole program. -The change to the "open with" property seems to stick, though. -Selecting "close" results in a restart of nautilus. I thought it should just stay closed. -This is absolutely reproducable. It happens every time I try it with the side pane open in tree view. -Closing the side pane prior to changing the "open with" property and re-opening it afterwards seems to circumvent the crash. HTH, Alex Janssen alex@ourwoods.org
*** Bug 323152 has been marked as a duplicate of this bug. ***
*** Bug 325303 has been marked as a duplicate of this bug. ***
*** Bug 332449 has been marked as a duplicate of this bug. ***
*** Bug 332801 has been marked as a duplicate of this bug. ***
*** Bug 332824 has been marked as a duplicate of this bug. ***
*** Bug 334089 has been marked as a duplicate of this bug. ***
*** Bug 376352 has been marked as a duplicate of this bug. ***
*** Bug 433459 has been marked as a duplicate of this bug. ***