Wayland + KDE - Control-C logs user out.

robbak

robbak

Recent ports updates have seen my -CURRENT workstation get upgraded to Wayland. Fairly smooth change, actually, as if it wasn't for this error, I wouldn't have even noticed.

But now, if I use Control-C in any program, trying to copy some text, the X/KDE/Plasma session abruptly ends and I return to the sddm window.

I can copy using the backup shortcut control-insert. This does not cause any problems - although muscle memory is strong!

I also switched the session back to Plasma (X11), and copying using Ctrl-C works without an issue.

I'd like to know if anyone else experiences this, if there is a workaround (apart from ctrl-insert), and if there is a likely fix.

And also, to let you know what a weird bug this is!
 
I had the same issue, as I hadn't noticed that the SDDM profile had changed to KDE(Wayland) after the KDE port update. I was surprised as this hadn't ever worked before. Switching back to X11 and everything is working properly as before.

There is however a another problem with KDE under Wayland in that after waking from sleep, a screen showing all of the login credentials used initially is shown!
 
I was a developer for PCLinuxOS (which uses consolekit instead of elogind like us) and this was an issue I ran into when I finally got Wayland working there, but it's not a fault of KDE but rather SDDM.

My issue:
github.com

Ctrl key issue when launching Wayland session with SDDM · Issue #1986 · sddm/sddm

Whenever a Wayland session is launched with SDDM 0.21 (tried labwc and Plasma Wayland), pressing a combination like Ctrl + C crashes the environment. Launching from the TTY works fine, such as ck-l...
github.com github.com

And now others are mentioning the same thing:
https://github.com/sddm/sddm/issues/2101 (this guy is from another distro which doesnt use elogind)
https://bugs.kde.org/show_bug.cgi?id=505552 (FreeBSD)
 
You must log in or register to reply here.
Back
Top