[Bug 1088495] Re: Onboard Keyboard is sometimes nonresponsive in Raring while unlocking screen

[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.


** Also affects: indicator-session
   Importance: Undecided
       Status: New

** Also affects: gnome-screensaver (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: onboard
       Status: New => Invalid

** Changed in: Ubuntu Raring
       Status: New => Invalid

-- 
You received this bug notification because you are a member of
Accessibility, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1088495

Title:
  Onboard Keyboard is sometimes nonresponsive in Raring while unlocking
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/1088495/+subscriptions