Totem crashes on startup (0.20.0)

["J. Gardner Biggs" <gardnerbiggs houston rr com>]

Any others having this problem?


terminal output:

$ totem
** Message: video_widget_create
Benchmarking memcpy methods (smaller is better):
        glibc memcpy() : 439492311
        linux kernel memcpy() : 440806140
        MMX optimized memcpy() : 439707395
        MMXEXT optimized memcpy() : 252088913
        SSE optimized memcpy() : 266843198
input_dvb: init class succeeded
demux_sputext: initializing
audio_oss_out: Opening audio device...
audio_oss_out: using device >/dev/dsp<
audio_oss_out: using SNDCTL_DSP_GETODELAY
audio_oss_out : supported modes are mono stereo
video_out_xv: Xv extension is present but I couldn't find a usable yuv12
port.
              Looks like your graphics hardware driver doesn't support
Xv?!
video_out_syncfb: aborting. (unable to open syncfb device "/dev/syncfb")
video_out_sdl: warning, xine's SDL driver is EXPERIMENTAL
video_out_sdl: fullscreen mode is NOT supported
video_out: thread created
xine: xine_stream_new
demux_sputext: open_plugin() called
metronom: video discontinuity #1, type is 0, disc_off is 0
metronom: waiting for audio discontinuity #1
metronom: audio discontinuity #1, type is 0, disc_off 0
metronom: waiting for in_discontinuity update #1
metronom: video vpts adjusted with prebuffer to 97502
metronom: audio vpts adjusted with prebuffer to 103402
Using MMXEXT for IDCT transform
Using MMXEXT for motion compensation
xine: xine_play
xine: xine_play_internal ...done
video_out_sdl: change frame format
** Message: on_eos_event
 
Gdk-ERROR **: 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 40 error_code 2 request_code 146 minor_code 3)
  (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.)
aborting...