https://bugzilla.redhat.com/show_bug.cgi?id=984333
Wolfgang Ulbrich chat-to-me@raveit.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dgibson@redhat.co | |m)
--- Comment #21 from Wolfgang Ulbrich chat-to-me@raveit.de --- Installing xmonad isn't user friendly. Why are the 2 needed yum/dnf groups in comps unvisible? Anyways, it runs in a f21 VM now. But i couldn't reproduce the issue until yet. So, some more questions: Does it only happens if the session is looked? Do i need to wait longer, ie 2 hours or 6 hours, before i try to unlock the session? Does it happens when the box boot from hibernate/suspend state?
I tested it also on bare metal several times, no luck. Which graphic are you using? I tested it with nvidia driver from rpmfusion. But sorry, i can't use xmonad on my main box whole the day for testing more ;) But it seems you're not alone, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785739
PS: you can try out latest mate-screensaver build which have improvements for systemd-login. https://bodhi.fedoraproject.org/updates/FEDORA-2015-5b345be5b9