I'm not able to reproduce this either on Gutsy Tribe1 or on Feisty.
On an ati mobility x600 system with Gutsy Tribe1 installed, and the latest fglrx driver, I switched it to using "vesa", restarted X, and ran glxinfo. It complained about DRI missing but did not cause X to die.
Next I tried on a Dell 1505n with the factory-installed Feisty. It uses the i810 driver, but I switched it to vesa. It returns an error GLXBadContext but does not cause X to die.
I'm not able to reproduce this either on Gutsy Tribe1 or on Feisty.
On an ati mobility x600 system with Gutsy Tribe1 installed, and the latest fglrx driver, I switched it to using "vesa", restarted X, and ran glxinfo. It complained about DRI missing but did not cause X to die.
Next I tried on a Dell 1505n with the factory-installed Feisty. It uses the i810 driver, but I switched it to vesa. It returns an error GLXBadContext but does not cause X to die.
However, I found this bug report, that mentions an almost identical backtrace: https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 9080
Can you try the test mentioned in that bug, to reproduce the crash? ALWAYS_ INDIRECT= y glxgears"
"LIBGL_