GNOME Bugzilla – Bug 507448
crash in Home Folder: I made a screen shot , ...
Last modified: 2008-01-05 18:54:02 UTC
What were you doing when the application crashed? I made a screen shot , and I was going to open it: "screenshot.png" on desktop. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Gion Memory status: size: 87379968 vsize: 87379968 resident: 18432000 share: 10452992 rss: 18432000 rss_rlim: 4294967295 CPU usage: start_time: 1199511096 rtime: 2085 utime: 1924 stime: 161 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 0xb6e096b0 (LWP 4340)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 184145
Thread 1 (Thread 0xb6e096b0 (LWP 4340))
----------- .xsession-errors --------------------- Unrecognized number formatter: cjk-chinese-simp Unrecognized number formatter: cjk-chinese-simp Unrecognized number formatter: cjk-chinese-simp Unrecognized number formatter: cjk-chinese-simp fallback mode ** (gnome-screensaver-preferences:9964): DEBUG: Found best visual for GL: 0x27 ** Message: <info> 您现在已连接到有线网络。 窗口管理器警告:last_user_time (3079560067) is greater than comparison timestamp (1232705196). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE 窗口管理器警告:0x2600157 (Google Mai) appears to be one of the offending windows with a timestamp of 3079560067. Working around... ** Message: drive = 0 ** Message: volume = 0 Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... --------------------------------------------------
This bug has been fixed in Debian already. Please update nautilus to version 2.20. Thanks. *** This bug has been marked as a duplicate of 440988 ***