totem-xine and mplayer cannot play any video

[junmin]

try to open some video files, but totem and mplayer just pop up and gone.
i am using gutsy

[Sebastien Bacher (seb128)]

Thank you for your bug. What videocard and driver do you use? Do you use compiz (desktop effects option)? Does it happen without running it? Could you run those applications from a command line and copy the error displayed to a comment?

[junmin (tienchi)]

the video card is intel X3100. using the least xserver-xorg-video-intel driver from repo of gutsy.
i am using compiz, anyway, this problema happens with metacity too.here is output from command line.

junmin@T61Linux:~$ totem MyDownloads/____01.wmv

Gdk-ERROR **: The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 67 error_code 11 request_code 141 minor_code 19)
  (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...
Trace/breakpoint trap (core dumped)

junmin@T61Linux:~$ mplayer MyDownloads/____01.wmv
MPlayer 2:1.0~rc1-0ubuntu11 (C) 2000-2006 MPlayer Team
CPU: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (Family: 6, Model: 15, Stepping: 10)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing MyDownloads/____01.wmv.
ASF file format detected.
VIDEO: [WMV3] 800x600 24bpp 6.000 fps 0.0 kbps ( 0.0 kbyte/s)
open: No such file or directory
[MGA] Couldn't open: /dev/mga_vid
open: No such file or directory
[MGA] Couldn't open: /dev/mga_vid
[VO_TDFXFB] Can't open /dev/fb0: No such file or directory.
[VO_3DFX] Unable to open /dev/3dfx.
==========================================================================
Opening video decoder: [dmo] DMO video codecs
DMO dll supports VO Optimizations 0 1
DMO dll might use previous sample when requested
GetOutput r=0x0 size:1440000 align:1
StreamCount r=0x0 1 1
Decoder supports the following formats: YV12 YUY2 UYVY YVYU RGB8 RGB555 RGB565 RGB24 RGB32
Decoder is capable of YUV output (flags 0x1b)
VDec: vo config request - 800 x 600 (preferred colorspace: Packed YUY2)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 800x600 => 800x600 Planar YV12
Selected video codec: [wmv9dmo] vfm: dmo (Windows Media Video 9 DMO)
==========================================================================
==========================================================================
Forced audio codec: mad
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 16000 Hz, 2 ch, s16le, 16.0 kbit/3.12% (ratio: 2000->64000)
Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg))
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
X11 error: BadAlloc (insufficient resources for operation)?,?% 0 0

MPlayer interrupted by signal 6 in module: vo_check_events
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlay...

[Suzan (suzan72)]

Same here with totem with enabled desktop-effects. But it didn't crash with desktop-effects disabled.

I've got an nvidia GeForce Go 7300 and I use the nvidia-glx-new driver under an actual Gusty.

Totem says the following:

Gdk-ERROR **: The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 126 error_code 11 request_code 140 minor_code 19)
  (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...
Trace/breakpoint trap (core dumped)

[mike.calimlim (mike-calimlim)]

I also have the same error.... It crashes even when the desktop-effects are disabled.....

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 42 error_code 8 request_code 141 minor_code 14)
  (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.)

I've got a ATI Radeon Mobility X2300 and got a xorg-fglrx driver installed on Gutsy.....

[Mikael Hansson (mikaelh)]

I have the same problem when running the restricted ATI drivers. When I revert to VESA drivers, it starts working immediately. It affects all xine-based players I've tried.

[pauliephonic (pauliephonic)]

I have the same problem, no desktop effects enabled

paul@ubuntu-media:~$ totem
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 41 error_code 8 request_code 142 minor_code 14)
  (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.)

I am using the fglrx driver.

I have dual monitors enabled if that makes any difference.

xorg.conf
Section "Device"
 Identifier "ATI Technologies, Inc. ATI Default Card"
 Driver "fglrx"
 BusID "PCI:1:0:0"
 Option "DesktopSetup" "horizontal" #Enable Big Desktop
 Option "Mode2" "1280x1024" #Resolution for second monitor
 Option "DesktopSetup" "LVDS,AUTO" #the types of monitors that is connected LVDS = LCD, CRT, AUTO
 Option "HSync2" "65" #This sets the horizontal sync for the secondary display.
 Option "VRefresh2" "60" #This sets the refresh rate of the secondary display.
EndSection

[pauliephonic (pauliephonic)]

Sorry for posting again, but I don't think that this bug is a duplicate at all.

It doesn't seem to be related to Compiz

Regards,

Paul

[bealer (robertbeal)]

I get this problem too.

Running Gutsy, with an ATI X1900. It worked ok in the 64-bit version strangely, but not the 32-bit version. I did however have the very latest 8.42 ATI drivers installed with the 64-bit version, whereas I'm no currently running via the ones in the repo.

(totem:9794): GLib-CRITICAL **: g_bookmark_file_get_size: assertion `bookmark != NULL' failed
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 42 error_code 8 request_code 141 minor_code 14)
  (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.)

[Dag-Erling Smørgrav (dag-erling)]

I previously posted this as a followup to #35229 (a different bug with very similar symptoms):

<<
Same as Chris Waigl. Worked fine with Feisty. The previously mentioned workaround (scaling or removing totem_logo.png) does not work. Furthermore, gxine fails in the exact same manner:

The program 'gxine' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 326 error_code 8 request_code 141 minor_code 14)
  (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.)

Really annoying, as I just got season 5 of the Simpsons for Christmas. I watched the first four seasons without a hitch on Feisty.

I was able to watch the first episode using totem-gstreamer. I also tried vlc, but the image was very jumpy, and navigation was almost impossible as I could not see the mouse pointer while it was inside the vlc window.

Correction, I was able to watch the first episode using mplayer. With the gutsy-backports version, I was even able to see (but not use) the menus. With totem-gstreamer, I was not able to see anything but an error message about missing codecs.
>>

Up-to-date Gutsy (Medibuntu but no backports) on a Lenovo T60, ATI Radeon Mobility X1400, xorg-driver-fglrx, no desktop effects.

[Dag-Erling Smørgrav (dag-erling)]

To be very clear, this is *not* a duplicate of #111257.

[Dag-Erling Smørgrav (dag-erling)]

A little more digging shows there are actually two different issues at play here. One of them (BadAlloc when using compiz) is indeed a duplicate of #111257. The other (BadMatch when using fglrx) is a duplicate of #130696. That one hasn't been fixed yet, but several workarounds are described in the comments.

[blackmx (net-surf)]

I have an ATI X2300

** (totem:12966): DEBUG: Init of Python module
** (totem:12966): DEBUG: Registering Python plugin instance: BBCViewer+TotemPythonPlugin
** (totem:12966): DEBUG: Creating object of type BBCViewer+TotemPythonPlugin
** (totem:12966): DEBUG: Creating Python plugin instance
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 61 error_code 11 request_code 140 minor_code 19)
  (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.)