I was a bit too fast, turns out, that openntpd's "adjusting local clock by" message means adjtime(). I've written a small test program to reproduce this bug.
sudo ./test -4 triggers the bug and sudo ./test 0 fixes it after doing the first. The bug can only be triggered with big (i.e. more than one second), negative adjustments. Positive adjustments don't trigger this bug. Attached is the source code for the test program. ** Attachment added: "test program" http://librarian.launchpad.net/4935549/test.c -- [edgy] keyboard broken in X11 on xen dom0 https://launchpad.net/bugs/67519 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
