Just for the sake of helping a guy out, even though answering what could be called support requests isn't strictly bug tracker stuff... well, at least it serves to illustrate the issues faced.
Vincenzo: Workarounds exist, the most troublesome of which would probably be using a rescue-CD to get access to the files needed.
Now, the timestamps get stored as root-only-accessible files in /var/run/sudo/yourusername/, and removing them manually will invalidate the timestamps, as I briefly mentioned in my initial report. You could try using sudo from another tty (Ctrl-Alt-F1 through F6), or from another shell in X to remove these files. This should allow you to use sudo normally, at least until your clock breaks again. ;-)
(Using graphical approaches, e.g. a root-mode file manager, to get root access to the files will probably work, too - I haven't checked how e.g. kdesu or gksudo use/store timestamps.)
Just for the sake of helping a guy out, even though answering what could be called support requests isn't strictly bug tracker stuff... well, at least it serves to illustrate the issues faced.
Vincenzo: Workarounds exist, the most troublesome of which would probably be using a rescue-CD to get access to the files needed.
Now, the timestamps get stored as root-only- accessible files in /var/run/ sudo/youruserna me/, and removing them manually will invalidate the timestamps, as I briefly mentioned in my initial report. You could try using sudo from another tty (Ctrl-Alt-F1 through F6), or from another shell in X to remove these files. This should allow you to use sudo normally, at least until your clock breaks again. ;-)
(Using graphical approaches, e.g. a root-mode file manager, to get root access to the files will probably work, too - I haven't checked how e.g. kdesu or gksudo use/store timestamps.)