https://bugzilla.redhat.com/show_bug.cgi?id=984333
David Gibson dgibson@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dgibson@redhat.co | |m) |
--- Comment #22 from David Gibson dgibson@redhat.com ---
Installing xmonad isn't user friendly. Why are the 2 needed yum/dnf groups in comps unvisible?
I can't answer that.
Anyways, it runs in a f21 VM now.
Ok, as noted above, I'm still seeing the problem with f22.
But i couldn't reproduce the issue until yet. So, some more questions: Does it only happens if the session is looked?
Sorry, I don't understand that question.
Do i need to wait longer, ie 2 hours or 6 hours, before i try to unlock the session?
No, I've rarely left the session locked that long, and I've frequently hit the problem when it has only been locked for seconds.
Does it happens when the box boot from hibernate/suspend state?
When I resume from suspend-to-ram, I think the problem has sometimes happened, but certainly not more frequently than any other time.
I'm not regularly using hibernate at the moment, so I don't know about that.
I tested it also on bare metal several times, no luck. Which graphic are you using?
I'm using Intel Graphics on a Thinkpad T520.
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
I also encountered the problem on my previous laptop, which was a Thinkpad X230, also with Intel graphics.
I tested it with nvidia driver from rpmfusion.
I don't have any nvidia machines I could cross test with.
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.
haskell-devel@lists.fedoraproject.org