Not need applying a similar fix with Ubuntu Trusty?
No, this was introduced in utopic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377698
Title:
/etc/default/rcS: UTC=no is being ignored
To
Not need applying a similar fix with Ubuntu Trusty? Ubuntu Trusty handle good
the UTc=no setting?
Possible I missunderstand the issue, but if I get dmesg|grep clock command, I
see following style output:
[1.348720] rtc_cmos 00:02: setting system clock to 2014-10-26 14:54:33 UTC
(1414335273)
This is a regression in the util-linux package in 14.10. When built
with the current debhelper, /etc/init.d/hwclock.sh is installed
alongside /etc/init/hwclock.conf, and is not masked out by the system;
and this init script has broken handling of the $UTC setting entirely.
This is courtesy of an
Ah, I see. service drops a .sh extension for masking by a systemd
unit, but not by an upstart job.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377698
Title:
/etc/default/rcS: UTC=no is being
** Changed in: util-linux (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377698
Title:
/etc/default/rcS: UTC=no is being ignored
To manage
Fix uploaded, waiting for RT review.
** Changed in: util-linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377698
Title:
/etc/default/rcS:
This bug was fixed in the package util-linux - 2.25.1-3ubuntu2
---
util-linux (2.25.1-3ubuntu2) utopic; urgency=medium
* Add debian/util-linux.hwclock.sh.upstart: Mask /etc/init.d/hwclock.sh, as
we don't want to run this under upstart (we already have hwclock.conf for
The bug appears to me like this:
Even with UTC=no, Ubuntu stores the time as UTC at shutdown. But since
UTC=no, it expects the time as local, thus applies no timezone
correction, and the time is 4 hours fast for those in EDT country.
Took me the longest time to suss it out, since having
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sysvinit (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377698
Title:
