GNOME Bugzilla – Bug 551451
crash in Computer: % nautilus
Last modified: 2008-09-09 12:10:51 UTC
Version: 2.22.5.1 What were you doing when the application crashed? % nautilus 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: 413974528 vsize: 413974528 resident: 30060544 share: 15589376 rss: 30060544 rss_rlim: 18446744073709551615 CPU usage: start_time: 1220928475 rtime: 42 utime: 38 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b426794b990 (LWP 28890)] [New Thread 0x41001950 (LWP 28895)] [New Thread 0x40800950 (LWP 28894)] 0x00002b4260349878 in __lll_mutex_lock_wait () from /lib/libpthread.so.0
+ Trace 206521
Thread 2 (Thread 0x41001950 (LWP 28895))
----------- .xsession-errors (58 sec old) --------------------- seahorse nautilus module initialized (nautilus:28822): GLib-GIO-CRITICAL **: g_unix_mount_is_system_internal: assertion `mount_entry != NULL' failed Initializing nautilus-open-terminal extension 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 --------------------------------------------------
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 ***