On Mon, Apr 9, 2012 at 9:19 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Wed, 4 Apr 2012 11:13:33 +0200 Thanatermesis <thanatermesis.e...@gmail.com> > said: >> E17 segfaults in the first run on virtualbox, when is running the wizard >> module checking for GL capabilities. >> >> The GL of virtualbox seems at this state a bit buggy, it seems to be a kind >> of overlay to the real graphic card, it does some buggy things on the >> interfaces, I think that the best could be to blacklist it (to fallback to >> software x11 mode). >> >> There's a traceback and a glxinfo: >> >> http://pastebin.com/YpTTLm3d >> >> http://pastebin.com/rqH2azgK > > there is no blacklist atm in the wizard - it tries to create a gl canvas - if > it succeeds then sets default gl/on/off based on driver from xorg log. looks > like the bt shows a definite bug in the vbox ogl driver - trying to print a > string to an invalid buffer addr. so how do u propose we implement this > blacklist? run glxinfo and read its stdout? i am not even sure it comes by > default with most distros (that have gl drivers of some sort). it's part of > mesa-utils, but it may likely not be there. could u give me your Xorg.0.log? > maybe there is something in there to look for.
We already have a blacklist in evas gl x11 engine. Couldn't we add it there ? -- Cedric BAIL ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
