timezone selection during install, not set properly post-install

Bug #1124432 reported by Sean Fay
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
High
Unassigned
Raring
Invalid
High
Unassigned

Bug Description

During installation (Raring Daily) Dallas, TX (CST) selected. However post-install, Los Angeles, CA (PST) selected.

Attached ubuntu-bug output saved to timezone_bug.txt.

wzn5t4@ubuntu:~$ lsb_release -rd
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
wzn5t4@ubuntu:~$

Revision history for this message
Sean Fay (ssbob98) wrote :
Thomas Ward (teward)
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

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/1124432

tags: added: iso-testing
Changed in ubiquity (Ubuntu):
status: New → Confirmed
tags: added: ubiquity-2.13.10
tags: added: raring
Revision history for this message
Colin Watson (cjwatson) wrote :

I was unable to reproduce this with a daily build from the 15th, and unfortunately your logs don't quite have enough information for me to debug it from them. Are you in a position to try installing again? If so, could you use the "Try Ubuntu without installing" option and then run "ubiquity --debug" from a terminal to start the installer (just beware that your password will end up in the debug log when running in debug mode, so don't use a valuable password)? That should make /var/log/installer/debug rather more useful.

Changed in ubiquity (Ubuntu Raring):
status: Confirmed → Incomplete
Revision history for this message
Colin Watson (cjwatson) wrote :

Also, what interface did you use to determine the post-install timezone?

Revision history for this message
Sean Fay (ssbob98) wrote : Re: [Bug 1124432] Re: timezone selection during install, not set properly post-install

I clicked on the clock in the upper right and checked timezone and it
showed Pacific time (Los Angeles) even though I typed in Dallas, TX in the
text field while installing.

On Wed, Feb 20, 2013 at 9:47 AM, Colin Watson <email address hidden>wrote:

> Also, what interface did you use to determine the post-install timezone?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1124432
>
> Title:
> timezone selection during install, not set properly post-install
>
> Status in “ubiquity” package in Ubuntu:
> Incomplete
> Status in “ubiquity” source package in Raring:
> Incomplete
>
> Bug description:
> During installation (Raring Daily) Dallas, TX (CST) selected. However
> post-install, Los Angeles, CA (PST) selected.
>
> Attached ubuntu-bug output saved to timezone_bug.txt.
>
> wzn5t4@ubuntu:~$ lsb_release -rd
> Description: Ubuntu Raring Ringtail (development branch)
> Release: 13.04
> wzn5t4@ubuntu:~$
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1124432/+subscriptions
>

Revision history for this message
Sean Fay (ssbob98) wrote :

On 02/20/2013 09:46 AM, Colin Watson wrote:
> I was unable to reproduce this with a daily build from the 15th, and
> unfortunately your logs don't quite have enough information for me to
> debug it from them. Are you in a position to try installing again? If
> so, could you use the "Try Ubuntu without installing" option and then
> run "ubiquity --debug" from a terminal to start the installer (just
> beware that your password will end up in the debug log when running in
> debug mode, so don't use a valuable password)? That should make
> /var/log/installer/debug rather more useful.
>
> ** Changed in: ubiquity (Ubuntu Raring)
> Status: Confirmed => Incomplete
>
I could not reproduce it, my guess is that it was a one time thing or it
was fixed inadvertently with a newer daily build.

What would you like me to do now?

Sean

Revision history for this message
Brian Murray (brian-murray) wrote :

I'm setting this to Invalid as it is no longer recreatable and we don't know what exactly fixed it so Fix Released is inappropriate.

Changed in ubiquity (Ubuntu Raring):
status: Incomplete → Invalid
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.