Re: [e-users] Failed to initialize EvasGL

2018-04-07 Thread The Rasterman 
On Sat, 07 Apr 2018 23:34:26 + Wido  said:

> Hi Ross, I don't think sid has the debug symbols from E22.3, which is the
> verion I have.
> 
> Raster, the problem was indeed in the driver version. When I rolled back to
> 386.111 and enabled opengl evas engine, the error logs disapeared ¯\_(ツ)_/¯

well for now that will work. i can't see issues on newer drivers though... on a
different os? perhaps something else? you're using egl/gles enabled in efl build
instead of opengl on nvidia? not sure.

> El sáb., 7 de abr. de 2018 a la(s) 15:15, Ross Vandegrift 
> escribió:
> 
> > On Sat, Apr 07, 2018 at 04:27:58PM +, Wido wrote:
> > > Unfortunately, sparky doesn't provides debug symbols, and I'm over
> > > compiling.
> >
> > Since you're running buster, you can install the packages from sid.  Debug
> > symbols are also packaged, see instructions at:
> > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
> >
> > Ross
> >
> >
> > --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___
> > enlightenment-users mailing list
> > enlightenment-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> >
> -- 
> Wido
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users


-- 
- Codito, ergo sum - "I code, therefore I am" --
Carsten Haitzler - ras...@rasterman.com


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Failed to initialize EvasGL

2018-04-07 Thread Wido 
Hi Ross, I don't think sid has the debug symbols from E22.3, which is the
verion I have.

Raster, the problem was indeed in the driver version. When I rolled back to
386.111 and enabled opengl evas engine, the error logs disapeared ¯\_(ツ)_/¯

El sáb., 7 de abr. de 2018 a la(s) 15:15, Ross Vandegrift 
escribió:

> On Sat, Apr 07, 2018 at 04:27:58PM +, Wido wrote:
> > Unfortunately, sparky doesn't provides debug symbols, and I'm over
> > compiling.
>
> Since you're running buster, you can install the packages from sid.  Debug
> symbols are also packaged, see instructions at:
> https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
>
> Ross
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
>
-- 
Wido
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Failed to initialize EvasGL

2018-04-07 Thread Ross Vandegrift 
On Sat, Apr 07, 2018 at 04:27:58PM +, Wido wrote:
> Unfortunately, sparky doesn't provides debug symbols, and I'm over
> compiling.

Since you're running buster, you can install the packages from sid.  Debug
symbols are also packaged, see instructions at:
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Ross

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Failed to initialize EvasGL

2018-04-07 Thread Wido 
What could I do to better show you the issue?

Unfortunately, sparky doesn't provides debug symbols, and I'm over
compiling.

Here's the complete output of the .xsession-error. These 4 messages keeps
showing permanently. I did one of the suggested backtraces, since all 4 are
the same, but I know that without dbg symbols they may not be much help.

https://pastebin.com/8g8Lg7i6

I'll try downgrading nvidia drivers, but I'm not sure if I can still get
the packages


thanks!

El sáb., 7 de abr. de 2018 03:31, Carsten Haitzler 
escribió:

> On Sat, 07 Apr 2018 04:33:52 + Wido  said:
>
> > Hi,
> >
> > I'm currently using E 22.3 with Debian test (buster). I'm geting E from
> the
> > Sparky repos. Also, I have an Nvidia 1050 with propietary blobs (from
> > debian non-free)
> >
> > Recently, E started misbehaving, high cpu and suddenly my home partition
> > was full.
> >
> > I noticed that E filled the .xsession-errors file with some evas GL
> errors:
> >
> > ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:973
> > _surface_cap_init() There are no available surface formats. Error!
> > ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:1901
> > evgl_engine_init() Error initializing surface cap
> > ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:1946
> > evgl_engine_init() Failed to initialize EvasGL!
> > ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:1605
> > _evgl_tls_resource_get() Invalid EVGL Engine!
> >
> >
> > and a backtrace that, since I don't have debug symbols, I can't really
> see.
> > And it's printing that permanently.
> >
> > I was able to get rid of those messages, by changing the engine to
> software
> > (it was in opengl), but performance now sucks
> >
> > Now, I think the culprit is in nvidia drives, since they were updated
> from
> > version 386.111 to 390.42. And I did this after updating E from 22.1 to
> > 22.3 (about a week later), so  I don't think updating E had anything to
> do,
> > but updating nvidia's driver did.
> >
> > could it be possible to fix this?
>
> i'm on the nvidia 390.42 drivers too and i don't see any of the issues you
> seem
> to have (this is arch though). gl working as normal. i am on git master
> though
> (naturally). :/ i guess downgrading your nvidia driver will do the job for
> you... but i don't see the same issues. :(
>
> > --
> > Wido
> >
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___
> > enlightenment-users mailing list
> > enlightenment-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> >
>
>
> --
> - Codito, ergo sum - "I code, therefore I am" --
> Carsten Haitzler - ras...@rasterman.com
>
> --
Wido
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Failed to initialize EvasGL

2018-04-07 Thread The Rasterman 
On Sat, 07 Apr 2018 04:33:52 + Wido  said:

> Hi,
> 
> I'm currently using E 22.3 with Debian test (buster). I'm geting E from the
> Sparky repos. Also, I have an Nvidia 1050 with propietary blobs (from
> debian non-free)
> 
> Recently, E started misbehaving, high cpu and suddenly my home partition
> was full.
> 
> I noticed that E filled the .xsession-errors file with some evas GL errors:
> 
> ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:973
> _surface_cap_init() There are no available surface formats. Error!
> ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:1901
> evgl_engine_init() Error initializing surface cap
> ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:1946
> evgl_engine_init() Failed to initialize EvasGL!
> ERR<1136>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:1605
> _evgl_tls_resource_get() Invalid EVGL Engine!
> 
> 
> and a backtrace that, since I don't have debug symbols, I can't really see.
> And it's printing that permanently.
> 
> I was able to get rid of those messages, by changing the engine to software
> (it was in opengl), but performance now sucks
> 
> Now, I think the culprit is in nvidia drives, since they were updated from
> version 386.111 to 390.42. And I did this after updating E from 22.1 to
> 22.3 (about a week later), so  I don't think updating E had anything to do,
> but updating nvidia's driver did.
> 
> could it be possible to fix this?

i'm on the nvidia 390.42 drivers too and i don't see any of the issues you seem
to have (this is arch though). gl working as normal. i am on git master though
(naturally). :/ i guess downgrading your nvidia driver will do the job for
you... but i don't see the same issues. :(

> -- 
> Wido
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> 


-- 
- Codito, ergo sum - "I code, therefore I am" --
Carsten Haitzler - ras...@rasterman.com


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users