[e-users] libeina and efreet errors

2016-05-19 Thread Mick 
Hi All,

I've noticed these backtraces in a box with a Kaveri APU:

ERR<15609>:eina_safety lib/efreet/efreet_ini.c:412 
efreet_ini_localestring_get() s
afety check failed: ini->section == NULL
*** Backtrace ***
/usr/lib64/libeina.so.1  0x7fbca524e6e9 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca5250287 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca525e49a 0x7fbca522b000
/usr/lib64/libefreet.so.10x7fbca499693f 0x7fbca498b000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x403a4b 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x404135 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x402db7 0x40
/lib64/libc.so.6 0x7fbca43eb610 0x7fbca43cb000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x4036c9 0x40
ERR<15609>:eina_safety lib/efreet/efreet_ini.c:412 
efreet_ini_localestring_get() s
afety check failed: ini->section == NULL
*** Backtrace ***
/usr/lib64/libeina.so.1  0x7fbca524e6e9 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca5250287 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca525e49a 0x7fbca522b000
/usr/lib64/libefreet.so.10x7fbca499693f 0x7fbca498b000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x403a93 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x404135 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x402db7 0x40
/lib64/libc.so.6 0x7fbca43eb610 0x7fbca43cb000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x4036c9 0x40

ERR<15609>:eina_safety lib/efreet/efreet_ini.c:299 efreet_ini_string_get() 
safety check failed: ini->section == NULL
*** Backtrace ***
/usr/lib64/libeina.so.1  0x7fbca524e6e9 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca5250287 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca525e49a 0x7fbca522b000
/usr/lib64/libefreet.so.10x7fbca4995ff7 0x7fbca498b000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x403adb 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x404135 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x402db7 0x40
/lib64/libc.so.6 0x7fbca43eb610 0x7fbca43cb000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x4036c9 0x40
ERR<15609>:eina_safety lib/efreet/efreet_ini.c:382 efreet_ini_boolean_get() 
safety check failed: ini->section == NULL
*** Backtrace ***
/usr/lib64/libeina.so.1  0x7fbca524e6e9 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca5250287 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca525e49a 0x7fbca522b000
/usr/lib64/libefreet.so.10x7fbca49965af 0x7fbca498b000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x403b23 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x404135 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x402db7 0x40
/lib64/libc.so.6 0x7fbca43eb610 0x7fbca43cb000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x4036c9 0x40
ERR<15609>:eina_safety lib/efreet/efreet_ini.c:299 efreet_ini_string_get() 
safety check failed: ini->section == NULL
*** Backtrace ***
/usr/lib64/libeina.so.1  0x7fbca524e6e9 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca5250287 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca525e49a 0x7fbca522b000
/usr/lib64/libefreet.so.10x7fbca4995ff7 0x7fbca498b000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x403b46 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x404135 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x402db7 0x40
/lib64/libc.so.6 0x7fbca43eb610 0x7fbca43cb000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x4036c9 0x40
ERR<15609>:eina_safety lib/efreet/efreet_ini.c:299 efreet_ini_string_get() 
safety check failed: ini->section == NULL
*** Backtrace ***
/usr/lib64/libeina.so.1  0x7fbca524e6e9 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca5250287 0x7fbca522b000
/usr/lib64/libeina.so.1  0x7fbca525e49a 0x7fbca522b000
/usr/lib64/libefreet.so.10x7fbca4995ff7 0x7fbca498b000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x403c2f 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x404135 0x40
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x402db7 0x40
/lib64/libc.so.6 0x7fbca43eb610 0x7fbca43cb000
/usr/lib64/efreet/v-1.17/efreet_icon_cache_create0x4036c9 0x40
ERR<15602>:e src/bin/e_randr2.c:867 _screen_config_do() screen config loop!
*** Backtrace ***
/usr/lib64/libeina.so.1  0x7f58180b66e9 0x7f5818093000
/usr/lib64/libeina.so.1  0x7f58180b8287 0x7f5818093000
/usr/bin/enlightenment   0x4e0440 0x40
/usr/bin/enlightenment   0x4e04bf 0x40
/usr/bin/enlightenment   0x4e04bf 0x40
/usr/bin/enlightenment   0x4e04bf 0x40
/usr/bin/enlightenment   0x4e04bf 0x40
/usr/bin/enlightenment   0x4e04bf 0x40
/usr/bin/enlightenment   0x4e04bf 0x40
/usr/bin/enlightenment   0x4e0eca 0x40
/usr/bin/enlightenment   0x4e1562 0x40

Re: [e-users] GLX Pixmap problem

2016-05-19 Thread Daniel Hirt 
This is being tracked on
https://phab.enlightenment.org/T3030.

Feel free to share more input there.
I will go ahead and quote your output there.

Thanks.
--Danny.

On 05/15/2016 05:39 AM, Conrad Knight wrote:
> I seem to have run into a conflict with efl, enlightenment, and nvidia
> GLX libraries, and i'm not sure where the problem lies. While running
> E-0.20.6, or E-0.21-beta, any windows opened have completely black
> contents. The window decorations are fine, and E's menus, etc. appear
> normally. But if i open a settings window from the menu, it's black.
> Terminology is likewise completely black. There are error messages in
> my .xsession-errors:
> 
> ERR<11215>:evas-gl_x11 modules/evas/engines/gl_x11/evas_engine.c:2783
> eng_image_native_set() GLX Pixmap create fail
> 
> This does not occur if i switch my glx libraries to the Intel ones for
> this laptop. It also does not occur if i run terminology under another
> window manager. The nvidia drivers appear to be working correctly
> otherwise (i can run Steam games that depend on glx 1.4, for
> instance).
> 
> I've tried recompiling efl, and enlightenment, to no avail. Would
> anyone have any suggestions what to try next? :)
> 
> TIA,
> -Conrad.
> 

--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] GLX Pixmap problem

2016-05-19 Thread Carsten Holtkamp 
Am Sat, 14 May 2016 22:39:28 -0400
schrieb Conrad Knight :

> I seem to have run into a conflict with efl, enlightenment, and nvidia
> GLX libraries, and i'm not sure where the problem lies. While running
> E-0.20.6, or E-0.21-beta, any windows opened have completely black
> contents. The window decorations are fine, and E's menus, etc. appear
> normally. But if i open a settings window from the menu, it's black.
> Terminology is likewise completely black. 

Try Settings/Compositor/Advanced/Rendering
and uncheck Texture from pixmap

--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users