GNOME Bugzilla – Bug 518023
crash in Home Folder: change the locale ,form ...
Last modified: 2008-02-22 13:35:40 UTC
What were you doing when the application crashed? change the locale ,form zh_CN.GBK to zh_CN.UTF-8 Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 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: 112603136 vsize: 112603136 resident: 27836416 share: 18235392 rss: 27836416 rss_rlim: 4294967295 CPU usage: start_time: 1203668878 rtime: 294 utime: 282 stime: 12 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 0xb6be86c0 (LWP 8006)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 190063
Thread 1 (Thread 0xb6be86c0 (LWP 8006))
----------- .xsession-errors --------------------- SCIM has been successfully launched. SESSION_MANAGER=local/joecen:/tmp/.ICE-unix/7649 xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 窗口管理器警告:无法读取保存的会话文件 /home/joe/.metacity/sessions/default0.ms:Failed to open file '/home/joe/.metacity/sessions/default0.ms': 没有那个文件或目录 Initializing gnome-mount extension (nautilus:7737): Eel-WARNING **: No extension, not implemented yet Initializing gnome-mount extension (nautilus:8006): Eel-WARNING **: No extension, not implemented yet (nautilus:8006): 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 ***