Bug 370704 – crash in Movie Player: changing visulisation si...

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 370704 - crash in Movie Player: changing visulisation si...


Summary:	crash in Movie Player: changing visulisation si...


Status:	RESOLVED DUPLICATE of bug 351181

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-11-04 20:53 UTC by mark
Modified:	2006-11-05 19:38 UTC

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

Description mark 2006-11-04 20:53:50 UTC

Version: 2.16.2

What were you doing when the application crashed?
changing visulisation size to large from small


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

Memory status: size: 230723584 vsize: 230723584 resident: 29335552 share: 14127104 rss: 29335552 rss_rlim: -1
CPU usage: start_time: 1162673720 rtime: 129 utime: 117 stime: 12 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47500055545472 (LWP 13505)]
[New Thread 1132489040 (LWP 13519)]
[New Thread 1124096336 (LWP 13518)]
[New Thread 1115703632 (LWP 13517)]
[New Thread 1107310928 (LWP 13516)]
[New Thread 1098918224 (LWP 13515)]
[New Thread 1090525520 (LWP 13514)]
[New Thread 1082132816 (LWP 13513)]
(no debugging symbols found)
0x00002b3376b7ceef in waitpid () from /lib/libpthread.so.0

+ Trace 82933

Thread 1 (Thread 47500055545472 (LWP 13505))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 _x_config_init
from /usr/lib/libxine.so.1
#5 bacon_video_widget_set_video_device
#6 bacon_video_widget_set_visuals_quality
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 gtk_combo_new
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_combo_box_set_active_iter
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_combo_box_set_active_iter
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_menu_shell_append
from /usr/lib/libgtk-x11-2.0.so.0
#21 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#30 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#32 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#33 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#34 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-11-05 19:38:02 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 351181 ***