Bug 519839 – 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 519839 - 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:	2008-03-02 02:44 UTC by Daniel Dickinson
Modified:	2008-03-02 12:40 UTC

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

Description Daniel Dickinson 2008-03-02 02:44:28 UTC

Version: 2.20.3

What were you doing when the application crashed?



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

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 154087424 vsize: 154087424 resident: 33648640 share: 15880192 rss: 33648640 rss_rlim: 4294967295
CPU usage: start_time: 1204425831 rtime: 241 utime: 211 stime: 30 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 0xb6e866b0 (LWP 14932)]
[New Thread 0xb225db90 (LWP 14941)]
[New Thread 0xb2a5eb90 (LWP 14940)]
[New Thread 0xb342cb90 (LWP 14939)]
[New Thread 0xb4016b90 (LWP 14938)]
[New Thread 0xb4817b90 (LWP 14937)]
[New Thread 0xb5073b90 (LWP 14936)]
[New Thread 0xb6129b90 (LWP 14935)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 191010

Thread 3 (Thread 0xb2a5eb90 (LWP 14940))

#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



----------- .xsession-errors (271135 sec old) ---------------------
** (gnome-cups-add:28712): WARNING **: Two ppds have driver == 'hpijs - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-LaserJet_3300_MFP-hpijs.ppd (HP LaserJet 3300 MFP Foomatic/hpijs - HPLIP 2.7.10[0]) and
	->hpijs/HP/HP-LaserJet_3300_MFP-hpijs.ppd (HP LaserJet 3300 MFP Foomatic/hpijs - HPLIP 2.7.10)[0]

** (gnome-cups-add:28712): WARNING **: Two ppds have driver == 'hpijs - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-LaserJet_3310_MFP-hpijs.ppd (HP LaserJet 3310 MFP Foomatic/hpijs - HPLIP 2.7.10[0]) and
	->hpijs/HP/HP-LaserJet_3310_MFP-hpijs.ppd (HP LaserJet 3310 MFP Foomatic/hpijs - HPLIP 2.7.10)[0]

** (gnome-cups-add:28712): WARNING **: Two ppds have driver == 'hpijs - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-LaserJet_3320_MFP-hpijs.ppd (HP LaserJet 3320 MFP Foomatic/hpijs - HPLIP 2.7.10[0]) and
	->hpijs/HP/HP-LaserJet_3320_MFP-hpijs.ppd (HP LaserJet 3320 MFP Foomatic/hpijs - HPLIP 2.7.10)[0]

** (gnome-cups-add:28712): WARNING **: Two ppds have driver == 'hpijs - HPLIP 2.7.10'
	->lsb/usr/hpijs/HP/HP-LaserJet_3320N_MFP-hpijs.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Philip Withnall 2008-03-02 12:40:06 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 ***