pitti: I hit this last night after debugging suspend/resume with the sysfs trick to store magic data in the RTC. Upon resuming the laptop clock was obviously full of non-clock data, and was interpreted as somewhen around 2016. Any sudo operation in an existing pty refused to do anything because the timestamps were too far in the future. Opening a new pty allowed me sudo access from there, which I could reset the clock with, using ntpdate.
-- "sudo -k" fails when timestamp is in the future https://bugs.launchpad.net/bugs/43233 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
