I'm not an expert but I had a similar problem, except it was visible after each time I was rebooting to windows. Linux by default interprets the hardware clock as UTC, whereas windows interprets as local time. The warning you see is when your linux distro is instead configured to behave like windows does (local time).
In your case, it doesn't seem as obvious what is the culprit (no windows to write the local time to the RTC) but perhaps the distro's update changed that parameter somehow ?
Setting the flag to 0 shouldn't cause more trouble than what you've already seen I think... So that's worth trying out for a few days ;)
+1 for Niri. Plus latest release of Niri has native alt-tab with window previews 👍
I'm not an expert but I had a similar problem, except it was visible after each time I was rebooting to windows. Linux by default interprets the hardware clock as UTC, whereas windows interprets as local time. The warning you see is when your linux distro is instead configured to behave like windows does (local time).
In your case, it doesn't seem as obvious what is the culprit (no windows to write the local time to the RTC) but perhaps the distro's update changed that parameter somehow ?
Setting the flag to 0 shouldn't cause more trouble than what you've already seen I think... So that's worth trying out for a few days ;)
Hey, are you SURE this isn't some timezone shenanigans, but at a lower level ? What is your timezone ? Are you dual booting to Windows sometimes ?
This could be an issue in how linux uses the hardware's realtime clock (RTC).
Perhaps running
datetimectl statuscould provide some insight ?