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


Summary:	crash in Movie Player:


Status:	RESOLVED DUPLICATE of bug 417969

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:

Duplicates:	394722 446186 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-13 13:13 UTC by levi
Modified:	2007-06-12 02:25 UTC

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

Description levi 2006-12-13 13:13:37 UTC

Version: 2.16.4

What were you doing when the application crashed?



Distribution: Gentoo Base System version 1.12.7
Gnome Release: 2.16.2 2006-12-12 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 228872192 vsize: 228872192 resident: 31305728 share: 16171008 rss: 31305728 rss_rlim: -1
CPU usage: start_time: 1166015578 rtime: 99 utime: 87 stime: 12 cutime:7 cstime: 2 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 47368760787824 (LWP 12334)]
[New Thread 1090525504 (LWP 12337)]
0x00002b14e482ab9a in waitpid () from /lib/libpthread.so.0

+ Trace 93817

Thread 1 (Thread 47368760787824 (LWP 12334))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 dbus_shutdown
from /usr/lib/libdbus-1.so.3
#6 dbus_watch_handle
from /usr/lib/libdbus-1.so.3
#7 dbus_message_new_method_call
from /usr/lib/libdbus-1.so.3
#8 libhal_device_get_property_bool
from /usr/lib/libhal.so.1
#9 totem_cd_detect_type_with_url
from /usr/lib/libtotem-plparser.so.1
#10 totem_action_open_dialog
#11 totem_action_play_media_device
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_has_handler_pending
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_marshal_VOID__UINT_STRING
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_has_handler_pending
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#27 gdk_event_get_graphics_expose
from /usr/lib/libgdk-x11-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_acquire
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 waitpid
from /lib/libpthread.so.0

Comment 1 palfrey 2006-12-13 21:35:31 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Bruno Boaventura 2007-01-14 13:11:02 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 3 Philip Withnall 2007-02-14 14:28:02 UTC

*** Bug 394722 has been marked as a duplicate of this bug. ***

Comment 4 Philip Withnall 2007-05-13 17:10:42 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 417969 ***

Comment 5 Pedro Villavicencio 2007-06-12 02:25:16 UTC

*** Bug 446186 has been marked as a duplicate of this bug. ***