Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[xenial] Terminal keyboard can't be summoned after unlocking #595
Steps to reproduce
Open the Terminal app. Lock the device. Unlock the device. Try to summon the OSK with the button.
Keyboard doesn’t appear, regardless of how many times the button is tapped.
Logfiles and additional information
Sometimes summoning the launcher by swiping from the left edge or creating a new terminal window solves the problem, but this doesn’t seem to work 100% of the time.
Happens on my Hammerhead Xenial (r383). Reproduced as follows: Lock the screen with the keyboard active (displayed), apps tested Telegram (sending a message), System Settings (Switch to passphrase) and Openstore (search). Unlock the screen screen frozen, reboot required to restart. The underlying OS is still running as I can connect (adb shell, clickable shell) and run top, etc.
referenced this issue
May 17, 2018
Updated to r387 based on #606 and tested. On Openstore webapp>Search keyboard appears, lock screen, unlock screen. Keyboard gone but does reappear after a few taps. Same thing happens on System Settings test. On Telegram test the keyboard does not appear at all - doh.
Update: I know the issue was opened indicating the
Something I didn't notice the last time: it appears that this issue only occurs if the keyboard was visible before locking. If I dismiss the OSK before locking the device, then unlock and summon it again, it does appear.
Perhaps it's caused by something about keyboard state? It appears that summoning the OSK fails when the keyboard was previously visible. The workarounds I mentioned in my original post are all cases in which the OSK would be dismissed.
I've been having this issue. As a new user I wound up here and after some quick testing the keyboard visibility sure seems to be the problem.
I'm having trouble in the messaging app too and couldn't figure out why I didn't have this trouble for the first few days using UT. Then I remembered that's about when I first set a screen lock code.
Sure enough setting a passcode seems to trigger this bug. So...
with Passcode set: