Comment 3 for bug 432229
Revision history for this message
| Roland Hughes (original-seasoned-geek) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
As of today, one of the update sets which came out seems to have fixed this. There is still a lot of fall out with the problems it created, but the clock/future date problem at boot up seem to be gone.