Bug 516582 – crash in Movie Player: was trying to open an in...

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 516582 - crash in Movie Player: was trying to open an in...


Summary:	crash in Movie Player: was trying to open an in...


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:	2008-02-14 23:48 UTC by gerano
Modified:	2008-02-14 23:49 UTC

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

Description gerano 2008-02-14 23:48:39 UTC

Version: 2.20.3

What were you doing when the application crashed?
was trying to open an incomplete video (compiz runnig)


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24.2 #1 SMP Mon Feb 11 19:17:19 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: UbuntuStudio-Feisty

Memory status: size: 145092608 vsize: 145092608 resident: 28123136 share: 14409728 rss: 28123136 rss_rlim: 4294967295
CPU usage: start_time: 1203032769 rtime: 64 utime: 54 stime: 10 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 0xb6e756b0 (LWP 8458)]
[New Thread 0xb2274b90 (LWP 8470)]
[New Thread 0xb2a75b90 (LWP 8469)]
[New Thread 0xb3443b90 (LWP 8468)]
[New Thread 0xb402db90 (LWP 8467)]
[New Thread 0xb482eb90 (LWP 8466)]
[New Thread 0xb5088b90 (LWP 8465)]
[New Thread 0xb60e4b90 (LWP 8464)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 189251

Thread 3 (Thread 0xb2a75b90 (LWP 8469))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 __assert_fail
from /lib/i686/cmov/libc.so.6
#10 ??
from /usr/lib/libpulse.so.0
#11 ??
from /usr/lib/libpulse.so.0
#12 ??
from /usr/lib/libpulse.so.0
#13 ??
#14 ??
from /usr/lib/libpulse.so.0
#15 ??
#16 ??
from /usr/lib/libpulse.so.0
#17 ??
#18 pa_threaded_mainloop_unlock
from /usr/lib/libpulse.so.0

Comment 1 Philip Withnall 2008-02-14 23:49:42 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 ***