Created attachment 342946 [details] Output of "emerge --info" In my ~amd64 gentoo system, enlightenment-0.17.1 stopped working with recent versions of mesa. When enlightenment is launched, it stays forever in the splash screen (initialization). In order to use the computer then I have to switch to a console and restart the xdm service, choosing another window manager/desktop. The latest version of mesa in portage that works with enlightenment is 9.0.3.
Have you tried revdep-rebuild? Also have you tried to rebuild x11-wm/enlightenment and following packages after mesa upgrade: qfile /usr/lib64/xorg/modules/ ?
Yes, I have run revdep-rebuild. I have also run: # emerge -avt --oneshot mesa xorg-server $(qlist -I -C x11-drivers/) # emerge --verbose --tree --update --deep --newuse --ask --keep-going --with-bdeps=y @system @world # emerge --unmerge enlightenment # emerge --ask --verbose --depclean # emerge -avt enlightenment:0.17 After all of that the problem persists.
Could you, please, try to run enlightenment from console via startx (could be done from other X-server) and record whatever it will output? startx &> log Or try to remove ~/.xsession-errors and launch enlightenment again from xdm and see if ~/.xsession-errors will reappear. If so - post it here, please. Most probably it's just crashing during compositing initialization (which is mandatory now). You may also try to recompile enlightenment without opengl/gles USE-flags (opengl rendering isn't working well anyway).
(In reply to comment #3) > Could you, please, try to run enlightenment from console via startx (could > be done from other X-server) and record whatever it will output? > > startx &> log I have run: $ enlightenment_start &> enlightenment_start.log & and the output is attached. > Or try to remove ~/.xsession-errors and launch enlightenment again from xdm > and see if ~/.xsession-errors will reappear. If so - post it here, please. The file ~/.xsession-errors obtained when trying to run enlightenment from lightdm is also attached.
Created attachment 343220 [details] enlightenment_start.log
Created attachment 343222 [details] .xsession-errors
Created attachment 343224 [details] Xorg.0.log
(In reply to comment #4) > (In reply to comment #3) > > Could you, please, try to run enlightenment from console via startx (could > > be done from other X-server) and record whatever it will output? > > > > startx &> log > > I have run: > > $ enlightenment_start &> enlightenment_start.log & In this case enlightenment does not start.
(In reply to comment #3) > You may also try to recompile enlightenment without opengl/gles USE-flags > (opengl rendering isn't working well anyway). Recompiling without opengl works, but the composite engine is set to software. Recompiling without gles also works, with the composite engine set to opengl. So the problem relies with GLES.
(In reply to José Romildo Malaquias from comment #9) > (In reply to comment #3) > > > You may also try to recompile enlightenment without opengl/gles USE-flags > > (opengl rendering isn't working well anyway). > > Recompiling without opengl works, but the composite engine is set to > software. > > Recompiling without gles also works, with the composite engine set to opengl. > > So the problem relies with GLES. I just added enlightenment-0.17.5_pre1 to the main tree. It should be on your local rsync mirror in a few hours. Please test it and report, if the issue is still there.
(In reply to Thomas Sachau from comment #10) > (In reply to José Romildo Malaquias from comment #9) > > (In reply to comment #3) > > > > > You may also try to recompile enlightenment without opengl/gles USE-flags > > > (opengl rendering isn't working well anyway). > > > > Recompiling without opengl works, but the composite engine is set to > > software. > > > > Recompiling without gles also works, with the composite engine set to opengl. > > > > So the problem relies with GLES. > > I just added enlightenment-0.17.5_pre1 to the main tree. It should be on > your local rsync mirror in a few hours. Please test it and report, if the > issue is still there. I have recompiled mesa, ecore, evas and enlightenment (0.17.5_pre1) with opengl enabled. Now enlightenment is working in both cases: when compiled with gles enabled or disabled. So it seems that the issue has gone. The only issue I see is a black screen with the old ~/.e directory. If this directory is removed, enlightenment starts without problems.
(In reply to José Romildo Malaquias from comment #11) > (In reply to Thomas Sachau from comment #10) > > (In reply to José Romildo Malaquias from comment #9) > > > (In reply to comment #3) > > > > > > > You may also try to recompile enlightenment without opengl/gles USE-flags > > > > (opengl rendering isn't working well anyway). > > > > > > Recompiling without opengl works, but the composite engine is set to > > > software. > > > > > > Recompiling without gles also works, with the composite engine set to opengl. > > > > > > So the problem relies with GLES. > > > > I just added enlightenment-0.17.5_pre1 to the main tree. It should be on > > your local rsync mirror in a few hours. Please test it and report, if the > > issue is still there. > > I have recompiled mesa, ecore, evas and enlightenment (0.17.5_pre1) with > opengl enabled. Now enlightenment is working in both cases: when compiled > with gles enabled or disabled. So it seems that the issue has gone. > > The only issue I see is a black screen with the old ~/.e directory. If this > directory is removed, enlightenment starts without problems. Can you check, if this is bug 483194 with 0.17.5_pre1? As in removing ~/.e/e/config/standard/e_randr.cfg from the old ~/.e directory removes the black screen?
(In reply to José Romildo Malaquias from comment #11) > I have recompiled mesa, ecore, evas and enlightenment (0.17.5_pre1) with > opengl enabled. Now enlightenment is working in both cases: when compiled > with gles enabled or disabled. So it seems that the issue has gone. Unfortunately enlightenment is not working when compiled with the gles (in the ecore and evas packages) use flag enabled, as I thought it was in my first quick test. It starts well, but a few seconds later the screen becomes black, with some noise white pixels near the left edge. Then a few seconds later the screen is normal again. Then it turns black again, and then normal again, and so on. When evas and ecore are compiled without gles, enlightenment works as expected.
(In reply to Thomas Sachau from comment #12) > (In reply to José Romildo Malaquias from comment #11) > > The only issue I see is a black screen with the old ~/.e directory. If this > > directory is removed, enlightenment starts without problems. > > Can you check, if this is bug 483194 with 0.17.5_pre1? > As in removing ~/.e/e/config/standard/e_randr.cfg from the old ~/.e > directory removes the black screen? Removing ~/.e/e/config/standard/e_randr.cfg does not help. I do not think it is bug 483194. That bug happened in my system too when I updated to 0.17.4, even with no prior ~/.e directory. At that time I just masked that version. Now I am getting a black screen with nothing visible in it.
I just added evas-1.7.9_pre1 and ecore-1.7.9_pre1, please update to those, rebuild enlightenment-0.17.5_pre1 and report, if anything has changed wrt gles support. For the black screen: If you still get that with the old config with the above setup, please open an extra bug for it so we have one bug per issue.
(In reply to Thomas Sachau from comment #15) > I just added evas-1.7.9_pre1 and ecore-1.7.9_pre1, please update to those, > rebuild enlightenment-0.17.5_pre1 and report, if anything has changed wrt > gles support. With evas-1.7.9_pre1, ecore-1.7.9_pre1 and enlightenment-0.17.5_pre1 compiled with support for gles enabled, enlightenment works as expected.
(In reply to Thomas Sachau from comment #15) > For the black screen: If you still get that with the old config with the > above setup, please open an extra bug for it so we have one bug per issue. I have opened a new bug: https://bugs.gentoo.org/show_bug.cgi?id=485268
should retry with the latest versions