and ran dnf downgrade plasma-workspace, which resulted in the following install, from rpm -qa --last
sddm-breeze-5.27.8-2.fc39.noarch Mon 27 Nov 2023 13:13:53 GMT
plasma-workspace-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:50 GMT
powerdevil-5.27.8-1.fc39.x86_64 Mon 27 Nov 2023 13:13:44 GMT
plasma-workspace-x11-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:44 GMT
plasma-workspace-wayland-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:44 GMT
plasma-lookandfeel-fedora-5.27.8-2.fc39.noarch Mon 27 Nov 2023 13:13:44 GMT
plasma-workspace-libs-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:43 GMT
plasma-workspace-geolocation-libs-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:43 GMT
plasma-workspace-geolocation-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:43 GMT
libddcutil-1.4.1-2.fc39.x86_64 Mon 27 Nov 2023 13:13:43 GMT
kscreenlocker-5.27.8-1.fc39.x86_64 Mon 27 Nov 2023 13:13:43 GMT
plasma-workspace-common-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:42 GMT
libkworkspace5-5.27.8-2.fc39.x86_64 Mon 27 Nov 2023 13:13:42 GMT
and the problem was fixed for now, although not an optimal install, i would have liked to get the prior version that my other workstation was running, but seems i cant find those on the mirrors i tried.
hope this helps anyone in the same situation, and alerts that theres a problem (that affected at least me).
thank you Ellis for replying.
As I run a normal install I could not just roll back. I dont know why when updates are pushed they dont leave the last 3 in the repo for rollbacks, as fedora has the feature to rollback, just cant use it.
anyone knows better would appreciate being put right on that one.
I know I can keep my own with reposync and keep all the old updates.
regards peter
OK, so after i checked my wifes PC , i found she was already on the 5.27.9.1-3.fc39.x86_64 version and no problems with login.
I updated my main PC and it too had no problems, so I updated the offending PC, and problem seems to be fixed.
I did notice that they were all getting slightly different lists of packages to update, ie different mirrors, and so
i can only guess that the offending PC was connected to a slow mirror, that had a package that was incompatible with 5.27.9.1-3.fc39.x86_64
and thats now been updated, as we are now about 24 hours ahead.
apparently you can install the repo fedora-repos-archive and this allows full downgrade to any version of a package since the base release.
regards peter
That seems a misunderstanding.
That is an archive for versions of the fedora-repos package and not for any package.
I suspect this may have been due to a case where the mirror in use was not fully updated at the time the update on the PC was done so inconsistencies were encountered. Another update later seems to have fixed the problem by completing the update.
This often happens to various users and the fix has historically been the same – redo the update after waiting some (usually small) amount of time.
They have that right. fedora-repos-archive contains the updates-archive repo, which contains all obsolete updates. It was created for Silverblue et al. for the case where you’re trying to layer a package that is tightly coupled to something in the base image, so you need the exact matching version.