Bug 365262 – Totem crash when switching screen-resolution

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 365262 - Totem crash when switching screen-resolution


Summary:	Totem crash when switching screen-resolution


Status:	RESOLVED DUPLICATE of bug 355793

Product:	totem
Classification:	Core
Component:	general
Version:	1.4.x
Hardware:	Other other

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-26 12:59 UTC by Rene Majcen
Modified:	2006-10-26 13:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Rene Majcen 2006-10-26 12:58:14 UTC

Distribution: Debian testing/unstable
Package: totem
Severity: Normal
Version: GNOME2.14.3 1.4.5
Gnome-Distributor: Debian
Synopsis: Totem crash when switching screen-resolution
Bugzilla-Product: totem
Bugzilla-Component: general
Bugzilla-Version: 1.4.5
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Switching screen resolution from 1600x1200 to 1280x1024 or 1024x768 and
trying to play any video-file in totem, gxine or mplayer causes the
players to crash.


Steps to reproduce the crash:
1. Switch screen-resolution from 1600x1200 to 1280x1024 or 1024x768 (see
system configuration below)
2. play video file with totem, gxine or mplayer
3. watch them crash

Expected Results:
playing video-files in any screen-resolution w/o problems

How often does this happen?
always

Additional Information:
Debian GNU/Linux 2.6.16-2-686 testing

Xorg 7.0

fglrxinfo:
display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FIREGL T2e Pentium 4 (SSE2) (FireGL)
(GNU_ICD)
OpenGL version string: 2.0.6011 (8.28.8)


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1492269376 (LWP 4825)]
[New Thread -1506296912 (LWP 4830)]
[New Thread -1497023568 (LWP 4827)]
(no debugging symbols found)
0xa76c8201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 78425

Thread 1 (Thread -1492269376 (LWP 4825))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 bacon_video_widget_get_backend_name
#4 bacon_video_widget_dvd_event
#5 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#6 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#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_widget_realize
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_widget_set_parent
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_box_pack_start
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_box_pack_start_defaults
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 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#17 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_container_add
from /usr/lib/libgtk-x11-2.0.so.0
#23 totem_action_exit
#24 main
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0





------- Bug created by bug-buddy at 2006-10-26 12:59 -------


Unknown version 1.4.5 in product totem.  Setting version to "1.4.x".

Comment 1 Fabio Bonelli 2006-10-26 13:04:58 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 ***