I’m seeing a very strange issue on a System76 Lemur Pro (lemp11).
What I’ve observed:
Fresh install of Fedora Silverblue → system boots with the wrong date/time.
The issue also occurs on Secureblue (which is based on Silverblue).
chronyd is running, but the system is sometimes not synchronized after boot.
Resetting or changing the DNS configuration causes the clock to immediately jump to the correct time.
The confusing part is that I can’t reproduce this on other distributions. The same laptop behaves normally with Fedora Workstation and Pop!_OS.
I haven’t been able to reproduce it on a ThinkPad X280/T480. The clock on those work fine post install.
That makes me wonder if this is something specific to the Silverblue/Atomic boot process or service ordering on this hardware, rather than a failing RTC or CMOS battery.
Has anyone seen something similar, particularly on System76 hardware? Any ideas on what to investigate next or which logs would be most useful?
I’d be happy to provide more details or run additional tests.
yes you can. On Graphene you can set the main profile as just there with nothing except to control wifi/add esim/etc. Then you can create many profiles with their own passwords. You can store your work stuff in 1 profile, private stuff in another. You can even create a dummy profile with fake Google. .
The downside currently is that the OS autoboot to main profile. Then you switch to your other profiles.