GNOME Bugzilla – Bug 515026
crash in Home Folder:
Last modified: 2008-02-07 19:03:29 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 73146368 vsize: 73146368 resident: 23597056 share: 15888384 rss: 23597056 rss_rlim: 4294967295 CPU usage: start_time: 1202403581 rtime: 248 utime: 224 stime: 24 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c086c0 (LWP 15327)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 188439
Thread 1 (Thread 0xb6c086c0 (LWP 15327))
----------- .xsession-errors (11 sec old) --------------------- (epiphany-browser:11410): libgnomevfs-WARNING **: Failed to create service browser: Bad state Autoselected keyboard map pt-br WARNING: Remote desktop does not support colour depth 24; falling back to 8 WARNING: No translation for (keysym 0xfe0a, ISO_Prev_Group) /usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking disconnect: Server idle timeout reached. (nautilus:3133): Eel-WARNING **: No extension, not implemented yet (nautilus:3133): Eel-WARNING **: No extension, not implemented yet seahorse nautilus module initialized Initializing gnome-mount extension (nautilus:15327): 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 ***