A normal dnf --refresh upgrade should now succeed and result in a working Plasma system without the application launcher issue, although users may need to wait some time for the update to propagate to local mirrors.
As a new fedora user coming from Kubuntu, are fedora upgrades normally this choppy?
I had to uninstall wine to upgrade, reinstall wine, fall back to previous krunner (which keeps telling me to upgrade now), and PlayOnLinux no longer works, so I had to move all that content to a flatpak install. I’m hoping this isn’t an every-six-months kind of thing.
Fedora Workstation is usually the very first to be released. The other editions (KDE) and spins (the rest) often follow very quickly and may or may not have the same or similar issues.
Each edition/spin has its own development team that is responsible for that particular flavor of fedora and most of the spins seem to depend upon the final release of Workstation before finalizing their own release. They are, after all, dependent upon the main base os upon which the spins add their own DE and specific management tools that define the differences between the main fedora edition and their own spin. This can, necessarily, add some delays in releasing the final version of the spin.
No this is not typical, however depending on what packages you depend on there is always a chance that you may see an issue.
Wine dropped the need for the .i686 RPMs and has caused a issue I think because of an problem with the packaging.
KDE released 6.5 while fedora 43 was frozen which has delayed getting 6.5 into shape for f43 - the packagers are actively working on this now that the freeze has been lifted.
Well, while the road into the future might be somehow bumpy from time to time, you cannot avoid it. As an alternative, you could dwell in the City of Stagnation.
You are saying that you have switched from Kubuntu to Fedora KDE. We have always had a lack of KDE users who would have tested KDE, so if you want, you can help us in the future.
@pg-tips Thanks for documenting this. Since the fixed gstreamer update is already stable, I wonder whether the issue is fully gone now, or whether some issues still remain? IIUIC, no KDE user should be blocked from getting the update, i.e. starting Plasma desktop and updating the system through Discover was not affected. So everyone should get the fixed update very soon (depending on local mirrors as well). Is there anything else to be concerned about? (I think there’s no worth polishing the article and publishing it, if the problem was resolved already). Let me know, thanks.
I agree we don’t need to publish this as a common issue now. As of now, the fixes that have been pushed should mean that everyone can dnf upgrade to a state with no broken dependencies.