Daniel Blaschke <[EMAIL PROTECTED]> writes: > Unfortunately, I don't know exactly when it stopped working but it was > some time ago. (I don't play on my laptop that often.) I did, however, > try changing the graphics-driver in xorg.conf to "vesa", and found out > that gnubg works fine with that. On my other computer I have an nvidia > card and it works fine there as well. So it seems to be a problem with > the i810-driver and as far as I remember, that driver was updated in > etch a couple of times in the past months...
I was kind of afraid of that. Unfortunately, I'm not sure whether that means that it's really a problem in the driver or if gnubg is doing something marginal that's just happening to work with the other drivers. I personally only have NVidia cards to test with, which isn't a good test case since I can't do 3D with them with free drivers and no one is really interested in the results of using the proprietary drivers since we can't check the source code. > I also played around with xorg.conf some more and found out, that when > the "dri"-module is NOT loaded, gnubg no longer crashes - but of course > 3D-performance is then very poor. (driver is once more i810). Yeah, it's definitely related to the GLX and DRI interface somehow. Without the 3D board, gnubg doesn't use that. I'm guessing that when you go into that menu option, gnubg is probing to see if can do 3D, and that's causing the failure. None of the bugs on xserver-xorg-video-i810 seem relevant. I'm not sure how to tackle this, to be honest. If you run gnubg --sync inside gdb and set a breakpoint like that error message suggested, can you get a backtrace? (Let me know if you haven't done that before and need more detailed instructions.) -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
