I'm experiencing this bug in Hardy, due to my real-time clock being set to localtime and my /usr being on an LVM. The bug is usually masked by ntpdate setting the correct time, but whenever I boot my notebook without a network connection, ntpdate can't do its job, and the system time is off by several hours because /usr/share/zoneinfo was not mounted when hwclock.sh was run.
I found out that a simpler workaround than those described above is to add the line export TZ="BRT3BRST,M10.2.0/0,M2.3.0/0" to /etc/default/rcS. Figuring out the correct format for TZ was a pain. I eventually found the above string at the end of my zoneinfo file, America/Sao_Paulo. The funny thing is that, in the 10+ years I've been using Linux, I never had this problem before, because I've always set the real-time clock to UTC, which is supposed to be the best practice. Now I ran into this bug because in Ubuntu the rtc is set to localtime by default (AND because I put /usr on LVM, but I believe this is not an unreasonable thing to do). I should add that for installation I used the Kubuntu 8.04 Alternate Install CD (precisely so I could use LVM). Perhaps the real-time clock is not set to localtime by default in other Ubuntu flavors. In any case, anyone choosing to use rtc on localtime+/usr on LVM is going to have this problem under Hardy (and, perhaps, the current Debian?). -- udev can lead to wrong system time https://bugs.launchpad.net/bugs/160197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
