/etc/default/rcS: UTC=no is being ignored

Bug #1377698 reported by Doug McMahon
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Fix Released
High
Martin Pitt

Bug Description

This causes the greeter time to display utc & sets system time to utc
Affects users who are in a different timezone
Also affects users who dual boot with windows, their time will be off by amount different from utc to their time zone

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: initscripts 2.88dsf-41ubuntu18
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 5 14:16:48 2014
InstallationDate: Installed on 2014-10-05 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
SourcePackage: sysvinit
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.rcS: 2014-10-05T10:58:21.042693

Revision history for this message
Doug McMahon (mc3man) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sysvinit (Ubuntu):
status: New → Confirmed
Revision history for this message
sgage@tds.net (sgage) wrote :

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 automatic time synch enabled fixed the time before a clock was ever displayed - for me, the problem only showed up when I dual-booted over to Windows, or turned off the auto-sync.

Revision history for this message
Steve Langasek (vorlon) wrote :

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 ill-conceived change in Debian to move the UTC setting into /etc/adjtime, which we *DO NOT NEED AT ALL* and should not have in Ubuntu.

affects: sysvinit (Ubuntu) → util-linux (Ubuntu)
Changed in util-linux (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → High
status: Confirmed → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

Ah, I see. "service" drops a .sh extension for masking by a systemd unit, but not by an upstart job.

Martin Pitt (pitti)
Changed in util-linux (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

Fix uploaded, waiting for RT review.

Changed in util-linux (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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
    that). (LP: #1377698)
  * debian/util-linux.postinst: Remove /etc/adjtime again on upgrades to this
    version, we don't want it in Ubuntu. This can be removed after utopic, it
    only affects intra-utopic upgrades.
 -- Martin Pitt <email address hidden> Tue, 07 Oct 2014 15:10:44 +0200

Changed in util-linux (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Attila Hammer (hammera) wrote :

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)
Because I using both Ubuntu and Windows, I set UTC=no setting into /etc/default/RCS file.
Because now happened a time zone change (I using Europe/budapest timezone), I ran hwclock -w --localtime command.
Next clock change need in europe/budapest timezone with 2015. last march sunday.

Attila

Revision history for this message
Martin Pitt (pitti) wrote :

> Not need applying a similar fix with Ubuntu Trusty?

No, this was introduced in utopic.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.