Bug 499704 – 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 499704 - 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-26 10:24 UTC by martino.pani
Modified:	2007-11-26 19:58 UTC

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

Description martino.pani 2007-11-26 10:24:23 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Industrial

Memory status: size: 146497536 vsize: 146497536 resident: 35028992 share: 15163392 rss: 35028992 rss_rlim: 4294967295
CPU usage: start_time: 1196073465 rtime: 170 utime: 156 stime: 14 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 0xb6e53970 (LWP 3853)]
[New Thread 0xb1839b90 (LWP 3865)]
[New Thread 0xb2417b90 (LWP 3864)]
[New Thread 0xb2c17b90 (LWP 3863)]
[New Thread 0xb35e4b90 (LWP 3862)]
[New Thread 0xb41cdb90 (LWP 3861)]
[New Thread 0xb4a0fb90 (LWP 3860)]
[New Thread 0xb527eb90 (LWP 3855)]
[New Thread 0xb62aab90 (LWP 3854)]
(no debugging symbols found)
0xb711052d in poll () from /lib/libc.so.6

+ Trace 179670

Thread 4 (Thread 0xb2c17b90 (LWP 3863))

#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: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x280001a (Archive Ma)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
jack init_class returning 0x8813ae0
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.
Failed to read a valid object file image from memory.
--------------------------------------------------

Comment 1 Philip Withnall 2007-11-26 19:58:32 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 ***