/etc/default/rcS replacement is prompted during raring to saucy upgrade

[Para Siva]

Replacement of /etc/default/rcS is prompted during upgrades of raring desktop to saucy. The file was not manually modified before the upgrade. This was on a fresh raring install being upgraded to saucy. Occurrs with both amd64 and i386.

The diff being notified at the prompt is,

--- /etc/default/rcS 2013-05-22 11:42:53.653107814 +0100
+++ /etc/default/rcS.dpkg-new 2013-05-16 06:06:50.000000000 +0100
@@ -9,19 +9,19 @@

 # delete files in /tmp during boot older than x days.
 # '0' means always, -1 or 'infinite' disables the feature
-TMPTIME=0
+#TMPTIME=0

 # spawn sulogin during boot, continue normal boot if not used in 30 seconds
-SULOGIN=no
+#SULOGIN=no

 # do not allow users to log in until the boot has completed
-DELAYLOGIN=no
+#DELAYLOGIN=no

 # assume that the BIOS clock is set to UTC time (recommended)
-UTC=no
+UTC=yes

 # be more verbose during the boot process
-VERBOSE=no
+#VERBOSE=no

 # automatically repair filesystems with inconsistencies during boot
-FSCKFIX=no
+#FSCKFIX=no

===============================
Steps to reproduce:
1. Install raring desktop
2. Run dist-upgrade (sudo apt-get update && sudo apt-get -y dist-upgrade)
3. Reboot after the update
4. Run update-manager -d
5. At the end the a prompt with 'Replaced the customised configuration file /etc/default/rcS?' message would be prompted with the diff as given above.

The the file before and after the upgrade are attached

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: initscripts 2.88dsf-41ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic i686
ApportVersion: 2.10.2-0ubuntu1
Architecture: i386
Date: Wed May 22 15:24:54 2013
InstallationDate: Installed on 2013-05-22 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
SourcePackage: sysvinit
UpgradeStatus: Upgraded to saucy on 2013-05-22 (0 days ago)

[Para Siva (psivaa)]

The file after the replacement is attache

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1182915

[Steve Langasek (vorlon)]

The "steps to reproduce" given here should not be correct. The default setting on a fresh install should be UTC=yes, *NOT* UTC=no. How did you get the UTC=no setting? If this is being preseeded somewhere, please don't preseed it. If it's being set by default, that's a bug that we should be concerned about fixing (for saucy - probably too late for raring).

Otherwise, this is the same as bug #1184006.

[Para Siva (psivaa)]

The UTC=no setting was not preseeded. It was a manual raring installation and the installation was in fact carried out on a machine with Windows 7 being side-by-side. I am curious that it could be the reason for UTC=no being there.

On a fresh VM raring installation with no other OS's present the UTC setting was set to 'yes', though and the upgrade was completed without any prompts.

[Launchpad Janitor (janitor)]

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