Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[xenial] Terminal keyboard can't be summoned after unlocking #595

Open
Arc676 opened this issue May 13, 2018 · 8 comments

Comments

7 participants
@Arc676
Copy link

commented May 13, 2018

  • Device: Nexus 5 hammerhead
  • Channel: 16.04 devel
  • Build: r367

Steps to reproduce

Open the Terminal app. Lock the device. Unlock the device. Try to summon the OSK with the button.

Expected behavior

Keyboard appears.

Actual behavior

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.

@Arc676

This comment has been minimized.

Copy link
Author

commented May 13, 2018

Still happens on r377.

@NeoTheThird NeoTheThird added bug and removed needs confirmation labels May 13, 2018

@NeoTheThird NeoTheThird added this to the 16.04 Backlog milestone May 13, 2018

@NeoTheThird NeoTheThird added this to Accepted in Ubuntu Touch May 13, 2018

@floop2002

This comment has been minimized.

Copy link

commented May 17, 2018

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.

@floop2002

This comment has been minimized.

Copy link

commented May 17, 2018

I can retrieve log files if some one could identify which ones may show relevant information

@floop2002

This comment has been minimized.

Copy link

commented May 18, 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.

@Arc676

This comment has been minimized.

Copy link
Author

commented Sep 2, 2018

Update: I know the issue was opened indicating the devel channel, but I'd like to note that this still happens after updating to OTA-4 on stable (congrats btw).

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.

@mariogrip mariogrip modified the milestones: 16.04 OTA-5, 16.04 OTA-6 Oct 1, 2018

@mariogrip mariogrip modified the milestones: 16.04 OTA-7, 16.04 OTA-8 Dec 29, 2018

@giiba

This comment has been minimized.

Copy link

commented Apr 13, 2019

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:

  • keyboard visible on locking = problems
  • keyboard hidden before locking = keyboard fine

remove Passcode:

  • no problems regardless of visibility
@Danfro

This comment has been minimized.

Copy link

commented Jun 1, 2019

Using E5 on release channel (16.04 2019-W22)

I had this issue too. Now I can not reproduce it any more. It seems to be fixed with one of the last updates.

Can anyone confirm that this is solved or if this issue does still remain?

@Arc676

This comment has been minimized.

Copy link
Author

commented Jun 1, 2019

Updated to 2019-06-01/2 on Hammerhead on devel channel. Can confirm that locking the device while the OSK is visible in Terminal still prevents the keyboard from being summoned upon unlocking. Tapping the "change tab" button and reselecting the same terminal still works as a workaround; the OSK can be summoned when the terminal regains focus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.