Closed GoogleCodeExporter closed 8 years ago
Also input should not go to them.
Original comment by danakj@chromium.org
on 16 Jul 2013 at 1:42
Only override_redirect windows are currently able to show above the lock
screen. Keyboard input will never go to them as we never move the input focus
to an overrideredirect window.
Original comment by reveman@chromium.org
on 16 Jul 2013 at 3:10
I had 2 terminal windows above the login screen.
Try open a terminal and (sleep 10 && xterm) in it, then lock the computer.
Original comment by danakj@chromium.org
on 16 Jul 2013 at 3:15
Are the lock screen and login screen handled the same in Ash? If a managed
window gets input or is placed above the lock screen, that sounds like a
general Ash issue. If it's a login-only issue then I might just mark this as
WontFix as I don't think that's a state you can get to unless deliberately set
up your session to create x windows before login, in which case you're on your
own.
Original comment by reveman@chromium.org
on 16 Jul 2013 at 3:46
I'm not sure.. but would you see the login screen on restart? That was how I
got there.
Original comment by danakj@chromium.org
on 16 Jul 2013 at 4:36
I think that restart should either not show the login screen or kill the X
session completely. The later is probably best.
Original comment by reveman@chromium.org
on 16 Jul 2013 at 4:44
Not clear to me that we should be using the built-in lock screen functionality.
Usage of xlock or similar X11 client is the recommend way to provide screen
locking functionality at the moment. We can reopen this if we decide to use the
built in locking mechanism.
Original comment by reveman@chromium.org
on 19 Aug 2013 at 2:52
Original issue reported on code.google.com by
danakj@chromium.org
on 16 Jul 2013 at 1:41