[gutsy] gxine crashes at startup due to an X server error

[Emiliano]

when executing gxine via terminal, it crashes and reports the following error:

$ gxine
received X error event: BadMatch (invalid parameter attributes)
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 433 error_code 8 request_code 140 minor_code 17)
  (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.)

It happens with gxine only, and not with other programs which use the xine library

[Andrew Starr-Bochicchio (andrewsomething)]

Thanks for the bug report. I've set the package as gxine.

 In the future, if you know the affected package, file the bug against it not just Ubuntu itself. This will help the right developers see your report.

[Emiliano (emiliano-perulli)]

Sure, I'm sorry, I tought I set the package..

[Darren Salt (dsalt)]

This looks like Yet Another Xv Failure to me. You'll have to get a full backtrace (all threads; you may need gxine debug symbols and libxine1-dbg) and report version numbers of gxine & libxine1.

[Emiliano (emiliano-perulli)]

Well, it seems I can't get a suitable backtrace
gxine version: 0.5.11-3ubuntu3
libxine1 version: 1.1.10-1~gutsy1

[Emiliano (emiliano-perulli)]

I'll add my xorg log file, just after gxine has been executed.
Maybe it could be useful to you.

[Darren Salt (dsalt)]

Looks like a case for radeonhd. Upstream does not use and does not support use of fglrx, but if you can provide enough debug info, something useful might still come of it. If you're lucky.

BTW, you can provide a useful backtrace. You just failed to set the breakpoint on gdk_x_error ‒ as given in the instructions which were printed along with the error…