For the past years I've been wishing to switch from X11 to Wayland and enjoy its performance improvements and other capabilities. Unfortunately even in the latest openSUSE Tumbleweed snapshot, a KDE / Plasma session will cause not just graphical glitches but also session crashes back to the login screen. I wanted to discuss the main one I've ran into during today's tests, before deciding if I should report this as a bug too.
Apart from the changing cursor size and harmless graphical glitches I could live with temporarily, Wayland seems to introduce a strange bug on amdgpu: Sometimes when you open an application, like from say the Kickoff launcher, the window of that application will never appear. The application process itself does start as I can see it in KSysGuard without any sleep status applied, where sending it a kill signal will quickly shut it down proving it's responsive. There is however no window or taskbar entry, although it feels like the desktop is trying to select something that doesn't exist. At this stage, if I use the scroll wheel to go to the other desktop and then back, everything will freeze for a few seconds followed by a black screen and waking up back in the login manager.
Someone suggested I try booting with amdgpu.dc=0. I did so but due to there still being crashes and bizarre visual glitches, it was hard to tell if that made this particular issue go away. I still crashed back to SDDM once but I think it may have been a different trigger. Anyone else getting this particular problem and knows when we can expect a solution?
Apart from the changing cursor size and harmless graphical glitches I could live with temporarily, Wayland seems to introduce a strange bug on amdgpu: Sometimes when you open an application, like from say the Kickoff launcher, the window of that application will never appear. The application process itself does start as I can see it in KSysGuard without any sleep status applied, where sending it a kill signal will quickly shut it down proving it's responsive. There is however no window or taskbar entry, although it feels like the desktop is trying to select something that doesn't exist. At this stage, if I use the scroll wheel to go to the other desktop and then back, everything will freeze for a few seconds followed by a black screen and waking up back in the login manager.
Someone suggested I try booting with amdgpu.dc=0. I did so but due to there still being crashes and bizarre visual glitches, it was hard to tell if that made this particular issue go away. I still crashed back to SDDM once but I think it may have been a different trigger. Anyone else getting this particular problem and knows when we can expect a solution?