I just had this happen to me on a fresh edgy install of a Lenovo T60.
The network didn't come up during install (ipw3945 couldn't auto-detect
the office wifi). So post-install, I brought the network up by pointing
it at the right ESSID. At that point ntpdate helpfully slewed the
clock by -28805 seconds and sudo promptly went onstrike on any existing
ttys.
Either we shouldn't slew time so drastically or core system tools like
sudo shouldn't break when we do.
** Changed in: sudo (Ubuntu)
Status: Rejected => Confirmed
--
Changing time could lock you out of the machine
https://launchpad.net/bugs/24217
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
