Re: [e-users] [E-devel] E causing problems with ArchLinux kernel 3.15.8-1-ARCH and possible vbox

2014-08-06 Thread Christopher Barry
On Thu, 7 Aug 2014 07:53:09 +0900 Carsten Haitzler (The Rasterman) wrote: >On Wed, 6 Aug 2014 17:57:05 -0300 Gustavo Sverzut Barbieri > said: > >> update, this is caused by efl/src/lib/ecore_x/xlib/ecore_x_vsync.c >> "#define ECORE_X_VSYNC_DRM 1". If you remove that line (or #undef the >> sym), i

Re: [e-users] [E-devel] E causing problems with ArchLinux kernel 3.15.8-1-ARCH and possible vbox

2014-08-06 Thread The Rasterman
On Wed, 6 Aug 2014 17:57:05 -0300 Gustavo Sverzut Barbieri said: > update, this is caused by efl/src/lib/ecore_x/xlib/ecore_x_vsync.c > "#define ECORE_X_VSYNC_DRM 1". If you remove that line (or #undef the > sym), it works, now to find out the actual call that triggers it to > produce a test case

Re: [e-users] E causing problems with ArchLinux kernel 3.15.8-1-ARCH and possible vbox

2014-08-06 Thread Gustavo Sverzut Barbieri
update, this is caused by efl/src/lib/ecore_x/xlib/ecore_x_vsync.c "#define ECORE_X_VSYNC_DRM 1". If you remove that line (or #undef the sym), it works, now to find out the actual call that triggers it to produce a test case for them... On Wed, Aug 6, 2014 at 12:38 PM, Gustavo Sverzut Barbieri wr

Re: [e-users] E causing problems with ArchLinux kernel 3.15.8-1-ARCH and possible vbox

2014-08-06 Thread Gustavo Sverzut Barbieri
sorry for the noise, this has nothing to do with Enlightenment or new vsync. I've disabled it and still happens, we're just triggering a bug in drm. if you suffer from this problem just remove virtualbox-guest-modules and you'll fallback to fbdev without problems (just setting X to use fbdev does

[e-users] E causing problems with ArchLinux kernel 3.15.8-1-ARCH and possible vbox

2014-08-06 Thread Gustavo Sverzut Barbieri
Hi all, Just a heads up that recent Enlightenment (GIT) is causing problems with ArchLinux vanilla kernel (3.15.8-1-ARCH), at least running inside VirtualBox 4.3.14. I'm trying to isolate the problem to report that to kernel guys since a Kernel Oops is always a kernel bug, until then watch out if

Re: [e-users] E19 and terminology odd behaviour

2014-08-06 Thread The Rasterman
On Wed, 6 Aug 2014 09:25:45 -0300 Wido said: > Never used gdb with efl libs, or valgrind at all. > > I narrowed the issue to elementary, anything using elm throws a segv in > that same place how do you know its the same place without gdb/valgrind? :) as i said - this mail isnt useful - no infor

Re: [e-users] E19 and terminology odd behaviour

2014-08-06 Thread Wido
Never used gdb with efl libs, or valgrind at all. I narrowed the issue to elementary, anything using elm throws a segv in that same place El 05/08/2014 22:15, "Carsten Haitzler" escribió: > On Tue, 5 Aug 2014 19:25:38 -0300 Wido said: > > > Hi all, > > > > I just got a fresh install from git an