media-keys: Wait forever for GrabAccelerators() to succeed
On slower machines (esp. with tracker and/or dropbox starting on login)
this may take more than the usual timeout of ~25 seconds.
We cannot use the existing retry loop here – in this bug, the first call
actually *succeeds* from gnome-shell's side, even if gsd-mediakeys gives
up on waiting for the reply.
So if we called GrabAccelerators again, we would receive no accel IDs
(because all keys are duplicates), and gnome-shell would keep sending
AcceleratorActivated signals with accel IDs that the 1st call has
established – resulting in exactly the same "Could not find accelerator
for accel id" as we're trying to fix.
7158ff1...
by
GNOME Translation Robot <email address hidden>
Update Scottish Gaelic translation
6077ded...
by
Benjamin Berg <email address hidden>
power: Correctly test lid related suspend inhibitions
The test was trying to verify that no suspend action happened. However,
this cannot happen during testing, as the suspend action for lid close
is not done by gsd-power. So instead just verify that the lid switch
inhibition works as expected.
75b331e...
by
Benjamin Berg <email address hidden>
power: Keep screen off while screensaver is on when adding inhibitors
When a new idle inhibitor is added then the state needs to be forced to
normal mode even when the user is idle. However, this should not happen
if the screensaver is active at the time.
dee9a77...
by
Benjamin Berg <email address hidden>
common: Work around output buffering for g_debug
During testing debug output is enabled using --verbose.
Unfortunately the default logging handler in GLib is not flushing the
utput stream for each log message. In addition, the default buffering
for stdout seems to be block based (not line based) if stdout is not a
TTY.
This causes the log message to get stuck in the buffer and the tests
cannot read them.
