Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen

[Sean Feole]

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.

[marmuta (marmuta)]

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.

[marmuta (marmuta)]

So no, Onboard isn't the cause. The unlock dialog's buttons still lock up when Onboard isn't embedded into the screensaver.

The ultimate cause most likely lies within gnome-screensaver itself, there is a lot of pointer grabbing going on during normal operation. However, the trigger seems to be the way indicator-session locks the screen. I can reproduce the lockups pretty reliably, on desktop and Nexus 7, with:

dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity

They seem to disappear with adding a one second delay between those calls:

dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock; sleep 1; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome ScreenSaver org.gnome.ScreenSaver.SimulateUserActivity

I'll link them both for now, gnome-screensaver and indicator-session. They'll be better able to sort this out.

[Rolf Leggewie (r0lf)]

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".