Plasma 6 issues

[wcrabtree9]

My computer updated to Plasma 6 last night and I noticed a few things so far.

1. Plasma now defaults to Wayland over X11. I've been on X11, so I had to check that as I log in.

2. Some keyboard shortcuts aren't working. Not sure how widespread that issue is, but I know Meta+Shift+E isn't working anymore. I'll test more when I get home tonight, I updated before going to bed and didn't have the chance then. EDIT: Forgot to mention that I can press the physical power button on my PC to bring up the sleep/reboot/shutdown menu instead, but none of the options will work. It just goes back to the desktop.

[wcrabtree9]

So changed my line in the i3 config file for using the Plasma logout screen to this:

bindsym $mod+Shift+e exec --no-startup-id qdbus-qt5 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptLogout

Based on this post: https://discuss.kde.org/t/what-command-to-display-the-sddm-shutdown-screen-on-plasma-6/11382
Meta+Shift+E now opens the screen, but still none of the options work.

[Reload-Reboot]

So changed my line in the i3 config file for using the Plasma logout screen to this:

bindsym $mod+Shift+e exec --no-startup-id qdbus-qt5 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptLogout

Based on this post: https://discuss.kde.org/t/what-command-to-display-the-sddm-shutdown-screen-on-plasma-6/11382 Meta+Shift+E now opens the screen, but still none of the options work.

I noticed this issue aswell when I upgraded a few hours ago. It seems that when you call the logout process on KDE 6 it attempts to invoke KWin for the different processes such as shutdown and logoff, but this is a problem considering we are replacing KWin with i3, so KWin can't be active at the same time as i3. I honestly have no idea if there is an alternative way to bypass KWin to logout anymore considering that plasma 5 used the ksmserver to invoke logging out previously and that worked fine, but now that's changed.

[Reload-Reboot]

Okay, so I'm a moron and I did some more digging and realized it's not KWin's fault, and it is actually the polkit authenticator agent, which is disconnected for some reason. Ignore the scuffed screenshot for the second image it's scrot acting strange, but the culprit appears to be polkit and it's authenticator agent not connecting properly when kde launches with i3.

[browser-bug]

Sorry for the intrusion but since this issue could become a general discussion place for Plasma 6 integration, could I ask if you found the need to have some different configuration with respect to the original? Aside from what you've already discussed.

[wcrabtree9]

Sorry for the intrusion but since this issue could become a general discussion place for Plasma 6 integration, could I ask if you found the need to have some different configuration with respect to the original? Aside from what you've already discussed.

Just this line change, but I'm wondering if it will change again on the next Plasma update. And there may be a better solution than this, I just posted the first thing I got to work.
bindsym $mod+Shift+e exec --no-startup-id qdbus-qt5 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptLogout

[browser-bug]

Sorry for the intrusion but since this issue could become a general discussion place for Plasma 6 integration, could I ask if you found the need to have some different configuration with respect to the original? Aside from what you've already discussed.

Just this line change, but I'm wondering if it will change again on the next Plasma update. And there may be a better solution than this, I just posted the first thing I got to work. bindsym $mod+Shift+e exec --no-startup-id qdbus-qt5 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptLogout

The prompt is showing up but I guess the real issue is with the KWin / polkit authenticator agent which showed @ChodyFlims . Hope to get solutions and support for that.

[varad-kadam]

Facing the same, I'd also like to add the task bar has has lost all cosmetics. It's still fully functional, but more like a black bar across the screen.

[DMaroo]

Hi everyone, I have figured out a solution for this. If we check the journalctl log, we find that no response from KWin is actually the reason behind the shut down not going through. The ksmserver (KDE session manager) requests KWin to close all wayland windows through a DBus method. Since we are not running KWin when using i3, this request does not go through and the shutdown is aborted.

Hence, I have written a fake KWin DBus service (< 30 lines) which, when run, makes sure that the shutdown/logout/restart does not hang up. Here is the code: https://github.com/DMaroo/fakwin. There are build instructions and links to the relevant KDE code in the readme.

