Bug 26469 - Multiple xsync timers fail to fire
Summary: Multiple xsync timers fail to fire
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.5 (2009.10)
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard: 2011BRB_Reviewed
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-08 04:42 UTC by Ross Burton
Modified: 2018-12-13 22:22 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Ross Burton 2010-02-08 04:42:27 UTC
gnome-screensaver 2.25.1 uses the sync extension in xext to detect idle. It installs multiple alarms so that it can fade the screen without locking and then lock after a few seconds, allowing the user to notice the fade and cause activity without having to unlock.

However, with xorg 7.5 (replicated with both xserver 1.7.3 and .4) only the initial alarm fires.

To replicate, download gnome-screensaver 2.25.2 from:

http://ftp.acc.umu.se/pub/GNOME/sources/gnome-screensaver/2.25/gnome-screensaver-2.25.2.tar.gz

Then configure, make, and run src/test-idle-monitor.  This installs three timers at 2.5s, 5s and 10s.  Only the 2.5s time will fire.
Comment 1 Jeremy Huddleston Sequoia 2011-10-06 11:11:30 UTC
Is this still an issue?  Was this behaving as you expected in an earlier server 
or libXext?  If so, what was the last version that behaved that way?
Comment 2 Adam Jackson 2018-07-30 15:46:41 UTC
Whatever these bugs are, they are probably not libXext's fault.
Comment 3 GitLab Migration User 2018-12-13 22:22:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/390.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.