desmume fails to start with GLXBadContext error

[Graham C]

Binary package hint: desmume

When I try to run desmume or desmume-glade (i.e. both of the application menu entries added by this package) I get the following error:

The program 'desmume-glade' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 397 error_code 154 request_code 143 minor_code 5)
  (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.)

desmume-cli works as expected when I feed it an nds rom, so I guess this is specific to the guis.

[Graham C (chckens)]

This is 0.7.3-3 in Hardy by the way, with a Radeon 9700 Pro using Free ati driver

[Cesare Tirabassi (norsetto)]

This seems to be caused by a call to glXMakeCurrent with an invalid GLX context and doesn't come from desmume code (even if desmume could be triggering the bug).
To know more, you should try to obtain a backtrace (https://wiki.ubuntu.com/Backtrace).
Make sure that you run desmume with the --sync option and set a breakpoint to the gdk_x_error() function with 'break gdk_x_error'.
Try also disabling AIGLX or DRI or running desmume with the --disable-3d and/or the --gdk-gl-force-indirect options.

[Graham C (chckens)]

desmume --disable-3d makes the problem go away, desmume --gdk-gl-force-indirect has no discernible effect

backtrace attached. I'll try disabling AIGLX/DRI next...

[Graham C (chckens)]

Disabling AIGLX also makes the problem disappear

[Cesare Tirabassi (norsetto)]

Thanks for your cooperation. Looks like an SDL bug, so setting as appropriate.

[Colin McQuillan (m-niloc)]

This is not related to SDL - the SDL calls are in other threads. I've extracted the relevant gtkglext parts into a program giving this error:

The program 'a.out' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 118 error_code 154 request_code 143 minor_code 5)
  (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.)

[Andy Hauser (andy-ubuntu-bugzilla)]

I tested the test programm on two Archlinux installations. It only shows the problem on x86_64 one with the fglrx drivers.
The other is x86 with intel drivers and does not show a problem running the a.out.

[Cesare Tirabassi (norsetto)]

Yes this is really Xorg (http://dri.sourceforge.net/doc/DRIuserguide.html):

GLXPixmap rendering is only supported for indirect rendering contexts. This
is a common OpenGL limitation. Attempting to use a direct rendering context
with a GLXPixmap will result in an X protocol error.

I guess the only solution would be to render to a pbfuffer (or even better an FBO) and then bind the buffer to a gtk drawable.

As Colin pointed out this is anyhow not a problem for desmume only, but to all apps that would be using the gtkglext rendering to pixmap functions when DRI is enabled (I can reproduce with the pixmap and pixmap-mixed examples, as well as with masyv).

[Evgeni Golov (evgeni)]

This is fixed in 0.8-2 in Debian.

[Justin Dugger (jldugger)]

Fixed in Jaunty. Please reopen if you can duplicate in Jaunty!