[Hi-Angel]

Hi everyone, I have figured out a solution for this. If we check the journalctl log, we find that no response from KWin is actually the reason behind the shut down not going through. The ksmserver (KDE session manager) requests KWin to close all wayland windows through a DBus method. Since we are not running KWin when using i3, this request does not go through and the shutdown is aborted.

Hence, I have written a fake KWin DBus service (< 30 lines) which, when run, makes sure that the shutdown/logout/restart does not hang up. Here is the code: https://github.com/DMaroo/fakwin. There are build instructions and links to the relevant KDE code in the readme.

Looks amazing! Did you consider though changing the ksmserver instead, so when the request reports an error it is ignored and the service proceeds with shutting down?

[DMaroo]

Changing ksmserver would require patching the /usr/bin/plasma-shutdown binary, which would not be a particularly stable/reliable/robust way to go about it. I feel that having a fake service makes it easy to change the behavior of KDE in the least intrusive way.

[Hi-Angel]

could I ask if you found the need to have some different configuration with respect to the original? Aside from what you've already discussed.

On Archlinux I did, but it looks like some Arch packaging bug rather than something to do with KDE6. The file /usr/share/xsessions/plasma-i3.desktop disappeared and I had to re-create it.

[varad-kadam]

On Archlinux I did, but it looks like some Arch packaging bug rather than something to do with KDE6. The file /usr/share/xsessions/plasma-i3.desktop disappeared and I had to re-create it.

Could you please explain how you got i3 to work with plasma?
For Option 1 I changed systemctl mask plasma-kwin_x11.service --user to systemctl mask plasma-kwin_wayland.service --user but I just get a blank black screen with no cursor when logging in.

Tried Option 2, changed Exec=env KDEWM=/usr/bin/i3 /usr/bin/startplasma-x11 to Exec=env KDEWM=/usr/bin/i3 /usr/bin/startplasma-wayland, still no luck however.

[Hi-Angel]

Could you please explain how you got i3 to work with plasma? For Option 1 I changed systemctl mask plasma-kwin_x11.service --user to systemctl mask plasma-kwin_wayland.service --user but I just get a blank black screen with no cursor when logging in.

Why did you change it? I didn't touch kwin_wayland at all, I only had to mask kwin_x11.service.

Did you create'n'enable plasma-i3 user service?

(worth noting though, I've used i3 + KDE before they migrated to systemd user services, so I have had an XSession file that starts i3, which I've been using till now. However, now that you commented I tested running the usual "KDE X11" session and it starts i3 + KDE for me as well, so you don't have to create an XSession file).

Tried Option 2

Option 2 I didn't test as I don't want to disable systemd support in KDE.

[varad-kadam]

Why did you change it? I didn't touch kwin_wayland at all, I only had to mask kwin_x11.service.

Are you still logging in with X11?
I'm using SDDM, and I have an option to sign in with either X11 or Wayland after the update.
If I didn't change the name, it would only apply with signing in with X11.

Yes, I have all the files (along with correct permissions and settings I'm assuming) as I was using i3 + KDE before the update just fine.

Funny thing is after I went back and followed the instructions again, it always starts with kwin no matter what I try to disable or mask.

[Hi-Angel]

Why did you change it? I didn't touch kwin_wayland at all, I only had to mask kwin_x11.service.

Are you still logging in with X11? I'm using SDDM, and I have an option to sign in with either X11 or Wayland after the update. If I didn't change the name, it would only apply with signing in with X11.

Yes, I log in with X11. i3 is an X11 thing, it's not applicable to Wayland.

If you want KDE with tiling in Wayland, you might have to try built-in tiling in kwin that they added an year ago and should be part of KDE6. Checking it out has been on my todo list for a long time but I still haven't gotten to it. You might try it if you feel motivated 😊

Funny thing is after I went back and followed the instructions again, it always starts with kwin no matter what I try to disable or mask.

Just to be clear: among other things that you tried, did you try masking out kwin_x11, enabling plasma-i3, and then logging into KDE X11 session?