GNOME Bugzilla – Bug 447567
crash in Open Folder: Closing Nautilus connect...
Last modified: 2007-06-23 11:37:50 UTC
Version: 2.18.1 What were you doing when the application crashed? Closing Nautilus connected to Windows share. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 511053824 vsize: 511053824 resident: 42119168 share: 19644416 rss: 42119168 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181831607 rtime: 7104 utime: 3558 stime: 3546 cutime:0 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912697156272 (LWP 2651)] (no debugging symbols found) 0x00002aaab0e9c89f in waitpid () from /lib64/libpthread.so.0
+ Trace 140958
Thread 1 (Thread 46912697156272 (LWP 2651))
----------- .xsession-errors (6 sec old) --------------------- connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! ** (nautilus:2651): WARNING **: No description found for mime type "x-directory/smb-share" (file is "aboris"), please tell the gnome-vfs mailing list. (gnome-terminal:3394): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (nautilus:2651): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed ** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0) aborting... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
I installed the suggested packages. If the crash happens again, the information will now be available for me to post.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 444717 ***