Correction, I was wrong because I was affected by bug #37750
--
System clock reverts to GMT at boot
https://launchpad.net/bugs/35423
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I was about to report a bug about the time going haywire as well, but I
*think* the problem described in this bugreport is identical to my
problem.
Previous releases of Ubuntu didn't have the Ubiquity Live CD installer.
Those installers used to ask me a question about whether the time was
set to l
Oh, forgot to mention, just like the initial bug reporter, Melissa
Draper, it's also pointless for me if I change the time, because the
change is not permanent.
--
System clock reverts to GMT at boot
https://launchpad.net/bugs/35423
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Actually, I don't think the hwclock was set wrongly at shutdown, because the
hwclock is currently correct, and it would only be set at shutdown if I
understand correctly (and I haven't booted in between).
It might be something broken about the way the system (kernel, initrd,
sysvinit) picks up
Just after the latest updates (kernel ...20 and not much more) I again booted
up with actual GMT displayed as localtime. Seems like ntpdate was not run
either. And probably related, I now had an IP address through dhcp (bug #33968).
The time was maybe set wrongly at shutdown earlier today (after
** Bug 28342 has been marked a duplicate of this bug
--
System clock reverts to GMT at boot
https://launchpad.net/malone/bugs/35423
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
