GNOME Bugzilla – Bug 515769
crash in Open Folder: Nautilus crash when I cl...
Last modified: 2008-02-11 17:53:46 UTC
Version: 2.21.90 What were you doing when the application crashed? Nautilus crash when I close a folder Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.21.90 2008-01-29 (Ubuntu) BugBuddy Version: 2.21.90 System: Linux 2.6.24-7-generic #1 SMP Thu Feb 7 01:29:58 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Aurora-looks Icon Theme: nuoveXT.2.2 Memory status: size: 128901120 vsize: 128901120 resident: 44773376 share: 24739840 rss: 44773376 rss_rlim: 4294967295 CPU usage: start_time: 1202729622 rtime: 3537 utime: 2424 stime: 1113 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ab86c0 (LWP 5750)] (no debugging symbols found) 0xb7f58410 in __kernel_vsyscall ()
+ Trace 188823
Thread 1 (Thread 0xb6ab86c0 (LWP 5750))
----------- .xsession-errors (7 sec old) --------------------- (nautilus:5750): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (nautilus:5750): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (nautilus:5750): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (nautilus:5750): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (nautilus:5750): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed (nautilus:5750): GLib-CRITICAL **: g_utf8_collate: assertion `str1 != NULL' failed Window manager warning: Received a _NET_WM_MOVERESIZE message for 0xc03485 (narcis - F); these messages lack timestamps and therefore suck. ** ** ERROR:(fm-tree-model.c:1563):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_ref_count > 0) --------------------------------------------------
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 512040 ***