Forwarded from: https://launchpad.net/distros/ubuntu/+source/gnome-screensaver/+bug/20070

After the daily limit is reached, I click on "Lock" to lock the screen. The
next day, I unlock the screen. Workrave doesn't refresh, it just hangs, with
input still blocked. (There's a grey patch where the dialog box used to be.) I
have to kill it from outide X to regain access to the desktop.

This only seems to be a problem if I wait until the next day. If I try
unlocking immediately, the dialog box comes back and I can "Skip" or "Postpone".
 This behaviour seems normal.

After logging in the next day, shouldn't the dialog box go away, the input be
unblocked, and the timers reset?

This should rather have been: https://launchpad.net/distros/ubuntu/+source/workrave/+bug/20070 (anyway, same bug).

This bug has been fixed in 1.8.3:

** Workrave no longer consumes 100% CPU is if a break is started while
   the screen is locked.

If you press lock in the restbreak windows, Workrave releases its mouse and keyboard grab. This allows the screensaver to obtain a grab. Workrave then periodically attempts to regain the grab (in case the screen saver was terminated). Because of a bug, the numbers of grab attempts increased exponentially over time causing workrave to use 100% cpu time after a while...