Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Screensaver |
Expired
|
High
|
|||
Onboard |
Invalid
|
Undecided
|
Unassigned | ||
Session Menu |
New
|
Undecided
|
Unassigned | ||
ubuntu-nexus7 |
Confirmed
|
Undecided
|
Unassigned | ||
gnome-screensaver (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned | ||
onboard (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Raring |
Invalid
|
High
|
Unassigned |
Bug Description
Ubuntu: 13.04
Platfrom: Nexus7
I was able to reproduce this a few times over the weekend. After locking the screen from System Menu -> Lock, Touch the screen to prompt for the password dialog and try to issue your password and press unlock.
1.) Lock Screen from system Menu
2.)(optional) allow display to go black.
3.) Touch display to prompt for password box
4.) try to issue password and hit Unlock
5.) Repeat this step at least 5 times
If you don't see the issue immediately repeat the steps above , I usually encountered the issue within 3 attempts. When the problem did occur, allow the device to timeout and re-blank the screen. Touch the display again and at this time I have experienced that Onboard will work as expected.
summary: |
- Onboard Keyboard does not work in Raring while unlocking screen + Onboard Keyboard is sometimes nonresponsive in Raring while unlocking + screen |
Changed in ubuntu-nexus7: | |
assignee: | nobody → Canonical Desktop Team (canonical-desktop-team) |
Changed in onboard (Ubuntu): | |
importance: | Undecided → High |
affects: | onboard (Ubuntu Raring) → Ubuntu Raring |
affects: | Ubuntu Raring → onboard (Ubuntu Raring) |
Changed in gnome-screensaver: | |
importance: | Unknown → High |
status: | Unknown → New |
tags: | added: raring |
Changed in ubuntu-nexus7: | |
assignee: | Canonical Desktop Team (canonical-desktop-team) → nobody |
Changed in gnome-screensaver: | |
status: | New → Expired |
Confirming, I've seen this too. However I'm not convinced yet this is Onboard's doing. When it happens here, the whole screen becomes unresponsive, including the buttons of the unlock dialog. This doesn't happen when I plug Onboard into any other XEmbed socket. Not saying Onboard is necessarily innocent, but I'd start debugging in gnome-screensaver. If I find the time I'll have a look.