Ubuntu
gnome-screensaver package

  1. Bug #1088495
  2. Comment #2

Comment 2 for bug 1088495

Revision history for this message
marmuta (marmuta) wrote :

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.