GNOME Bugzilla – Bug 510391
crash in Home Folder: Renaming a file on Deskt...
Last modified: 2008-01-18 15:34:17 UTC
What were you doing when the application crashed? Renaming a file on Desktop to a name with spaces and an apostrophe (') Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.20.4 #2 Tue Jan 8 21:15:30 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 116113408 vsize: 116113408 resident: 29470720 share: 14753792 rss: 29470720 rss_rlim: 4294967295 CPU usage: start_time: 1200662882 rtime: 329 utime: 306 stime: 23 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 0xb6e2f6b0 (LWP 3405)] [New Thread 0xb2ab7b90 (LWP 5398)] [New Thread 0xb4668b90 (LWP 5397)] [New Thread 0xb5668b90 (LWP 5396)] [New Thread 0xb5e68b90 (LWP 5395)] [New Thread 0xb6668b90 (LWP 5394)] [New Thread 0xb4e68b90 (LWP 5393)] (no debugging symbols found) 0xb7684321 in waitpid () from /lib/libpthread.so.0
+ Trace 185821
Thread 1 (Thread 0xb6e2f6b0 (LWP 3405))
----------- .xsession-errors --------------------- (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files get tim imap://tim@localhost/ Find Items 0 get daemon imap://daemon@localhost/ Find Items 0 (totem:5311): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (totem:5311): Gdk-WARNING **: locale not supported by C library (bug-buddy:5405): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (bug-buddy:5405): Gdk-WARNING **: locale not supported by C library --------------------------------------------------
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 ***