Bug 498860 – crash in Movie Player:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 498860 - crash in Movie Player:


Summary:	crash in Movie Player:


Status:	RESOLVED DUPLICATE of bug 449658

Product:	totem
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	General Totem maintainer(s)
QA Contact:	General Totem maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-21 22:50 UTC by robert
Modified:	2007-11-22 07:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description robert 2007-11-21 22:50:37 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 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: 131284992 vsize: 131284992 resident: 24670208 share: 13643776 rss: 24670208 rss_rlim: 4294967295
CPU usage: start_time: 1195685423 rtime: 170 utime: 146 stime: 24 cutime:0 cstime: 1 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 0xb6e266b0 (LWP 3545)]
[New Thread 0xb2876b90 (LWP 3556)]
[New Thread 0xb3076b90 (LWP 3555)]
[New Thread 0xb3a43b90 (LWP 3554)]
[New Thread 0xb462cb90 (LWP 3551)]
[New Thread 0xb4e2cb90 (LWP 3550)]
[New Thread 0xb56acb90 (LWP 3547)]
[New Thread 0xb66c8b90 (LWP 3546)]
(no debugging symbols found)
0xb724e6c2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0

+ Trace 179176

Thread 3 (Thread 0xb3076b90 (LWP 3555))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 __assert_fail
from /lib/libc.so.6
#8 pa_mutex_unlock
from /usr/lib/libpulse.so.0
#9 pa_threaded_mainloop_unlock
from /usr/lib/libpulse.so.0
#10 ??
from /usr/lib/xine/plugins/1.1.8/xineplug_ao_out_pulseaudio.so
#11 ??
#12 ??
from /usr/lib/xine/plugins/1.1.8/xineplug_ao_out_pulseaudio.so
#13 ??
#14 ??



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Unknown parameter encountered: "SO_RCVBUF"
Ignoring unknown parameter "SO_RCVBUF"
jack init_class returning 0x88894f0
sh: jackd: command not found
sh: jackd: command not found
open_jack_plugin: Error: Failed to connect to JACK server
open_jack_plugin: (did you start 'jackd' server?)
totem: pulsecore/mutex-posix.c:81: pa_mutex_unlock: Assertion `_r == 0' failed.
--------------------------------------------------

Comment 1 Philip Withnall 2007-11-22 07:31:11 UTC

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 ***