Hey Thomas, Thanks for the info.
I don't *think* that pyglet is using glut functions to manage windows - looking at the pyglet source, it seems to call directly into X windows libraries using ctypes instead. I don't know whether Glut method calls and X lib calls would, under the covers, both hit the same speedbump, or whether these are two separate seg faults. Clearly though, the common factor is the ATI drivers under Jaunty. I have since found other things that are flaky here. Some games work fine, others (eg., BZFlag) lock up after a fraction of a second. In fact, now I come to write this, maybe there's a helpful bug I could file for the ati driver project. I'll go over there and see whether their existing bug reports seem to have it all covered. I considered downgrading from Jaunty back to Intrepid, but there is no formal migration path, so it would be a full reinstall. So I'm going to use my Nvidia desktop machine to develop on while the install ticks along, and hope the open source ATI drivers improve the situation in the not-too-distant-future. Have also upped the priority on a replacement laptop with Nvidia on-board, but that won't happen immediately. Thanks all, Jonathan On May 4, 10:04 am, Thomas <[email protected]> wrote: > hi, i have the same issue using the ati driver with jaunty. > on launchpad, they mentioned several times that this can be a problem > with the glutCreateWindow() function, in particular it has to be > called before glutInitDisplayMode(). > > here is an answer of an user from the launchpad issue tracker: > [quote] > Yes, making the code look like this, completely resolves this > segmentation fault problem: > > GLUT.glutInit(sys.argv) > GLUT.glutCreateWindow('foobar') # required to be a line before > glutInitDisplay > GLUT.glutInitDisplayMode(GLUT.GLUT_RGBA | GLUT.GLUT_DOUBLE) > [/quote] > > my understanding of the pyglet code is very poor right now, but i will > try to find out if this is the source of the problem.. > > On 1 Mai, 14:36, Jonathan Hartley <[email protected]> wrote: > > > > It's not clear to me whether the seg fault you're reporting happens > > > with the "fglrx" or "ati" driver (or both?) > > > Beg your pardon. > > The 'fglrx' driver doesn't work at all since I upgraded (I am not > > alone in this.) > > The segfault when using pyglet occurs using the 'ati' driver (am I > > alone in this?) > > > > Stop trying to use accelerated ATI under Linux? > > > Sincerely considering it. > > > Thanks. > > > On May 1, 1:39 am, Richard Jones <[email protected]> wrote: > > > > On 01/05/2009, at 9:54 AM, Jonathan Hartley wrote: > > > > > I upgraded to Ubuntu Jaunty (9.04) and now 'from pyglet.window import > > > > Window' gives me a seg fault. > > > > > I have an ATI card (ohdear), a Radeon X1400. > > > > > I tried to use ATI's proprietary 'fglrx' driver at first, but that > > > > apparently has problems under Jaunty, and only produces garbage on- > > > > screen for me, so I've fallen back to the open source 'ati' driver, > > > > which apparently works, reportedly is stable, but has mediochre 3D > > > > performance. > > > > It's not clear to me whether the seg fault you're reporting happens > > > with the "fglrx" or "ati" driver (or both?) > > > > > Anyone got any suggestions of things I might try? > > > > Stop trying to use accelerated ATI under Linux? > > > > Richard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
