desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #124936
[Bug 786901] Re: Screensaver sometimes doesn't start
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: xorg-server (Ubuntu Lucid)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/786901
Title:
Screensaver sometimes doesn't start
Status in xorg-server package in Ubuntu:
Fix Released
Status in xorg-server source package in Lucid:
Won't Fix
Bug description:
There is a problem with gnome-screensaver on Ubuntu 10.04 Lucid LTS.
Sometimes the screensaver doesn't start and doesn't lock the screen
after the idle timeout. A semi-reliable way how to trigger this bug is
to move the mouse during fade-out before the screensaver kicks in. On
the next idle timeout, screensaver doesn't start anymore.
This is a security issue, because it leaves the computer unlocked.
I found out that the problem is in the xserver-xorg-core package, in
particular in the file Xext/sync.c. The xserver sometimes doesn't fire
the alarm event. I looked at the upstream repository and the Maverick
patches. The following two patches solve the problem for me:
205_fix-bracket-values.patch (from upstream)
206_fix-neg-sync-transition.patch (from Maverick)
These patches are included in Maverick and Natty, so the only affected
release is Lucid.
Related:
The same bug in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=566351
Upstream patches: http://cgit.freedesktop.org/xorg/xserver/log/Xext/sync.c
Related bug: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/595555
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/786901/+subscriptions