GNOME Bugzilla – Bug 551452
crash in Computer: Bug report came just aft...
Last modified: 2008-09-09 12:10:42 UTC
Version: 2.22.5.1 What were you doing when the application crashed? Bug report came just after 551451. No more action done. Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.22.3 2008-09-02 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.24-gentoo-r8-v3 #3 SMP Sat Sep 6 14:39:32 CEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Gion Memory status: size: 347426816 vsize: 347426816 resident: 29839360 share: 15482880 rss: 29839360 rss_rlim: 18446744073709551615 CPU usage: start_time: 1220928639 rtime: 41 utime: 37 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b5fd28eb990 (LWP 28944)] [New Thread 0x41001950 (LWP 28950)] [New Thread 0x40800950 (LWP 28948)] 0x00002b5fcb2e9878 in __lll_mutex_lock_wait () from /lib/libpthread.so.0
+ Trace 206522
Thread 3 (Thread 0x40800950 (LWP 28948))
----------- .xsession-errors --------------------- seahorse nautilus module initialized (nautilus:28838): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed Initializing nautilus-open-terminal extension seahorse nautilus module initialized (nautilus:28856): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed Initializing nautilus-open-terminal extension seahorse nautilus module initialized (nautilus:28871): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed Initializing nautilus-open-terminal extension seahorse nautilus module initialized (nautilus:28944): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed --------------------------------------------------
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 526868 ***