KDE Tumbleweed users: consider giving Wayland a chance

Wayland has less security problems on average.

Have been using Wayland for the last few months. For me no issues-AMD Raydeon.

I remain a faithful Wayland user, and haven’t logged in to an X11 session in many months. Further, most of the problems noted in my first post have disappeared.

However, my Wayland experience also isn’t perfect. I post to share a couple of fixes for problems that still occur occasionally.

#1: The plasma desktop freezes. Icons for closed apps remain in the panel, the time in the digital clock doesn’t change. My fix:

killall plasmashell
kstart plasmashell

#2: krunner access disappears. My fix:

killall krunner

There may be better remedies , but these work for me.

1 Like

Just curious, how often do you run into plasmashell crashes? After months of using Wayland exclusively, I bit the bullet and switched to an X11 session for now, as I was running into plasmashell crashing multiple times per day, which was also taking down things like Brave Browser, etc.

I believe from reviewing the list that all of the things I’ve run into are addressed in Qt6/Plasma 6 based on the Wayland showstoppers page, but for now I feel compelled to deal with a few more stutters in exchange for keeping programs running.

John, as rarely as once every three days and as often as three times a day. That’s my rough estimate.

I remember that I used to have problems with Brave if I opened another Chromium-based browser at the same time, but that hasn’t occurred for awhile, and is the only Wayland-related problem that was a real inconvenience for me.

BTW, for others, something I should have mentioned in the earlier post: the fixes described above are in script files. As in:

#!/bin/bash
killall plasmashell
kstart plasmashell

When KDE Wayland works well with my laptop’s dedicated Nvidia card, I’ll make the swap there. I’ve already swapped on desktop, since all the important stuff works with AMD cards just fine.

i just installed tumbleweed with a kde desktop. is wayland already there or do i need to do extra setup to use it?

Just a matter of choosing the Plasma Wayland session at the displaymanager login screen.

3 Likes

i just reinstalled tumbleweed here and sometimes i get funky graphic errors and messages like this in dmesg:

[ 5270.843876] amdgpu 0000:07:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32770, for process kwin_wayland pid 2135 thread kwin_wayla:cs0 pid 2178)
[ 5270.843881] amdgpu 0000:07:00.0: amdgpu:   in page starting at address 0x00006bcd534f5000 from IH client 0x1b (UTCL2)
[ 5270.843887] amdgpu 0000:07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00300430
[ 5270.843889] amdgpu 0000:07:00.0: amdgpu:      Faulty UTCL2 client ID: IA (0x2)
[ 5270.843891] amdgpu 0000:07:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5270.843893] amdgpu 0000:07:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5270.843894] amdgpu 0000:07:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[ 5270.843896] amdgpu 0000:07:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5270.843898] amdgpu 0000:07:00.0: amdgpu:      RW: 0x0

not sure why.

the screen remains messed for a while but it ā€˜heals’ itself.

I use Wayland all the time on my AMD 6800H CPU and GPU. Works great.
Only when I switch to X11 on the login screen I automatically use the Nvidia GPU.
I can’t let the builtin GPU work with X11, nor the Nvidia with Wayland (but as I read this is normal for the Nvidia GPU)
Wayland gives me no issues what soever.

1 Like

KDE wayland is a blackscreen for my gtx960 + proprietary drivers.
Wayland works great on solo slow games, playing RedDeadRedemption1/2 on it was amazing. But on most of the online games it is awful .
I hope Opensuse and plasma wont follw fedoras move, and will keep maintained X after plasma 6. At least waiting to have a non ā€œvsyncā€ wayland mod for gamers and a possibility to scale colors aswell.

That’s the difference between you and me: I don’t play games so I don’t have the problems you have when playing a game.

In concrete terms, the three cases for which wayland is not ready (with desktop/GPU environments where it works) are :
-video games (adapative framerate)
-video/photo editing (color scaling)
-multi-window applications
Wayland is safer, lighter, better, prettier. I just hope kde wont forget that it makes a lot of users.

Since my initial post on 3 June, I finally made the switch from Debian 12 to openSUSE Tumbleweed on desktop hardware (two systems) and Tumbleweed-Slowroll on an external USB SSD, because of numerous Plasmashell crashes occurring after an X11 login on Debian.

No issues with openSUSE using either X11 or Wayland.

2 Likes

wayland also is not ready under vmware workstation where copy/paste is broken for quite a long time. also nomachine doesn’t work – only a dark screen.

Updated today to the latest snapshot where I ended up in a situation where the x11 plasma desktop was gone. reverted the snapshot and see what that caused (now need to work with the vm …)

Wayland is still janky for me, I see flickering in windows where stuff disappears and a little while later shows up. Waylan on TW is not ready for prime time but looks promising with its more responsive feeling.

I’ve got a RTX3080 video card with the latest driver installed.

For now going back to X11 and will come back to this next month to see if they fix these annoying rendering bugs.

I’m waiting for some of the remaining issues to be cleared up, see:
https://community.kde.org/Plasma/Wayland_Known_Significant_Issues

I have a test-user login that I periodically use to to see how well Plasma Wayland is coming along. Having a separate login prevents any corruption of my main X11 login, and makes for easier comparisons (I do have to be very careful to pick the right option on the sddm login screen). I’ve used the test-login to try and setup something that parallels my main account, based on that, I think I could make the switch if I felt there was a compelling reason.

This would all be with a GeForce GTX 1650 SUPER with the proprietary G06 550 driver.

I gave it a try on Fedora when 40 came out and ran into a condition where OOM killer took out the entire Plasma 6 session because I was trying to compile an Android ROM.

Wayland in any fashion without session restore or even separating the DE shell and apps is a gamble, that shouldn’t be entertained on a PC.


Never-mind the years of people exaggerating how good it is (my 1000Hz mouse is still floaty GNOME 46/Plasma 6 Wayland today; perfect on Xorg, and perfect years on Windows 7-11; I lose 10-20 FPS on Dota 2 from Wayland sessions and inexplicable 50 FPS caps on two games; both non-issues on Xorg).

Basically, I do give Wayland a try every now and then, and in less than a day I’m back on Xorg sessions because people are still pushing an inferior solution for some reason.

Right now I’m on Xfce with Xorg, with freedom to disable the compositor on games. Can’t beat that :stuck_out_tongue:

@Espionage724 I know this is Plasma related, but since you mentioned GNOME, I’ve not had any recent issues with GNOME on Wayland with Intel Arc or Nvidia Quadro T400, the Intel ARC is performing hardware wise (degraded no rebar or PCIe 4.) Blender with oneAPI, Darktable with oneAPI, Handbrake uses the Intel ARC etc… Also have the T400 for Prime Render Offload…

I gave wayland a try, and initially thought it was more responsive. After a reboot, it switch my primary and secondary monitors. Also, I got some flickering on the screen, and one screen ā€œspilled overā€ into the other.

NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Leap 15.6