Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 462732 - x11-wm/enlightenment-0.17.1 with media-libs/mesa-9.1* hangs during splash
Summary: x11-wm/enlightenment-0.17.1 with media-libs/mesa-9.1* hangs during splash
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: enlightenment+disabled
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-22 23:01 UTC by José Romildo Malaquias
Modified: 2015-03-17 02:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Output of "emerge --info" (emerge.info.txt,16.40 KB, text/plain)
2013-03-22 23:01 UTC, José Romildo Malaquias
Details
enlightenment_start.log (enlightenment_start.log,1.91 KB, text/plain)
2013-03-25 11:35 UTC, José Romildo Malaquias
Details
.xsession-errors (.xsession-errors.e,796 bytes, text/plain)
2013-03-25 11:36 UTC, José Romildo Malaquias
Details
Xorg.0.log (Xorg.0.log.e,42.02 KB, text/plain)
2013-03-25 11:36 UTC, José Romildo Malaquias
Details

Note You need to log in before you can comment on or make changes to this bug.
Description José Romildo Malaquias 2013-03-22 23:01:52 UTC
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.
Comment 1 Peter Volkov (RETIRED) gentoo-dev 2013-03-24 08:15:26 UTC
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/ ?
Comment 2 José Romildo Malaquias 2013-03-24 16:28:40 UTC
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.
Comment 3 Petr Polezhaev 2013-03-25 10:57:09 UTC
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).
Comment 4 José Romildo Malaquias 2013-03-25 11:34:39 UTC
(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.
Comment 5 José Romildo Malaquias 2013-03-25 11:35:33 UTC
Created attachment 343220 [details]
enlightenment_start.log
Comment 6 José Romildo Malaquias 2013-03-25 11:36:11 UTC
Created attachment 343222 [details]
.xsession-errors
Comment 7 José Romildo Malaquias 2013-03-25 11:36:44 UTC
Created attachment 343224 [details]
Xorg.0.log
Comment 8 José Romildo Malaquias 2013-03-25 11:38:54 UTC
(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.
Comment 9 José Romildo Malaquias 2013-03-29 09:47:44 UTC
(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.
Comment 10 Thomas Sachau gentoo-dev 2013-09-15 11:01:22 UTC
(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.
Comment 11 José Romildo Malaquias 2013-09-15 14:04:23 UTC
(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.
Comment 12 Thomas Sachau gentoo-dev 2013-09-15 14:13:12 UTC
(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?
Comment 13 José Romildo Malaquias 2013-09-16 18:01:10 UTC
(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.
Comment 14 José Romildo Malaquias 2013-09-16 18:07:27 UTC
(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.
Comment 15 Thomas Sachau gentoo-dev 2013-09-17 14:47:14 UTC
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.
Comment 16 José Romildo Malaquias 2013-09-18 08:31:47 UTC
(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.
Comment 17 José Romildo Malaquias 2013-09-18 08:44:02 UTC
(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
Comment 18 SpanKY gentoo-dev 2015-03-17 02:27:25 UTC
should retry with the latest versions