GNOME Bugzilla – Bug 517831
crash in Movie Player: Distribution: Fedora rel...
Last modified: 2008-02-21 16:40:13 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 195088384 vsize: 195088384 resident: 28618752 share: 13672448 rss: 28618752 rss_rlim: 4294967295 CPU usage: start_time: 1203589238 rtime: 105 utime: 80 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' (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 -1209076000 (LWP 2645)] [New Thread -1359168624 (LWP 2655)] [New Thread -1341834352 (LWP 2652)] [New Thread -1331344496 (LWP 2651)] [New Thread -1318966384 (LWP 2650)] [New Thread -1304376432 (LWP 2649)] [New Thread -1293886576 (LWP 2648)] [New Thread -1283396720 (LWP 2647)] [New Thread -1268667504 (LWP 2646)] (no debugging symbols found) 0x00ecf402 in __kernel_vsyscall ()
+ Trace 189954
Thread 2 (Thread -1359168624 (LWP 2655))
----------- .xsession-errors (30 sec old) --------------------- Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x340005b (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: last_focus_time (998149757) is greater than comparison timestamp (998007125). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET Window manager warning: last_user_time (998149757) is greater than comparison timestamp (998007125). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ Window manager warning: 0xc00003 (Top Panel) appears to be one of the offending windows with a timestamp of 998059962. Working around... Window manager warning: 0xc0002a (Bottom Pan) appears to be one of the offending windows with a timestamp of 998149039. Working around... Window manager warning: 0x320001e (laxman@npj) appears to be one of the offending windows with a timestamp of 998149154. Working around... Window manager warning: 0x140001f (Desktop) appears to be one of the offending windows with a timestamp of 998062714. Working around... Window manager warning: 0x1400908 (laxman) appears to be one of the offending windows with a timestamp of 998065986. Working around... Window manager warning: 0x1400a59 (Documents) appears to be one of the offending windows with a timestamp of 998068218. Working around... Window manager warning: 0x340005b (Multimedia) appears to be one of the offending windows with a timestamp of 998149757. Working around... Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x340005b (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. closing gnome-mount 0.6 --------------------------------------------------
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 368224 ***