GNOME Bugzilla – Bug 486566
crash in Movie Player: I was watching a normal ...
Last modified: 2007-10-21 12:23:14 UTC
Version: 2.20.0 What were you doing when the application crashed? I was watching a normal dvd, I wanted to go forward so I moved the progress bar and the program crashed. Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22.9-slh-smp-1 #1 SMP PREEMPT Wed Sep 26 22:13:39 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 142352384 vsize: 142352384 resident: 61104128 share: 16605184 rss: 61104128 rss_rlim: 4294967295 CPU usage: start_time: 1192370681 rtime: 6050 utime: 5775 stime: 275 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c326b0 (LWP 28639)] [New Thread 0xb3485b90 (LWP 28687)] [New Thread 0xb2c85b90 (LWP 28686)] [New Thread 0xb3e85b90 (LWP 28683)] [New Thread 0xb5386b90 (LWP 28678)] [New Thread 0xb4b86b90 (LWP 28677)] [New Thread 0xb5d86b90 (LWP 28676)] [New Thread 0xb65e4b90 (LWP 28666)] 0xb7124a29 in __lll_mutex_lock_wait () from /lib/libpthread.so.0
+ Trace 170139
Thread 7 (Thread 0xb5d86b90 (LWP 28676))
----------- .xsession-errors (86 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 358891 ***