Bug 7794

Summary:	oclock: better behaviour wrt date change
Product:	xorg	Reporter:	john <johnsmith7219>
Component:	App/other	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED INVALID	QA Contact:	Xorg Project Team <xorg-team>
Severity:	enhancement
Priority:	high	CC:	jeremyhu
Version:	unspecified	Keywords:	love
Hardware:	All
OS:	Linux (All)
Whiteboard:	2011BRB_Reviewed
i915 platform:		i915 features:

Description john 2006-08-07 02:57:59 UTC

When a new date is set on the system clock (with date --set, or by ntpd for
instance), it would be very nice if there was a way to make oclock take it into
account (for instance sending a SIGHUP).  Currently the only solution (as far as
I know) is to kill oclock and run a new one.

Comment 1 Daniel Stone 2007-02-27 01:33:07 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 2 Adam Jackson 2018-06-12 19:10:41 UTC

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

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.