Bug 519619 – 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 519619 - crash in Movie Player:


Summary:	crash in Movie Player:


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-29 20:41 UTC by cek
Modified:	2008-02-29 21:22 UTC

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

Description cek 2008-02-29 20:41:53 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-4-rt #1 SMP PREEMPT RT Mon Jan 14 19:42:34 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mac4Lin_GTK_v0.3
Icon Theme: Mac4Lin_Icons_v0.3a

Memory status: size: 117264384 vsize: 117264384 resident: 38387712 share: 15745024 rss: 38387712 rss_rlim: 4294967295
CPU usage: start_time: 1204317579 rtime: 182 utime: 164 stime: 18 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 0xb6cd06b0 (LWP 12514)]
[New Thread 0xb1bd7b90 (LWP 12526)]
[New Thread 0xb23d8b90 (LWP 12525)]
[New Thread 0xb2bf5b90 (LWP 12524)]
[New Thread 0xb3ccbb90 (LWP 12521)]
[New Thread 0xb44ffb90 (LWP 12520)]
[New Thread 0xb59bab90 (LWP 12519)]
[New Thread 0xb646fb90 (LWP 12516)]
(no debugging symbols found)
0xb7fd3410 in __kernel_vsyscall ()

+ Trace 190885

Thread 6 (Thread 0xb44ffb90 (LWP 12520))

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



----------- .xsession-errors (6 sec old) ---------------------
xscreensaver-command: activating and locking.
** (totem:12514): WARNING **: Invalid borders specified for theme pixmap:
        /home/c/.themes/Mac4Lin_GTK_v0.3/gtk-2.0/Frame-Gap/frame1.png,
borders don't fit within the image
JACK tmpdir identified as [/dev/shm]
** ERROR **: file gstffmpegdec.c: line 731 (gst_ffmpegdec_get_buffer): should not be reached
aborting...
JACK tmpdir identified as [/dev/shm]
** (totem:12514): WARNING **: Invalid borders specified for theme pixmap:
        /home/c/.themes/Mac4Lin_GTK_v0.3/gtk-2.0/Range/null.png,
borders don't fit within the image
--------------------------------------------------

Comment 1 Philip Withnall 2008-02-29 21:22:05 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 508530 ***