Gxine crashes on launch with BadMatch error

[Ludovico Fischer]

Launching gxine results in the splash screen flashing for a moment; then the program crashes. Here is Terminal output:

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 331 error_code 8 request_code 140 minor_code 14)

Ubuntu Gutsy 7.10.
This doesn't seem neither the mozilla-related bug, nor the the one coming up with full screen (?).

[Darren Salt (dsalt)]

This could be an X configuration or driver problem. Install libxine1-dbg (optional, but very useful for backtraces), then
  $ gdb --args gxine --sync
  (gdb) break gdk_x_error
  (gdb) run
...
  (gdb) bt

Also, you may find that at least one of the following works:
  gxine -V opengl
  gxine -V xshm
If so, you can edit the video.driver option in ~/.gxine/config accordingly (you'll need to uncomment it), but this isn't really fixing the problem...

(Bug 130696 may be relevant.)

[Ludovico Fischer (ludovicofischer)]

Running gxine -V opengl and gxine -V xshm results in normal startup. gxine also works the normal way under xubuntu.

 I can't get the backtrace you asked:

(gdb)break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Whether I choose yes or no, bt always gives 'no stack'. Also, it can't find the debug symbols.

. Using a radeon x1600 with fglrx installed by the distribution. I've had other hassles with X on Ubuntu Gutsy Beta.

[Darren Salt (dsalt)]

> (gdb)break gdk_x_error
> Function "gdk_x_error" not defined.
> Make breakpoint pending on future shared library load? (y or [n]) y

No installed libgtk2.0-dbg?

> Whether I choose yes or no, bt always gives 'no stack'.

Either you forgot to tell gdb to run the program or the program exited normally.

> Also, it can't find the debug symbols.

This is reported for each library or executable without debug symbols. Mostly harmless.

> Using a radeon x1600 with fglrx installed by the distribution.

That rules out use of xserver-xorg-video-ati :-\

You could try xserver-xorg-video-avivo (AFAIK, it's more or less completelt unaccelerated) or try the new driver, very much still in development, for R5xx/R6xx (link below). Otherwise, you're stuck with the taintware; and if you want 3D, you're stuck with it anyway for now (until AMD release the relevant specs and the necessary work is done to the drivers).

http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd

(http://www.freedesktop.org/wiki/Infrastructure/git/Users for info on how to check out the source.)

[Ludovico Fischer (ludovicofischer)]

Indeed, I lacked that second debug library.

Here is the backtrace:

#0 gdk_x_error (display=0x8af5800, error=0xbfea25a8)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
#1 0xb7a26bfa in _XError () from /usr/lib/libX11.so.6
#2 0xb7a286c4 in _XReply () from /usr/lib/libX11.so.6
#3 0xb256ef2c in XvGetPortAttribute ()
   from /usr/lib/libXv.so.1
#4 0xb2584de0 in open_plugin_2 (class_gen=0x8b15138,
    visual_gen=0xbfea27bc) at video_out_xv.c:1097
#5 0xb258590c in open_plugin_old (class_gen=0x8b15138,
    visual_gen=0xbfea2880) at video_out_xv.c:1660
#6 0xb7f8b4cf in _x_load_video_output_plugin (
    this=0x80bf610, id=0x0, visual_type=1,
    visual=0xbfea2880) at load_plugins.c:1527
#7 0xb7f8b544 in xine_open_video_driver (this=0x80bf610,
    id=0x0, visual_type=1, visual=0xbfea2880)
    at load_plugins.c:1591
#8 0x0805a6a8 in ?? ()
#9 0x080bf610 in ?? ()
#10 0x00000000 in ?? ()