You are not logged in.
Hi,
I have had e17 installed for quite a while from the e-svn packages, but did not realise that the packages had apparently been dropped from the repos, and I have just switched to the extra/enlightenment17 packages. I noticed right away that it takes much longer to start into an enlightenment session than it did before. When I start X to xterm and then run enlightenment_start, I find these error messages in the output:
ERR<>e_randr_12.c:214 safety check failed: E_RANDR_12_NO_MODE(mode) is true
ERR<>e_randr_12_output.c:196 safety check failed: outputs == NULL
and
ERR<1285>: efreet_ini.c:449 efreet_ini_localestring_get() safety check failed: ini->section == NULL
ERR<1285>: efreet_ini.c:449 efreet_ini_localestring_get() safety check failed: ini->section == NULL
ERR<1285>: efreet_ini.c:336 efreet_ini_string_get() safety check failed: ini->section == NULL
ERR<1285>: efreet_ini.c:419 efreet_ini_boolean_get() safety check failed: ini->section == NULL
ERR<1285>: efreet_ini.c:336 efreet_ini_string_get() safety check failed: ini->section == NULL
ERR<1285>: efreet_ini.c:336 efreet_ini_string_get() safety check failed: ini->section == NULL
I also see a lot of
libpng warning: iCCP: known incorrect sRGB profile
I do not know if these have anything to do with the long startup time, but these are the only error messages I see in the output. Does anyone know if these might be the problem, or if there is any other way I can debug this?
Thanks!
Offline
Are *all* of the EFL libs up to date as well? This would include Ecore, E_dbus, Edje, Eet, Eeze, Efreet, Eina, Eio, Embryo, Emotion, Ethumb, & Evas.
The libpng warning can safely be ignored. It's just libpng 1.6 complaining that some of the pngs are using old sRGB profiles.
Offline
Thanks for the reply. Yes, pacman reports that all of them are up to date (all ver. 1.7.7-1).
Offline
Next thing I would suspect is problems with the config, maybe something hanging around from the old system. Rename ~/.e and try again.
Offline
No, still no luck. Startup is still as slow, and those two error messages still appear. Are there any other logs I can/should look at?
Offline