On Mon, 9 Apr 2012 11:19:44 +0200 Cedric BAIL said:
> On Mon, Apr 9, 2012 at 9:19 AM, Carsten Haitzler wrote:
> > On Wed, 4 Apr 2012 11:13:33 +0200 Thanatermesis
> > said:
> >> E17 segfaults in the first run on virtualbox, when is running the wizard
> >> module checking for GL capabilities.
> >
On Mon, Apr 9, 2012 at 9:19 AM, Carsten Haitzler wrote:
> On Wed, 4 Apr 2012 11:13:33 +0200 Thanatermesis
> 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 seem
On Wed, 4 Apr 2012 11:13:33 +0200 Thanatermesis
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 s
Maybe blacklist for that version "only" ?
I think that is related in the way of how it works this GL, i think that is
something like a fake layer underlying to the real graphic card, this could
explain why do strange things like "ghosted windows of GL when switching
e17 desktops"
2012/4/4 Vincen
On Wed, Apr 4, 2012 at 11:13 AM, Thanatermesis
wrote:
> 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 som
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
