Created attachment 1840688 [details]
KDE is presented when logging in after installation with a UTC timezone
Description of problem:
When installing Fedora Kinoite - or rebasing from Silverblue to Kinoite - when the system is installed as a UTC timezone, the KDE Desktop Environment is broken
Have linked Anaconda as the component as this is the only place at install time you can define the timezone.
Version-Release number of selected component (if applicable):
Fedora Kinoite 35
Steps to Reproduce:
1. Run through installation process, selecting a UTC timezone (Europe/london tested) at install time
2. When installation completes, log into KDE
Applications and Links missing from the Application Launcher, white, broken icons for the preferred apps on the bottom panel. Links from both Application Launcher and bottom panel generate errors instead of performing expected actions.
WOrkaround is to install with a non-UTC timezone and change timezone after installation has completed, and then reboot. This fixes the issue temporarily. It appears that any interaction with rpm-ostree does trigger the issue again, requiring resetting of the timezonesto non-UTC and another reboot.
First raised and discussed here:
Top level post to raise awareness here:
Created attachment 1840689 [details]
Installation logs from another user who coorborated issue
I don't think it's an Anaconda bug. Redirecting to plasma. I've reported it here already: https://bugs.kde.org/show_bug.cgi?id=442011 but now that we have a better reproducer I can work on it / update the upstream report.
I don't think that bug is related, Timothée. It's not just missing icons, when installing using a GMT timezone there are no applications at all. The KDE menu is empty, not even system settings starts.
The mostly likely issue here is that on Kinoite, all files in /usr are timestamp 0 (thus using the UNIX origin timestamp).
The fact that it manifest only on the UTC timezone might be because on other TZ, something in KDE will convert the date into a "local zone" timestamp/date which then won't be 0.
Thus I think that the linked bug is a most probably a part but I agree that it may not be the entire bug or the full root cause behind this issue.
I can confirm this is still an issue on Kinoite Fedora 35. I set the timezone to London BST (UTC+1) during installation and KDE is unusable!
Reinstalling using US Eastern Standard Time leads to a working system.
Fedora Kinoite 36 has the same issue. Europe/London timezone. Trying to get my brother to switch from popOS after his install exploded after an update. Changing timezone fixes it but it's really not a solution.
Posted a patch upstream: https://invent.kde.org/frameworks/kservice/-/merge_requests/87
You can try the fix by downloading the RPM from https://koji.fedoraproject.org/koji/taskinfo?taskID=87087243 and then running:
$ rpm-ostree override replace ./kf5-kservice-5.93.0-2.fc36.x86_64.rpm
FEDORA-2022-5f52a69edb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5f52a69edb
FEDORA-2022-5f52a69edb has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.
Any chance of this being backported to Kinotie 36? Without this fix the only just released Kinoite 36 is effectively unusable in the UTC timezone.
This will come to Fedora 36 as part of the update to KDE Frameworks to 5.94 that should happen in the coming days/weeks.
Same for F35, if it ever gets this update (not sure about that though).
This is now in Kinoite 36 too.