GNOME Bugzilla – Bug 527699
crash in File Browser: selected "open as..." fr...
Last modified: 2008-04-13 09:40:45 UTC
Version: 2.20.0 What were you doing when the application crashed? selected "open as..." from right button menu Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-core #1 SMP PREEMPT Thu Mar 20 21:33:00 GMT 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Mac_OS_X_Leopard_for_Debian_v1.4 Memory status: size: 405692416 vsize: 405692416 resident: 29790208 share: 17125376 rss: 29790208 rss_rlim: 18446744073709551615 CPU usage: start_time: 1208009579 rtime: 102 utime: 90 stime: 12 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 0x2ac15c27dda0 (LWP 4817)] 0x00002ac155ac6edf in waitpid () from /lib/libpthread.so.0
+ Trace 195027
Thread 1 (Thread 0x2ac15c27dda0 (LWP 4817))
----------- .xsession-errors --------------------- gnome-mount 0.7 Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600021 (Riprodutto) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600021 (Riprodutto) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (nautilus:3334): Eel-WARNING **: No extension, not implemented yet Initializing gnome-mount extension seahorse nautilus module initialized (nautilus:4779): Eel-WARNING **: No extension, not implemented yet Initializing gnome-mount extension seahorse nautilus module initialized (nautilus:4817): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 355018 ***