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 #23 from Wolfgang Ulbrich chat-to-me@raveit.de --- (In reply to David Gibson from comment #22)
Ok, as noted above, I'm still seeing the problem with f22.
For some reasons xmonad-mate didn't start in my f22 VM.
Another thought occurred to me: I also have workrave installed. I don't know if it is relevant, but it's possible. Often mate-screensaver activates when I am taking a workrave enforced rest break. I'm pretty sure I've had this problem occur other times as well, but I'm not certain.
After installing xmonad-mate on my notebook MSI FX600 with intel graphic i could reproduce the issue after a long day of testing. Late in evenning i couldn't unlock the session anymore. Running 'journlctl -b 0 -f --no-tail' shows me that the fprintd.service was running. This is complete weird/bad because my notebook doesn't have a fingerprint-reader. After stoping the service i could unlock the session :)
fprintd.service is a static service wich will call by another service if needed, so i tried to mask the service. But today i run in the issue again, so masking the service isn't enough. Dbus tried to load the mask service, which failed of course. But the lookscreen was unselectable again. Reason enough to uninstall unneeded fprintd. Now the lookscreen works until yet.
So the question is why is fprintd.service running on a system w/o a hardware for it, and which other service or appliction call it?
Looks for me more like a fprintd or maybe a systemd issue.
Can confirm that uninstalling fprintd helps?