Created attachment 130475 [details] SDDM Wayland session log SUMMARY I'm using SDDM to login to a plasma-wayland session, and upon doing so, it seems to crash and take me back to SDDM. But the session is actually still live, and kdeconnectd consumes 100% cpu till I manually kill it. STEPS TO REPRODUCE 1. Use SDDM 2. Choose plasma-wayland session 3. Login OBSERVED RESULT Crash. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux: 5.7.10 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Attached is "~/.local/share/sddm/wayland-session.log".
Created attachment 130476 [details] Coredump infor for KWin Also attaching the coredump info for the kwin crash. It may not be useful due to a lack of debug symbols, but still.
kwayland-server 5.19.4-2 package fixed this crash on my Arch Linux.
Yes, looks like this was an issue with `plasma-wayland-protocols` which was fixed by: https://invent.kde.org/libraries/plasma-wayland-protocols/-/commit/404ae95b.patch and Arch seems to have patched it. https://bugs.archlinux.org/task/67430 https://github.com/archlinux/svntogit-packages/commit/362b418cfa4ebd9dbe3e3d099a205584ee9202e1 https://github.com/archlinux/svntogit-packages/commit/bb942dfdf20b1868e8ac6248f5869443b0d96bab
*** Bug 424834 has been marked as a duplicate of this bug. ***
Does this need any tagging as a packaging bug for KDE Neon User? Or a way to expedite the backport?