This bug was fixed in the package gnome-screensaver - 2.28.0-1ubuntu5
---------------
gnome-screensaver (2.28.0-1ubuntu5) lucid; urgency=low
[ Chris Coulson ]
* debian/patches/10_legacy_scrsvr_inhibit.patch:
- Re-write to not use XTest to simulate fake key-presses in order
to reset the IDLETIME counter, as this appears to be problematic.
Use XResetScreenSaver() to do this instead. Thanks to Reinhard
Tartler for the hint (LP: #505789)
* Drop debian/patches/90_autotools.patch - no longer needed
* Dropped debian/patches/08_gs_dialog_request_to_exit.patch - this is
fixed by this commit in gtk: 0748cf563d0d0d03001a62589f13be16a8ec06c1,
so there is no need to carry this patch any more.
* Drop debian/gconf-defaults:
- Use upstream default for lock_enabled (locking on screensaver
activation)
- user_switch_enabled is already set to the upstream default
[ Marc Deslauriers ]
* Added apport hook:
- debian/source_gnome-screensaver.py
- debian/gnome-screensaver.install
-- Chris Coulson <chrisccoul...@ubuntu.com> Tue, 19 Jan 2010 17:46:56 +0000
** Changed in: gnome-screensaver (Ubuntu)
Status: In Progress => Fix Released
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
