Not being able to press [enter] after X windows lock screen has been activated

[thjwong]

Hi Nix,

I found this app super handy to control my Pi remote. Thanks for your work.
There is a problem / question about using it:

I activated fauxcon from ssh and ran startx from the console. After the X session stayed idle for a while, the blank screen came up and I was asked to provide my password to unlock the X session again. However, there is no way to press [enter] to execute the login, and the [Tab] as well as arrow keys do not work either so that I could not navigate to any of the [Leave message], [Cancel], [Unlock] buttons. What I say that [Tab] and arrow keys do not work on that screen - they actually made the screen turn blank again.

Can you point me the solution or work around?
Thanks in advance.

• J

[thjwong]

note: it would be really nice I can still input all the shortcut key combinations within X or within kodi, i.e. Ctrl, Alt, Shift, Tab, Win/Super, Esc, Arrow-keys, especially when some applications (e.g. emacs) need many key combinations to work.

[lornix]

Hmmm... I'm using the absolute simplest method to read from local keyboard
and write to remote, so some key combinations just won't work (ctrl-alt-A,
for example).

I've been considering requiring the keyboard routine to use & transmit
scancodes, a little bit more overhead, but would be worth it since it would
allow full keyboard emulation.

Off to the drawing board...

Loni
On Feb 14, 2016 2:02 PM, "thjwong" notifications@github.com wrote:

note: it would be really nice I can still input all the shortcut key
combinations within X or within kodi, i.e. Ctrl, Alt, Shift, Tab,
Win/Super, Esc, Arrow-keys, especially when some applications (e.g. emacs)
need many key combinations to work.

—
Reply to this email directly or view it on GitHub
#1 (comment).