Bug 1685305 - Timezone not taken into consideration
Summary: Timezone not taken into consideration
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-04 23:05 UTC by Alessio
Modified: 2020-05-26 14:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 14:45:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/log/anaconda/ks-script-hvc_kuas.log (150 bytes, text/plain)
2019-03-05 15:16 UTC, Alessio
no flags Details
/var/log/anaconda/dnf.librepo.log (1.72 MB, text/plain)
2019-03-05 15:17 UTC, Alessio
no flags Details
/var/log/anaconda/journal.log (1.63 MB, text/plain)
2019-03-05 15:17 UTC, Alessio
no flags Details
/var/log/anaconda/hawkey.log (2.44 KB, text/plain)
2019-03-05 15:20 UTC, Alessio
no flags Details
/var/log/anaconda/lvm.log (166.11 KB, text/plain)
2019-03-05 15:20 UTC, Alessio
no flags Details
/var/log/anaconda/program.log (54.74 KB, text/plain)
2019-03-05 15:21 UTC, Alessio
no flags Details
/var/log/anaconda/dbus.log (3.10 KB, text/plain)
2019-03-05 15:21 UTC, Alessio
no flags Details
/var/log/anaconda/anaconda.log (38.55 KB, text/plain)
2019-03-05 15:22 UTC, Alessio
no flags Details
/var/log/anaconda/ks-script-ix1yv089.log (69.10 KB, text/plain)
2019-03-05 15:24 UTC, Alessio
no flags Details
/var/log/anaconda/storage.log (115.47 KB, text/plain)
2019-03-05 15:24 UTC, Alessio
no flags Details
/var/log/anaconda/packaging.log (310 bytes, text/plain)
2019-03-05 15:25 UTC, Alessio
no flags Details

Description Alessio 2019-03-04 23:05:50 UTC
Description of problem:

Fedora Workstation Live
During the installation process, I selected a different timezone than the one automatically proposed by the installer.

Once the system is installed and once completed the initial setup spokes, I go to gnome-control-center -> Date & Time, and here the time zone is still the one originally proposed by the installer.

Note: this happens whether Location services is enabled or not during gnome initial setup spokes.


Version-Release number of selected component (if applicable):

Fedora-Workstation-Live-x86_64-30-20190301.n.0.iso
anaconda-30.25.1-1.fc30.x86_64
gnome-initial-setup-3.30.0-2.fc30.x86_64

Comment 1 Vendula Poncova 2019-03-05 11:40:32 UTC
Please, attach logs from the installation. You can find them during the installation in /tmp/*log or on the installed system in /var/log/anaconda/*log.

Comment 2 Alessio 2019-03-05 15:16:39 UTC
Created attachment 1540989 [details]
/var/log/anaconda/ks-script-hvc_kuas.log

Comment 3 Alessio 2019-03-05 15:17:05 UTC
Created attachment 1540990 [details]
/var/log/anaconda/dnf.librepo.log

Comment 4 Alessio 2019-03-05 15:17:45 UTC
Created attachment 1540992 [details]
/var/log/anaconda/journal.log

Comment 5 Alessio 2019-03-05 15:20:29 UTC
Created attachment 1540995 [details]
/var/log/anaconda/hawkey.log

Comment 6 Alessio 2019-03-05 15:20:50 UTC
Created attachment 1540996 [details]
/var/log/anaconda/lvm.log

Comment 7 Alessio 2019-03-05 15:21:13 UTC
Created attachment 1540998 [details]
/var/log/anaconda/program.log

Comment 8 Alessio 2019-03-05 15:21:35 UTC
Created attachment 1540999 [details]
/var/log/anaconda/dbus.log

Comment 9 Alessio 2019-03-05 15:22:18 UTC
Created attachment 1541001 [details]
/var/log/anaconda/anaconda.log

Comment 10 Alessio 2019-03-05 15:24:31 UTC
Created attachment 1541013 [details]
/var/log/anaconda/ks-script-ix1yv089.log

Comment 11 Alessio 2019-03-05 15:24:58 UTC
Created attachment 1541014 [details]
/var/log/anaconda/storage.log

Comment 12 Alessio 2019-03-05 15:25:19 UTC
Created attachment 1541015 [details]
/var/log/anaconda/packaging.log

Comment 13 Alessio 2019-03-05 16:12:15 UTC
I have spotted that if internet is unreachable during the installation, the selected timezone will be in place also after the initial setup.

Comment 14 Alessio 2019-03-21 07:13:10 UTC
I have also spotted that performing an installation using text mode, the right timezone selected during installation setup is still in place.
Maybe it is related to gnome initial setup?

Comment 15 Ben Cotton 2020-04-30 22:15:05 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Ben Cotton 2020-05-26 14:45:01 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.