QML applications (including Plasma) didn't start after the recent update. Clearing the QML cache (find ~/.cache/ -name qmlcache -exec rm {} -r \;) helps.
find ~/.cache/ -name qmlcache -exec rm {} -r \;
I suspect this to be related to missing timestamps on the Qt libraries. Qt probably just compares its own timestamp to the timestamp of the cache file. All files in /usr have Jan 1970 timestamps.
If that turns out to be correct, maybe Qt could be built in a way that cache timestamps are compared to a build-time timestamp instead (although that would be bad for reproducible builds, so not sure)
Weirdly, this problem only occurred on one of my machines, which has my oldest Kinoite install.
I realize my proposed workaround doesn't actually work, since then it would still break when a qmlcache file was generated while in the time interval between when a new Qt package was built, and when it reached the user, since then the cache is still newer then the build-time stamp.
Metadata Update from @ngompa: - Issue tagged with: experience, kinoite
Which update? Please include the output of rpm-ostree status for any Kinoite report.
rpm-ostree status
I can not reproduce that so I'll close it until we get more info.
Metadata Update from @siosm: - Issue close_status updated to: Can't fix - Issue status updated to: Closed (was: Open)
I think this is essentially the same issue as https://github.com/flathub/org.kde.kasts/issues/19 and https://bugs.kde.org/show_bug.cgi?id=463770.
I can't reconstruct which update caused this now, but it can probably happen with any Qt update as long as the QML cache in the home directory is reasonably old.