Timezone info is switched w/ GMT in expert install.

Bug #34253 reported by GarlicSalt2
This bug report is a duplicate of:  Bug #28961: installer assumes system time is UTC. Edit Remove
16
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Medium
Unassigned
gnome-system-tools (Ubuntu)
High
Unassigned

Bug Description

When I install Ubuntu 5.10 "Breezy Badger" on my Toshiba 2065CDS Laptop PC (AMD K6 366MHz CPU, et al.) when I select the US Pacific Timezone and continue to the next page of the install, I am told that the GMT time is the time that the local time should be, and that the local time is 8 Hours later than that. For example, if my bios clock shows 4:00 PM (1600 Hours int'l) then Ubuntu shows that GMT is 16:00 Hours and that local time is 0:00 hours or 12:00 AM the next day. This is only a minor problem, which is fixed at the next update from an NTP server. There might be those, however, who don't have network access. Currently, this old Notebook PC is the only place where I have Ubuntu installed, so I can't do a check on another hardware platform. I have done more than 3 Re-installs for various reasons, and this apparent bug appeared in all of those cases. I did a search for "timezone" in the bug tracker search page and did not see any reports of this problem. I'm not very good with internet searches, so I hope I'm not resubmitting a know problem.
--Aaron

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Not sure if it the same bug, but when I installed flight 5 I told the installer my hw clock is localtime (because I have a windows dual boot). After install the clock was wrong, also back in windows. Seems like it had set the hw clock wrongly to UTC.

This was with a normal install (not expert).

Revision history for this message
Melissa Draper (melissa) wrote :

This has happened to me also. I've had this dapper system installed for several weeks now, and it is up-to-date. I had not rebooted for several days, but yesterday I did so and this behaviour began.

Changing time/date via the applet is not permanent, as it reverts to GMT at reboot. The system acknowledges the correct timezone (for me, Australia/Sydney), however it seems that data for said timezone has been wrongly changed or corrupted. Sychronising with the internet server does not do anything to help.

Changed in debian-installer:
status: Unconfirmed → Needs Info
Revision history for this message
Colin Watson (cjwatson) wrote :

Melissa, this report is of an installer issue; if you're having trouble with some part of the installed system, then that's a different bug. Could you please file a separate bug report about that? If it's the "Adjust Date & Time" applet in a standard Ubuntu installation, then that should go on the gnome-system-tools package.

Changed in timezoneconf:
status: Needs Info → Unconfirmed
Revision history for this message
Melissa Draper (melissa) wrote :

Colin, if i've refiled this wrong, please fix it. I'm still learning how to use this launchpad thing :-/

Revision history for this message
GarlicSalt2 (garlicsalt2) wrote :

Melissa, I think Australia's Dailight saving time has been delayed this year in several Australian states. Dailight Time normally starts in March. This year, for something called the "Commonwealth Games", dailight Saving Time will start in April instead. Check if this problem still occurs in April. Your clock is probably only an hour off?? I suspect that either Ubuntu didn't update that info - OR - Ubuntu developers accidently updated DST for all of Australia, and you are in a state that isn't affected. Either way, this problem will PROBABLY fix itself on April 1st. This is just stuff I read about, so I couldn't tell you the details

IF this is NOT the case for you, THEN please file a NEW bug report.

Revision history for this message
Colin Watson (cjwatson) wrote :

This shouldn't be part of the same bug - they're different problems and it's going to be confusing if we interleave discussion about them. Could you please file a new bug here:

  https://launchpad.net/distros/ubuntu/+source/gnome-system-tools/+filebug

Changed in gnome-system-tools:
status: Unconfirmed → Rejected
Revision history for this message
GarlicSalt2 (garlicsalt2) wrote : Re: Timezone info is switched w/ GMT - I *might* have found the problem!!

Today I discovered something interesting! Although I was not trying to work out this bug, I was poking around in /etc/default folder, and did an 'less rcS' (or 'cat rcS') while I was in there, I noticed that the setting for something about "System clock is UTC" or something listed in the comment above, and the setting 'UTC=True' directly below. My internet doesn't work on my laptop, (which is where I have Ubuntu installed,) so I can't check if an NTP update works as expected. Someone may want to try checking this out...

Revision history for this message
Erich Pawlik (erichpawlik) wrote :

I had the issue with the change of the system clock mentioned in some posts. Setting UTC=no in /etc/default/rcS solved this problem. I don't have any indication whether one of the other issues mentioned in the posts including the original bug reports can be fixed by this change.

As proposed above, I have posted a bug report about the change of system clock (as bug #37380).

Revision history for this message
GarlicSalt2 (garlicsalt2) wrote :

I forgot to post this: While installing Ubuntu on a second PC, I discovered how to avoid the problem from the beginning! During the install process, select your time zone as usual. When you're asked "Is this correct", select "No". You should then be asked "Is system clock set to UTC?". At this point answer "No". You should then be asked to select the timezone again, etc. The time settings should be correct from there on out, including the setting in '/etc/devault/rcS'.

The problem seems to be that the question isn't being asked the first time around.

--Aaron

Revision history for this message
Matt Zimmerman (mdz) wrote :

Colin, is there actually a bug here? It sounds like just confusion over what it means for the hardware clock to be in UTC

Revision history for this message
GarlicSalt2 (garlicsalt2) wrote :

Whether you'd call it a "bug" or just an oversight, I don't know, but the problem at this point seems to me to be that, during the install, I am not being asked whether the hardware clock is UTC as I should. Instead, the installer automatically assumes that the H/W clock IS set to UTC. Through trial and error, I have discovered that if I choose my timezone settings as usual and then choose the option to go back and reselect those settings, the question is then asked correctly the second time around.

BTW, Is there a target release date for Dapper Drake, or is it just going to be "Whenever it's finnished"? I see info. that points to this month, but not a particular day.

--Aaron

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

Other bug subscribers