GNOME Bugzilla – Bug 464476
crash in System Log: Started shutdown from th...
Last modified: 2007-08-07 20:39:11 UTC
Version: 2.18.1 What were you doing when the application crashed? Started shutdown from the System sub menu Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 38313984 vsize: 38313984 resident: 20492288 share: 15388672 rss: 20492288 rss_rlim: 4294967295 CPU usage: start_time: 1186517636 rtime: 294 utime: 273 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1208256800 (LWP 3262)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 153560
Thread 1 (Thread -1208256800 (LWP 3262))
----------- .xsession-errors --------------------- Window manager warning: last_user_time (2315381378) is greater than comparison timestamp (1105781937). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE Window manager warning: 0xc0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 2314898406. Working around... Window manager warning: 0xe0001f (Desktop) appears to be one of the offending windows with a timestamp of 2315301982. Working around... Window manager warning: 0xc00274 (Right Expa) appears to be one of the offending windows with a timestamp of 2314872626. Working around... Window manager warning: 0xc00003 (Top Panel) appears to be one of the offending windows with a timestamp of 2315344146. Working around... Window manager warning: 0x3600003 (Date/Time ) appears to be one of the offending windows with a timestamp of 2315381378. Working around... Window manager warning: Window 0x360001f (BitScope D) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Window manager warning: Window 0x360087a (Open) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Window manager warning: Window 0x36002ea (Dso) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Window manager warning: Window 0x360101d (Open) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Window manager warning: Window 0x380001f (BitScope D) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Window manager warning: Window 0x380087a (Open) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Window manager warning: Window 0x38002ea (Dso) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Window manager warning: Window 0x3801054 (Open) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM. Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3124-730930117-1186517035 --active --geometry 80x24+166+123 --title root@localhost:~ --wor --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 421621 ***