This is caused by my recent change to fix bug 428884. I'm slightly
bewildered why we haven't seen issues like this before, as the method I
chose for inhibiting the screensaver is used elsewhere already (eg,
Totem uses the same method when not running under GNOME, for example
when it runs under XFCE).
Anyway, I'll look for a better method to do this this evening
** Changed in: gnome-screensaver (Ubuntu Karmic)
Importance: Undecided => High
** Changed in: gnome-screensaver (Ubuntu Karmic)
Status: New => In Progress
** Changed in: gnome-screensaver (Ubuntu Karmic)
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => In Progress
** Changed in: gnome-screensaver (Ubuntu)
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
** Tags added: regression-update
** Tags removed: blueproximity gnome-screensaver
** Changed in: gnome-screensaver (Ubuntu Karmic)
Milestone: None => karmic-updates
--
gnome-screensaver-command -p triggers keyboard event
https://bugs.launchpad.net/bugs/505789
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
