Public bug reported:
Binary package hint: gnome-screensaver
gnome-screensaver misinterprets arbitrary clock changes as being periods
of inactivity. Hence, when changing the clock in the forward direction
for more than the configured timeout, the screensaver launches.
This is a rather minor bug, I admit, but I encounter this all the time
because my motherboard battery is dead and I have to resync every bootup
:)
** Affects: gnome-screensaver (Ubuntu)
Severity: Minor
Priority: (none set)
Status: Unconfirmed
** Changed in: gnome-screensaver (Ubuntu)
Severity: Normal => Minor
--
Misinterpretation of an NTP sync as "idle activity"
https://launchpad.net/bugs/48183
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs