Bug 515121 – crash in Movie Player: trying to play a movie

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 515121 - crash in Movie Player: trying to play a movie


Summary:	crash in Movie Player: trying to play a movie


Status:	RESOLVED DUPLICATE of bug 508530

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-08 02:00 UTC by xdieyoung.saveyourselfx
Modified:	2008-02-08 07:07 UTC

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

Description xdieyoung.saveyourselfx 2008-02-08 02:00:24 UTC

Version: 2.20.3

What were you doing when the application crashed?
trying to play a movie


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

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: gnome

Memory status: size: 111833088 vsize: 111833088 resident: 36364288 share: 15159296 rss: 36364288 rss_rlim: 4294967295
CPU usage: start_time: 1202436084 rtime: 190 utime: 168 stime: 22 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c1d6c0 (LWP 2947)]
[New Thread 0xb24cdb90 (LWP 2958)]
[New Thread 0xb2cceb90 (LWP 2956)]
[New Thread 0xb34ebb90 (LWP 2955)]
[New Thread 0xb3ebeb90 (LWP 2954)]
[New Thread 0xb46bfb90 (LWP 2953)]
[New Thread 0xb5d11b90 (LWP 2952)]
[New Thread 0xb677db90 (LWP 2949)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 188488

Thread 6 (Thread 0xb46bfb90 (LWP 2953))

#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 g_logv
from /usr/lib/libglib-2.0.so.0
#7 g_log
from /usr/lib/libglib-2.0.so.0
#8 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/gstreamer-0.10/libgstffmpeg.so
#10 ??



----------- .xsession-errors (138719 sec old) ---------------------
/etc/gdm/Xsession: Beginning session setup...
/etc/X11/Xsession.d/40guidance-displayconfig_restore: line 11: /usr/bin/displayconfig-restore: No such file or directory
SESSION_MANAGER=local/nipples:/tmp/.ICE-unix/15181
xrdb:  "*Label.background" on line 220 overrides entry on line 150
xrdb:  "*Text.background" on line 226 overrides entry on line 191
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
Window manager warning: Failed to read saved session file /home/ash/.metacity/sessions/default0.ms: Failed to open file '/home/ash/.metacity/sessions/default0.ms': No such file or directory
Initializing gnome-mount extension
cannot connect at /usr/bin/remotewin line 5.
Window manager warning: Treating resize request of legacy application 0x24002f7 (WinXP [Run) as a fullscreen request
Executing C:\Program Files\Windows Live\Messenger\msnmsgr.exe...
Complete {C:\Program Files\Windows Live\Messenger\msnmsgr.exe
--------------------------------------------------

Comment 1 Philip Withnall 2008-02-08 07:07:59 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 508530 ***