[Bug 72430] New: alock fails to blank screen with SNA on Intel HD 4600
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Dec 7 03:55:57 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=72430
Priority: medium
Bug ID: 72430
Assignee: chris at chris-wilson.co.uk
Summary: alock fails to blank screen with SNA on Intel HD 4600
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: All
Reporter: Andreas.Klauer at metamorpher.de
Hardware: Other
Status: NEW
Version: unspecified
Component: Driver/intel
Product: xorg
Created attachment 90405
--> https://bugs.freedesktop.org/attachment.cgi?id=90405&action=edit
alock showing desktop when it should stay blank
Using the current (as of now) git drivers on a i5-4570, Gentoo ~amd64.
alock ( http://code.google.com/p/alock/ version 94 ) is a xscreensaver
alternative, which locks and blanks (black) the screen. When you press enter,
it shows a green border around the black screen. Then you enter your password
(no other prompt shown) and the screen is unlocked. If you got the password
wrong, the green border turns red and you have to wait a bit for the next
attempt.
With current intel drivers in SNA/Tearfree mode, the behaviour is as follows:
1. You lock the screen using "alock -auth passwd -bg blank"
2. Screen goes black.
3. You press enter.
4. Screen shows a green border around an old still image of the desktop
contents.
5. You enter your password.
6. Desktop is unlocked and old image is updated to current one.
What should happen is that the screen stays black (apart from the green border)
in step 4. This works fine in UXA mode, and with non-intel driver, so I assume
it's a driver specific issue.
Of course it could be a bug in alock that only appears in Intel/SNA mode for
some reasons?!
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20131207/6b887d68/attachment.html>
More information about the intel-gfx-bugs
mailing list