Bug 2229207 - initial-setup always sets the RTC to local mode
Summary: initial-setup always sets the RTC to local mode
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 38
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-04 15:54 UTC by Davide Cavalca
Modified: 2023-08-04 16:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
inital-set/anaconda log from an affected fedora asahi remix system (134.35 KB, text/plain)
2023-08-04 16:31 UTC, Janne Grunau
no flags Details

Description Davide Cavalca 2023-08-04 15:54:04 UTC
In the Fedora Asahi Remix we've noticed that inital-setup (which uses anaconda under the hood) is always setting the RTC to local by writing LOCAL to /etc/adjtime. We would expect it to use UTC instead.

Reproducible: Always

Steps to Reproduce:
1. Get an Apple Silicon Mac (M1 mac mini or macbook is the easiest)
2. curl https://fedora-asahi-remix.org/install | sh
3. go through the install
4. check the time

Comment 1 Janne Grunau 2023-08-04 16:31:05 UTC
Created attachment 1981677 [details]
inital-set/anaconda log from an affected fedora asahi remix system

from browsing through the anaconda source code I suspect the problem is that time_initialize() https://github.com/rhinstaller/anaconda/blob/f076f51c9c56ef226dc7ee56fce3feefa5cf2032/pyanaconda/timezone.py#L55 is not called.

I do not see an execution of `hwclock --hwtosys ...` logged. From my cursory browsing think the program execution should be logged and `hwclock --systohw --local` is logged.

timezone_proxy.IsUtc defaults to false resulting in the system being configured LOCAL in etc/adjtime.


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