I am not sure if my issue would have the same bug report number or not
but I did a search and this bug is very close to the same issue I am
having. I am using dual boot with grub2, windows 7 and Ubuntu Mate 17. I
mainly use windows and the clock works fine reboot after reboot no
issues, and when I
trollord: set "UTC=no" in /etc/default/rcS. This setting will make
Ubuntu read and write to the hardware clock in localtime, rather than
UTC. Windows does the same by default, and thus you won't have problems
with them fighting over the clock's timezone. This is the default (in
Intrepid and Jaunty,
** Changed in: ntp (Ubuntu)
Sourcepackagename: None => ntp
Assignee: Brian Murray (brian-murray) => (unassigned)
Status: Incomplete => New
--
Windows dual-boot can corrupt system clock even if time servers are enabled
https://bugs.launchpad.net/bugs/97722
You received this bug notific
Brian, this happens still, even with for instance Hardy+Vista
combination. Windowses seem to use local time set to the hardware clock
whereas at least I usually have UTC on the Linux side. Every visit to
Windows and coming back really does move clock for 2 hours (I am at
UTC+2).
What I would do is
Not an issue for me, since I am not dual-booting anymore; however, it
could be for anyone who does. But I could not check if it was still a
problem this autumn. I didn't even have a machine. :)
But I do not think it should be that difficult to test. Just set the
clock to auto, and change the time
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in recently. We were wondering if this is still and issue
for you? Thanks in advance.
** Changed in: ubuntu
Assignee: (unassigned) => Bri
