From: John Z. <joh...@wa...> - 2008-10-05 03:51:28
|
I can confirm this problem. We were running VPython over x4vnc (supports OpenGL) just fine until a lab upgrade this fall. With the new machines running Kubuntu Hardy and Intel graphics drivers, we get this same error trying to run visual over VNC. Visual works fine at the console, and other OpenGL apps run fine over VNC. I'm at a loss. We are running with Python 2.5.2 and visual 3.2.9. --John On Fri, 2008-10-03 at 15:02 +0100, chris lyon wrote: > I presume there are people running visual over VNC like piping > mechanisms with no trouble? > > > chris@harvest001:~/wirusview$ python > Python 2.4.4 (#2, Apr 15 2008, 23:43:20) > [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from visual import * > >>> a = sphere() > >>> Gdk-ERROR **: GLXBadLargeRequest > serial 108 error_code 158 request_code 148 minor_code 2 > > > Where best for me to start digging? > > Chris > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |