ubuntu-x-swat team mailing list archive

[Unonium <786901@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  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 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 from me:
+ 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: LP #595555

** Description changed:

  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 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: LP #595555
+ Related bug: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/595555

** Description changed:

  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 the xserver-xorg-core package, in
+ 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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/786901

Title:
  Screensaver sometimes doesn't start