Plasma 6.3 update: a lot of problems with sessions (x11)

Help
, , ,
21

Problems here too. When screens go to sleep mode, at the wake-up kwin has crashed and panels have disappeared on one screen. When I wake up my screens I have to pkill plasmashell && kstart5 plasmashell

OS: KDE neon 6.2 x86_64 
Kernel: 6.11.0-17-generic 
Uptime: 2 days, 1 hour, 36 mins 
Packages: 4034 (dpkg), 20 (flatpak), 30 (snap) 
Shell: bash 5.2.21 
Resolution: 2560x1440, 1920x1080 
DE: Plasma 6.3.0 
WM: KWin 
Theme: Default [GTK2/3] 
Icons: breeze-dark [GTK2/3] 
Terminal: konsole 
CPU: AMD Ryzen 5 3600 (12) @ 4.208GHz 
GPU: AMD ATI Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X 
Memory: 16445MiB / 32019MiB
22

The problem is when you play a game using steam, with wayland rather than X11, graphics perfs are divided by 3 ou 4…

1 Like
23

Operating System: MocaccinoOS (… a Gentoo-based distro)
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.6.75-mocaccino (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11700K @ 3.60GHz
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Manufacturer: ASUS

Nvidia driver is 550.144.03.

KWin crashestoo at startup in 90% of the cases , I run this to recover:

DISPLAY=:0 kwin_x11 --replace '>' /dev/null '2>&1'

Altrnately, logout/login.

My issue is that I get about 40 GB of thumbnails in ~/.cache and it takes eons to start after the login. How could I limit that?

Another odd thing is on my laptop that has a touchpad with gestures.
The gestures work in SDDM, but not after and KDE Plasma shows no such device in the settings. Yet, it works as simple pad, but no gestures.

Under Wayland there is no KWin, I think, all the windows show up in the middle of the screen and there is no title bar, no way to move/resize them.

Also, session restore is random, unreliable, if any.

24

That’s highly unexpected and not reproduce-able by most users.

GPU: AMD ATI Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X

Perhaps it is a driver issue with a rather oldish AMD GPU.
Which driver are you using ?

https://docs.mesa3d.org/drivers/radv.html#supported-hardware

Note that for GFX6-7 (GCN 1-2) GPUs, the amdgpu kernel driver is currently not the default in Linux (by default the old radeon KMD is used for these old GPUs, which is not supported by RADV), so users need to manually enable amdgpu by adding the following to the kernel command line: radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1

26

Moin,

updated my KDE neon today. The panel does not start (in my case at the bottom of the screen) with the program selection etc. does not start.

Without the panel I can’t check much.

Any hint how to start it or to analyze the error?

Thanks

27

I’d go in a command line second session, using CTRL+ALT+Fn, and check logs, clear the cache, create a new user, to see if does the same. It is hard to say remotely. I remember the first time I have moved from Plasma 5 to Plasma 6 it took a lot to start and get to that step.

28

Moin,
thanks, got it back. Eratic clicking with the mouse, restarting, trying to log in with a new user and a few curses helped.

The only problem I still have: Windows with file dialogs open very slowly. A remote drive is probably not accessible.

Micha

29

Considering the obvoius bugs, also the Wayland session is not tested.

30

I’m on Manjaro unstable (Arch in disguise) and X11 works fine.
Maybe most of these problems are Neon specific.

31

Mmmh I’m on Manjaro unstable, it is de facto Arch, I had no problem on X11. I did not test Wayland exensively but it works.
(Intel gpu)

32

I’m using amdgpu. I can reproduce at any time.

aegir@aegir-system:~$ sudo dmesg | grep amdgpu
[   12.662923] [drm] amdgpu kernel modesetting enabled.
[   12.663118] amdgpu: Virtual CRAT table created for CPU
[   12.663154] amdgpu: Topology: Add CPU node
[   12.663962] amdgpu 0000:07:00.0: No more image in the PCI ROM
[   12.663986] amdgpu 0000:07:00.0: amdgpu: Fetched VBIOS from ROM BAR
[   12.663990] amdgpu: ATOM BIOS: 113-TIC32794-001
[   12.682236] amdgpu 0000:07:00.0: vgaarb: deactivate vga console
[   12.682241] amdgpu 0000:07:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[   12.682759] amdgpu 0000:07:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[   12.682762] amdgpu 0000:07:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
[   12.682906] [drm] amdgpu: 2048M of VRAM memory ready
[   12.682910] [drm] amdgpu: 16009M of GTT memory ready.
[   12.690113] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[   12.800616] snd_hda_intel 0000:07:00.1: bound 0000:07:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[   13.077621] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[   13.077643] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[   13.077778] amdgpu: Virtual CRAT table created for GPU
[   13.077874] amdgpu: Topology: Add dGPU node [0x67ef:0x1002]
[   13.077877] kfd kfd: amdgpu: added device 1002:67ef
[   13.077896] amdgpu 0000:07:00.0: amdgpu: SE 2, SH per SE 1, CU per SH 8, active_cu_number 14
[   13.082187] amdgpu 0000:07:00.0: amdgpu: Using BACO for runtime pm
[   13.082723] [drm] Initialized amdgpu 3.59.0 for 0000:07:00.0 on minor 1
[   13.107625] fbcon: amdgpudrmfb (fb0) is primary device
[   13.107633] amdgpu 0000:07:00.0: [drm] fb0: amdgpudrmfb f
33

I’m unable to use any of my GUI automation tools like xdotool under Wayland. I tried ydotool and it doesn’t work. That’s why I cling to X11.

34

While I don’t use such software, ydotool should work. Are you sure you have the daemon (ydotoold) installed and it’s running as root? I assume it’s very important that it runs as root under Wayland.

35

xdotool is X11 specific that won’t ever work in Wayland (as it x prefix implies).

sudo -b ydotoold --socket-path=“$HOME/.ydotool_socket” --socket-own=“$(id -u):$(i
d -g)”
YDOTOOL_SOCKET=“$HOME/.ydotool_socket” ydotool key 125:1 125:0;

That does work. ydotool needs a daemon running with a socket to talk to the client.
It might not be 1 for 1 replacement still, don’t know.

36

Try kdotool instead of ydotool.

1 Like
37

I can confirm this. My issue predates 6.3, though—I was hopeful that 6.3 would fix it, but it didn’t! Here’s what happens:

Everything seems fine, but if Plasma locks my session after the set time, when I unlock it, I either get a black task manager or a black screen. Every program is still open, and I can use Alt+Tab to switch between them. I can also hit the Meta key, and the application dashboard shows up. To restore everything, I have to restart Plasma with:

kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell &

However, if I lock the session manually, the issue doesn’t occur.

Output of plasmashell --version && kf5-config --version (left the QThreadStorage output there—it didn’t appear before, but I’m getting it under 6.3):

plasmashell 6.3.0  
QThreadStorage: Thread 0x55b27ebbd1f0 exited after QThreadStorage 8 destroyed  
QThreadStorage: Thread 0x55b27ebbd1f0 exited after QThreadStorage 3 destroyed  
QThreadStorage: Thread 0x55b27ebbd1f0 exited after QThreadStorage 2 destroyed  
Qt: 5.15.15  
KDE Frameworks: 5.116.0  
kf5-config: 1.0

My GPU is an integrated Intel for i7-1165G7.

38

I used to think that locking it manually did not effect it either, but then I left the manually locked screen locked for a few hours and the glitch reared its ugly face again.

39

Interesting, has not happened to me yet. Will try to reproduce it since I usually put it to sleep when I expect to be away from it for a long time.

40

That sounds unrelated

41

Hi!

I also encountered a problem after the last update of Plasma 6.3 on my machine which has KDE Neon: basically I can’t delete files. Whether I press DEL/CANC or if I right-click on the file to move it to the trash can, I get a kioworker crash and the error “The process for the trash protocol died unexpectedly”. If I use the rm command from the terminal everything works.