I’ve been trying the Plasma 6 upgrade on Tumbleweed over the past few weeks. All I can say is thank god I can use virtualbox to roll back…
After the upgrade, SDDM defaults to the Wayland session. With that selected, my mouse cursor disappears. If I actually log in, the screen goes black. I have to reset the VM.
Pick the X11 session back in SDDM, my mouse reappears. Boot into plasma desktop. Slow. Very slow. Until I dismiss the welcome screen (the tour). Then the whole thing freezes. I have to reset the VM.
Is there an easy way to block the P6 upgrade in zypper? A list of packages to block? Such that zypper doesn’t get stuck in endless reams of dependencies on packages that have been removed?
Because if I do a ‘zypper dup’ it installs Plasma 6 and the system becomes unusable.
So I am stuck with either:
not upgrading packages anymore;
finding a way to block the plasma 6 upgrade and resume using zypper dup;
or manually selecting which packages to upgrade and which to leave – on a rolling release which regularly generates thousands of package upgrades at a time
Maybe. But I also tried installing KDE Neon in Virtualbox after the first time I had to roll back the plasma 6 upgrade and I had the same problem. So I don’t think the problem is zypper, but plasma. Which is why I am looking for a way to block the plasma upgrade.
I actually had tried a fresh install from openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240319-Media.iso and that had exactly the same effect. But I just tried openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240404-Media.iso in the same VM config as I had on my main install.
X11 essentially shows the same behavior as on my main VM.
But Wayland actually seems to work.
Guess I’ll try clearing out all my cached RPMs and upgrading again. And failing that, set up a new machine.
I did, and still on Plasma5. But I’m sure it’s too late for your install. Mine is a native install, and not running in a VM.
I simply set all the repos to Not Active
Of course, the side effect is no updates, unless you’re very cautious and know which (repo) to Enable and do a very select update of specific packages, then turn it off again
Yea,I admit, what I do (for now) is not the proper way to “use” TW. But it’s always the user’s decision how to do updates, and so forth.
A rolling distro can be a gamble much of the time. Like the recent xz issue (only the cutting edge rolling distros were affected), and the occasional broken package every so often. And yea, I understand the gamble. With that said, I turned off updates to avoid the KDE6 fiasco. Maybe I should write a Disclaimer in my posts
So, to solve my issue to stay on KDE5 (vs everyone’s rush to get KDE6), I’m investigating Slowroll and Leap (15.6 Beta). I’d rather wait until the majority of issues are resolved, rather than being a beta tester.
