By the way in Window Maker (which used to have problems with it, too) it works.

Thank you for this insight. So I "accidentally" picked WMs which happened to work with this. It is indeed very frustrating.

Thank you, unchecking the monitor hotplug option helps (but of course this is more of a workaround). I am not sure whether this is really a problem outside of e's code, since other WMs don't exhibit this problem (while still reacting on such events).

Just in case it helps I have run through the sequence again and created a sequence of e output logs.

In T8217#150609, @raster wrote:

in this case the xrandr tool will not be very helpful. the stdout log from e will be. the likes starting with RRR specifically. does x report screens chnanging/being plugged/unplugged before/after suspend/resume in the log? what does it say?

In T8217#150602, @ProhtMeyhet wrote:

Sorry, I noticed this comment a bit late. Here's the output you were asking for.

I have not really checked, but it looks like I have not had any of those problems for quite some time. So maybe we can close this (and reopen if it reoccurs).

I have found out that an easy way to reproduce the problem is to run enlightenment with two screens and then switch one screen off. At least with the screens I am using (see above) I always run into it and need to restart enlightenment (after that things are fine again).

I can confirm that the problem still persists with EFL 1.23.1 and enlightenment 0.23.1.

It just turned out that the problem is not yet solved. Reopening this.

It looks like with the update to efl-1.22.5 / enlightenment-0.23.0 the problem has been fixed.

OK, so I'll wait for the next minor release and check again.

I was using my system password. Actually I've just rerun the build of 0.22.2 and went through the build log. On my box pam-devel is and was installed (and found by e's configure, and library linked). At the moment I cannot reinstall e (I may at the end of this week) to try again, but I don't really expect anything new.

In T6779#112121, @mbert wrote:

No, I am now using 0.22.1 again, built on the same box. Lock/unlock works as expected.

In T6779#112122, @raster wrote:

have you tried it with an incorrect password?

In T6779#112115, @raster wrote:

ok. found out why - you're missing libpam dev/devel pkgs. e's build auto-enables pam if found, otherwise disables.

I'm afraid this is not easy for me since I have recovered from that crash since and e is now running stable again. Running it in valgrind all the time is of course not an option for a machine I use for my daily work :)

Still having trouble with my monitors. Having switched things about for a couple of time I got into a situation where e would crash each time I logged in from gdm. Here's my crashdump file.

So here it is.

In T6621#109707, @zmike wrote:

Can you upload your config profile?

With e22 the problem has not disappeared but improved slightly. I cannot really dig any deeper for now, so I will most likely not be able to give more input. Hence closing this will probably be the best option.

I have been observing my system and trying to reproduce this for some weeks now, and the problem never occurred again.
Since at that time I had some problems with my graphics driver, I assume that this was not a bug in e and close this taks now.

Installed the debug package now. However at the moment I am unable to trigger the crash at this moment. I will upload another crash dump as soon as the crash occurs again.

Not sure if I understand this right.
I install Enlightenment as rpm which I build from the latest sources.
I have not had this issue until recently.
The problem is not limited to one theme alone, actually it occurs with a good number of themes.

Here it is.

Where would I find this?

In T6001#97910, @zmike wrote:

Can you describe your exact process for installing and enabling the theme so that I can be sure to use the same steps for testing?

enlightenment-0.20.5-13.el7.x86_64

Sure.

I've been using 0.20.5 since this morning and have not been able to reproduce the error. Looks like it's been fixed, thank you!

See strace output here:

Having tried to downgrade to 0.20.1 I find that the problem seems to be in that version, too.