GNOME Bugzilla – Bug 535346
crash in Computer: Open a remote samba fold...
Last modified: 2008-05-28 22:50:23 UTC
Version: 2.20.0 What were you doing when the application crashed? Open a remote samba folder. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24.6 #5 SMP Sat May 17 19:06:48 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 67624960 vsize: 67624960 resident: 28381184 share: 16687104 rss: 28381184 rss_rlim: 4294967295 CPU usage: start_time: 1212006823 rtime: 133 utime: 123 stime: 10 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b5b720 (LWP 6813)] [New Thread 0xb55e2b90 (LWP 7206)] 0xb759af91 in waitpid () from /lib/libpthread.so.0
+ Trace 198904
Thread 1 (Thread 0xb6b5b720 (LWP 6813))
----------- .xsession-errors (614 sec old) --------------------- (rhythmbox:6871): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:6871): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %l (rhythmbox:6871): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %l (rhythmbox:6871): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:6871): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %l (rhythmbox:6871): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:6871): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %l ...Too much output, ignoring rest... --------------------------------------------------
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 522534 ***