Totem exits after a while in full screen

Bug #18983 reported by Sami Haahtinen on 2005-07-15
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Sebastien Bacher

Bug Description

Totem(-gstreamer) exits with code 1 after a while in full screen mode. This
appears to happen with all video files i have tried so far.

To reproduce:
1. open totem and a video file
2. Enter fullscreen mode (press F)
3. wait a while

I haven't yet verified if this is an upstream problem, gstreamer backend problem
or just ubuntu related in some other way.

Sebastien Bacher (seb128) wrote :

Thanks for your bug. How long is your while? Is that constant (ie: maybe the
screensaver usual running time)? What version of totem do you use?

Sami Haahtinen (ressu) wrote :

er, sorry. Forgot to include version number. The version where this bug appeared
is 1.1.3 (currently running 1.1.3-0ubuntu2). While means a minute or so, it is
definitely less than the activation time of the screensaver.

I tried to create a library that i could preload to make totem segfault on exit
so i could provide a backtrace. Apparently my coding skills have degraded too
much for me to create a simple reliable segfault ;)

Corey Burger (corey.burger) wrote :

Totem-xine does it as well. Let me grab a backtrace for you.

Sami Haahtinen (ressu) wrote :

Ok, i managed to get my programming skill up to par, here is the backtrace:

(gdb) bt
#0 0x00000008 in ?? ()
#1 0xb7f8b1b6 in ?? ()
#2 0xbfaa1068 in ?? ()
#3 0xb7f9ab30 in _dl_rtld_di_serinfo () from /lib/
#4 0xb7732045 in _gdk_windowing_exit () from /usr/lib/
#5 0xb7732045 in _gdk_windowing_exit () from /usr/lib/
#6 0xb7e50eab in bonobo_ui_gtk_module_info_get ()
   from /usr/lib/
#7 0xb7a6fafc in _XError () from /usr/lib/
#8 0xb7a71207 in _XEventsQueued () from /usr/lib/
#9 0xb7a60e8e in XPending () from /usr/lib/
#10 0xb7725b0d in _gdk_x11_drawable_draw_xft_glyphs ()
   from /usr/lib/
#11 0xb7728407 in _gdk_events_queue () from /usr/lib/
#12 0xb72461e6 in g_main_context_check () from /usr/lib/
#13 0xb724654d in g_main_context_check () from /usr/lib/
#14 0xb7246ac3 in g_main_loop_run () from /usr/lib/
#15 0xb787ac45 in gtk_main () from /usr/lib/
#16 0x08063bb4 in main ()

Corey, can you get a backtrace from your copy too. Just to see that this isn't
just random.

As for these results, it would look like a bug in gdk-x11 and not totem.

Sami Haahtinen (ressu) wrote :

Created an attachment (id=3009)
Preload library to cause a crash and help debugging

This is the tool i used to cause a crash and get a backtrace.

Sami Haahtinen (ressu) wrote :

I'm now rather convinced that my previous backtrace is rather useless. i'm
trying to track down a better symbol than exit.

Sebastien Bacher (seb128) wrote :

Is the video crashing or the UI? Maybe the same as this upstream bug: too. Do you have any X Window
message when it crash?

Sami Haahtinen (ressu) wrote :

That looks like the same trace, and looks a bit like the same error. Also there
is an error in the terminal:
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 13192 error_code 2 request_code 149 minor_code 2)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

The UI exits (it doesn't really crash) with exit code 1. I just forced it to
crash to get a backtrace.

Sebastien Bacher (seb128) wrote :

This fix the issue here:

 totem (1.1.3-0ubuntu3) breezy; urgency=low
   * debian/patches/01_fixcrash.dpatch:
     - patch from the CVS to fix a crasher with the new version
       (Ubuntu: #12724).

I'm closing the bug. Let me know if that works for you.

Sami Haahtinen (ressu) wrote :

Confirming as fixed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.