GNOME Bugzilla – Bug 521225
crash in System Log: it did?
Last modified: 2008-08-25 10:50:08 UTC
Version: 2.18.1 What were you doing when the application crashed? it did? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-7.fc7xen #1 SMP Tue Feb 12 12:32:24 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 36401152 vsize: 36401152 resident: 18944000 share: 15355904 rss: 18944000 rss_rlim: 4294967295 CPU usage: start_time: 1204997253 rtime: 43 utime: 42 stime: 1 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208641824 (LWP 19662)] (no debugging symbols found) 0x005c2402 in __kernel_vsyscall ()
+ Trace 191771
Thread 1 (Thread -1208641824 (LWP 19662))
----------- .xsession-errors --------------------- [Thread-9] INFO org.apache.log4j.chainsaw.LoggingReceiver - Thread started [Thread-9] DEBUG org.apache.log4j.chainsaw.LoggingReceiver - Waiting for a connection [AWT-EventQueue-7] INFO org.apache.log4j.chainsaw.ExitAction - shutting down Window manager warning: last_user_time (136705480) is greater than comparison timestamp (2406254463). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0xa0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 136705480. Working around... Window manager warning: last_user_time (136705480) is greater than comparison timestamp (2406256176). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0xa0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 136705480. Working around... Window manager warning: 0x3800003 (Desktop Ba) appears to be one of the offending windows with a timestamp of 10485968. Working around... Window manager warning: last_user_time (136705480) is greater than comparison timestamp (2406257723). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0xa0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 136705480. Working around... Window manager warning: last_user_time (136705480) is greater than comparison timestamp (2406257724). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0xa0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 136705480. Working around... Window manager warning: last_user_time (102131274) is greater than comparison timestamp (2406260757). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: 0xa0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 102131274. Working around... Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-19665-918482318-1204997328 --active --geometry 80x24+218+60 --title root@kip:/etc --workin --------------------------------------------------
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 442846 ***