GNOME Bugzilla – Bug 547195
crash in Movie Player: starting a wmv video and...
Last modified: 2008-08-16 11:29:50 UTC
Version: 2.22.2 What were you doing when the application crashed? starting a wmv video and switching to fullscreen, under awesome window manager. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 146038784 vsize: 146038784 resident: 52260864 share: 15249408 rss: 52260864 rss_rlim: 4294967295 CPU usage: start_time: 1218395848 rtime: 136 utime: 119 stime: 17 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [Thread debugging using libthread_db enabled] [New Thread 0xb7eeb720 (LWP 2925)] [New Thread 0xb0bffb90 (LWP 2934)] [New Thread 0xb3b73b90 (LWP 2933)] [New Thread 0xb451ab90 (LWP 2932)] [New Thread 0xb4dfeb90 (LWP 2931)] [New Thread 0xb55ffb90 (LWP 2930)] [New Thread 0xb5f91b90 (LWP 2929)] [New Thread 0xb6be3b90 (LWP 2928)] [New Thread 0xb7792b90 (LWP 2927)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 204955
----------- .xsession-errors (17539 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ...Too much output, ignoring rest... --------------------------------------------------
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 527572 ***