GNOME Bugzilla – Bug 462226
crash in Movie Player: model preview
Last modified: 2007-07-31 18:50:27 UTC
Version: 2.18.2 What were you doing when the application crashed? model preview Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21.3-alfroid #5 Thu Jun 7 12:19:24 BST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 146219008 vsize: 146219008 resident: 34246656 share: 13398016 rss: 34246656 rss_rlim: 4294967295 CPU usage: start_time: 1185903366 rtime: 386 utime: 363 stime: 23 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/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225852720 (LWP 11003)] [New Thread -1320227952 (LWP 11018)] [New Thread -1304724592 (LWP 11017)] [New Thread -1296331888 (LWP 11016)] [New Thread -1286050928 (LWP 11015)] [New Thread -1273558128 (LWP 11014)] [New Thread -1265165424 (LWP 11013)] [New Thread -1256371312 (LWP 11012)] [New Thread -1239852144 (LWP 11011)] (no debugging symbols found) 0xb7f0b410 in __kernel_vsyscall ()
+ Trace 151883
Thread 4 (Thread -1296331888 (LWP 11016))
----------- .xsession-errors --------------------- ** 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 totem: pulsecore/mutex-posix.c:81: pa_mutex_unlock: Assertion `_r == 0' failed. Previous frame inner to this frame (corrupt stack?) totem: pulsecore/mutex-posix.c:81: pa_mutex_unlock: Assertion `_r == 0' failed. Previous frame inner to this frame (corrupt stack?) --------------------------------------------------
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 449658 ***