GNOME Bugzilla – Bug 474634
crash in Volume Control: listening to mplayer, lo...
Last modified: 2007-09-08 11:24:22 UTC
Version: 2.18.0 What were you doing when the application crashed? listening to mplayer, loaded with a mp3 Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 41709568 vsize: 41709568 resident: 12165120 share: 9084928 rss: 12165120 rss_rlim: 4294967295 CPU usage: start_time: 1189190436 rtime: 916 utime: 777 stime: 139 cutime:4 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (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 -1208919824 (LWP 5773)] (no debugging symbols found) 0x00962402 in __kernel_vsyscall ()
+ Trace 161171
Thread 1 (Thread -1208919824 (LWP 5773))
----------- .xsession-errors (31 sec old) --------------------- ** Message: GetValue variable 2 (2) ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() Grabbing the mouse failed with "GrabInvalidTime" Window manager warning: last_focus_time (3786894695) is greater than comparison timestamp (3779695892). This most likely represents a buggy client sending inaccurate timestamps in messages such as _N Window manager warning: last_user_time (3786907281) is greater than comparison timestamp (3779695892). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE Window manager warning: 0xa00003 (Top Panel) appears to be one of the offending windows with a timestamp of 3786891005. Working around... Window manager warning: 0xa0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 3781935401. Working around... Window manager warning: 0x100001e (Desktop) appears to be one of the offending windows with a timestamp of 3783656288. Working around... Window manager warning: 0x2c007a6 (Calendar) appears to be one of the offending windows with a timestamp of 3786890106. Working around... Window manager warning: 0x320001e (tenchoster) appears to be one of the offending windows with a timestamp of 3786731680. Working around... Window manager warning: 0x1e00002 (PhishTank ) appears to be one of the offending windows with a timestamp of 3786401167. Working around... Window manager warning: 0x3800003 (Volume Con) appears to be one of the offending windows with a timestamp of 3786826923. Working around... Window manager warning: 0x3a00003 (Date/Time ) appears to be one of the offending windows with a timestamp of 3786907281. Working around... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 471133 ***