FWIW, I’ve been using KDE Plasma 6 (Wayland and Xorg with Leap 15.5) for the past two weeks and experienced no real issues. (I’ve also tweaked my digital clock to display in green!)
3 Likes
Right. So what configs should I be looking at changing?
No clue, I suggest creating a new user, and logging in there, and copying over configs from your existing $HOME/.config until you find the ones that are breaking things.
3 Likes
You can’t possibly be suggesting that you have to create a new user account after the upgrade (??). A user should be able to use their well-established user account after the upgrade. No excuse.
EDIT:
Maybe don’t suggest the ‘new user’ if unsure about next steps.
1 Like
that worked! Thank you so much awesome person! What is that terminal it takes me to? Does that like unload the entire de and just take me down to a terminal and that’s it? I also couldn’t figure out how to get out of there, and since it locked the zypper app in my regular de terminal, I went back into it, exited the root user, then just rebooted, I hope that’s okay?
2 Likes
Disagreed, @aggie , because it is a new-new thing, and all the final bug cleanup can’t possibly have been finished.
@sfalken (Shawn) gave one of the best troubleshooting answers. But, note, he does NOT say you need a new user. Instead, he is suggesting creating a new user to test configs one at a time until the culprit is identified.
I said nothing of the sort. Read what I said.
1 Like
That takes your Desktop environment out of the loop, yes. It’s not impossible, when upgrading a desktop, for it to replace running files, as part of the upgrade process, and it will break running processes.
When it’s minor releases (like Plasma 5.27.9 to Plasma 5.27.10) usually you’re fine, but this is a major upgrade.
4 Likes
That approach is commonly used for diagnostic/comparative purposes amongst users, especially with those investigating broken Wayland environments.
2 Likes
Exactly. One of the best approaches, useful in many different situations.
I’ve survived the update. Neat.
3 Likes
I didn’t think to run the update in a tty so my session got killed when the update was almost finished. I was thrown back to the login screen with the default sddm theme (some qml file was not found for some reason)
Then I log in, everything is slow as a turtle and later I realize I’m running Plasma Wayland?? Even though the nvidia 470 driver doesn’t support it?? Later I found the Plasma X11 session is missing.
I’m trying to figure out what went wrong
switch to a tty, and try running another dup, it’s not impossible you didn’t get a complete update.
3 Likes
I’ve been using Wayland since 5.20 will there be any problems?
Or should I set up my new user before updating?
Oh! one more ting reasding these doing a tty not a konsolr in X,
I would probably just setup a new user ahead of time, just in case, but it really won’t “break” anything if you need to do it after the update, for troubleshooting.
1 Like
Thanks just wanted to be prepared.
Everything seems to be fixed now. It was a bit of a pain because I still needed to use nmtui to get the network up and running before I could run zypper dup again, but now everything seems to be fine.
I still have no idea why the Plasma Wayland session is still listed, given that my driver doesn’t support it.
Another annoying problem is that kwallet pam config that forwards your login password to kwallet no longer seems to work and now I have to type the password twice in order to get the wifi up. I’ll check if that’s still the case after the next reboot.
(edit: sound effects pretty)
It’s installed as part of the pattern, whether your hardware supports it or not. You can likely remove it, if it bothers you enough.
It’s always been installed, but it wouldn’t show up as an option unless the driver supported it (if I installed nouveau, for instance).