On Die, 2006-04-25 at 23:24 +0100, Regis Boudin wrote: > Ok, si this bug is now starting to turn me crazy. > > All running tests point to a problem with Mesa : > -crash with Mesa in software mode
You mean the X error from the original report? Did you find out which extension generates it using xdpyinfo -queryExt|grep 144 ? > -no crash with Mesa using the ATI DRI, but weird display of the web > pages Seen that. Most likely a Mesa (driver) issue indeed. > -no crash with the nvidia proprietary driver, display is happy. > > When I tried using gdb to get a backtrace(attached), all I got was a > long list of calls involving wxWidgets, GTK, but not Mesa. X is asynchronous, so the client receives the error long after it sent out the request causing it. When this happens, GTK should tell you how to make it use a synchronous X connection. > CCing the XSF in case someone has an idea, A Mesa list might have been even better? :) > > > > OpenGL Status: > > > > Software Mode = Hard > > > > VENDOR : Tungsten Graphics, Inc. > > > > VERSION : 1.2 Mesa 6.4.1 > > > > RENDERER : Mesa DRI Radeon 20050528 AGP 4x x86/MMX+/3DNow!+/SSE NO-TCL > > > > GLU Version : 1.3 > > > > Aux buffers count 0 > > > > Acumm rgba : 0 0 0 0 > > > > *** Amaya: Irrecoverable error ***Segmentation fault Can you get a backtrace for this? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
