On Fri, 2006-04-28 at 21:12 +0100, Regis Boudin wrote: > On Thu, 2006-04-27 at 18:28 +0200, Michel Dänzer wrote: > > > > > -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. > > I know. The previously attached backtrace was obtained with libgl1-mesa-swx11, > running amaya with the --sync parameter, so there might be a problem there > too. Doing the same with libgl1-mesa-glx and DRI disabled, I get the > attached one. Could wxWidgets be doing something bad ?
Possibly; in particular in the previous backtrace, it does look like either wx or GTK is the culprit. In this case, it looks like it could be wx and/or libGL and/or the X server. > > > CCing the XSF in case someone has an idea, > > > > A Mesa list might have been even better? :) > > Sorry, I didn't find the debian-mesa list :) There's [EMAIL PROTECTED], but it used to only allow subscribers to post; not sure if that's still the case. At the moment, the relevant people are probably reading debian-x. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer