fluendo-isv team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

Looks to me like either path really should work -- ScreenSaver sends
signals on the correct path, and there is no indication anywhere that it
would be listening on straight /. However, it seems like indicator-
session also calls methods on / for locking the screen, for example...

Trying to call the Inhibit method with either path appears to work fine
on the CLI (I get a cookie back). Can you see exactly in which way
things fail if you inhibit using /org/gnome/ScreenSaver in your code?

-- 
screensaver is not inhibited
https://bugs.launchpad.net/bugs/674314
You received this bug notification because you are a member of Fluendo,
which is a direct subscriber.

Status in Canonical and Fluendo collaberation project: New

Bug description:
The screensaver isn't getting inhibited while a movie is playing in fullscreen mode.