Bug 367374 – crash in Movie Player: Playing DVIX video

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 367374 - crash in Movie Player: Playing DVIX video


Summary:	crash in Movie Player: Playing DVIX video


Status:	RESOLVED DUPLICATE of bug 355793

Product:	totem
Classification:	Core
Component:	general
Version:	2.16.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:	2006-10-30 03:10 UTC by andraycho
Modified:	2006-10-30 11:27 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description andraycho 2006-10-30 03:10:35 UTC

Version: 2.16.2

What were you doing when the application crashed?
Playing DVIX video


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 50802688 vsize: 0 resident: 50802688 share: 0 rss: 16678912 rss_rlim: 0
CPU usage: start_time: 1162177750 rtime: 0 utime: 63 stime: 0 cutime:55 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225881936 (LWP 6816)]
[New Thread -1243702368 (LWP 6818)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 80209

Thread 1 (Thread -1225881936 (LWP 6816))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 bacon_video_widget_get_backend_name
#5 bacon_video_widget_dvd_event
#6 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#7 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 gtk_widget_realize
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_widget_set_parent
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_box_pack_start
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#18 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_container_add
from /usr/lib/libgtk-x11-2.0.so.0
#24 totem_action_exit
#25 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-30 11:27:02 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 355793 ***