The openSUSE Tumbleweed rolling release Linux distribution has begun rolling out the KDE Plasma 6.0.1, Gear 24.02 apps, and Frameworks 6.0 packages. Plasma 5 is being replaced within the Tumbleweed repository but openSUSE Tumbleweed isn’t yet transitioning to the Wayland session by default.
Switched from the kde test repo over to baseline Tumbleweed today. It was actually smoother than I’d expected
Are there any Arch based distros with KDE + Wayland by default?
Endeavor has X11 by default, right?
Endeavor and Arch both default to whatever upstream defaults to, so if you update Endeavor to plasma 6 then it will be wayland by default.
I upgraded to 6 on EOS and it switched to Wayland after the reboot after the upgrade. X11 is still there, though. I kept it as a fallback in case Wayland shits the bed at some point.
Garuda’s gaming spin should. At least mine runs on Plasma 6 + Wayland and I didn’t do anything special to get there.
Endeavor and Arch both default to a Wayland session currently.
(Tested yesterday)
This is the best summary I could come up with:
The openSUSE Tumbleweed rolling release Linux distribution has begun rolling out the KDE Plasma 6.0.1, Gear 24.02 apps, and Frameworks 6.0 packages.
Plasma 5 is being replaced within the Tumbleweed repository but openSUSE Tumbleweed isn’t yet transitioning to the Wayland session by default.
Plasma 6 on openSUSE Tumbleweed has been fairing well in developer testing and uncovered bugs are being fixed for forthcoming KDE Plasma 6.0 point releases.
openSUSE developer Fabian Vogt who has been coordinating the Plasma 6 landing in Tumbleweed noted that the KDE Wayland session isn’t the default yet.
Plasma on Tumbleweed will switch to Wayland as a later time to help differentiate Wayland-specific bugs versus general Plasma 6 issues.
More details on the Plasma 6 transition for openSUSE Tumbleweed via the openSUSE Factory mailing list.
The original article contains 129 words, the summary contains 129 words. Saved 0%. I’m a bot and I’m open source!
I did an update. First time I tried I borked something. Zypper refused to work. No worries, just rolled back to a snapshot did the update again from tty to be safe. Everything worked just fine. I even released all the locks I had for patterns hah.
It did leave a ton of unneeded packages behind. Now I’m wondering if I’m safe in cleaning them up.
The new system has a few bugs but seems otherwise fine. A panel keeps jumping to a different screen on restart. Some small graphical glitches. Nothing I can’t live with.
Had to switch back to X11 because of novideo being shit. Tried 525, 535, and 540 and vscode would flicker like that one light at the back of the gas station nobody likes to visit because all they sell are stale cigarettes
Am also back to X11, because
xsetwacomdoesn’t work with waylandWhat do you need xsetwacom for that isn’t working with the native settings manager?
I want to map the surface of the tablet to the bottom left quarter of the screen so that xournal++ doesn’t take up all my screen space. I don’t think that’s possible with gnome settings
https://github.com/OpenTabletDriver/OpenTabletDriver pretty sure this tool is what you’re looking for!
The latest driver should be 550 series. If VS Code is running under xwayland then you are probably going to be waiting a few more months for explicit sync to be finished in xwayland and various other pieces of the graphics stack https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967. Since vs code is electron you can try running it with the wayland command line arguments
--ozone-platform=wayland. There might be some other arguments you need to pass depending on the version of electron.I’ll have to look into this a bit more. The guy at the end of the comment chain says his chromium stuff is still flickering, but I’ll give it a whirl when I don’t strictly need a working dev environment :P
Also went back to x11 because of vscode flickering and redrawing badly. I’m not sure whether it’s an nvidia problem, a vscode problem, or a kwin-wayland problem though.
you might want to give this fix a shot!
https://old.reddit.com/r/Fedora/comments/1afkoge/how_to_make_vscode_run_in_wayland_mode/
That seems to have worked. Thanks.
Plasma 6 and Wayland are working great under Tumbleweed for me on my 2-in-1 laptop, but there’s still no usable virtual keyboard package like Maliit in Factory.
Honestly, I don’t like any of the wayland keyboards, I wish onboard still worked, but sighhh.
I’m just waiting for a good 2-in-1 Linux solution to come around. I don’t have the programming chops to try and make something myself.
I’d love to have something like Gboard (maybe de-googled) that completely deactivates when in laptop-mode.
I don’t even mind if it’s Xorg or Wayland at this point.
