This forum has been archived. All content is frozen. Please use KDE Discuss instead.

After updating to 5.25 KDEWM ignored by startplasma-x11

Tags: None
(comma "," separated)
skeletonadventure
Registered Member
Posts
2
Karma
0
Today I updated to Plasma 5.25, and upon logging in Kwin started instead of my set WM.
I had changed the WM to XMonad as directed by https://userbase.kde.org/Tutorials/Using_Other_Window_Managers_with_Plasma almost a year ago with the this script located at ~/.config/plasma-workspace/env/
Code: Select all
#!/bin/sh
export KDEWM=$HOME/.local/bin/xmonad

Upon it suddenly not working, I checked that the variable was set, and it was. I also started XMonad manually and saw that it was still working. So then I followed the other part of this tutorial and created a new xsession, and removed my usage of $HOME just to be safe:
Code: Select all
#!/bin/sh
export KDEWM=/home/skeleton/.local/bin/xmonad
/usr/bin/startplasma-x11

This, unfortunately does not make any difference. I am at a total loss and have no idea how to further troubleshoot this issue, any help would be very appreciated.
shfjorm
Registered Member
Posts
2
Karma
0
Hi i don't know if my message is relevant but I have the very same issue with i3

.xinitrc has

export KDEWM=/usr/bin/i3
export MOZ_DBUS_REMOTE=1
export XDG_CURRENT_DESKTOP=KDE
export KDE_FULL_SESSION=true
export GTK_USE_PORTAL=1
exec startplasma-x11
skeletonadventure
Registered Member
Posts
2
Karma
0
Finally, I have found some information on this problem, here some new ways to set your WM.
From the Arch Wiki you can disable systemd startup: https://wiki.archlinux.org/title/KDE#systemd_startup
And from here using method B you can keep systemd startup enabled: https://gist.github.com/TJuberg/75f7787f66277b6a6400b45e6b63351e
Rather frustratingly, information of the effects this has for users of alternate window managers was not very forthcoming. This could have been handled much better, such as updating the tutorials accordingly. I have only a good Samaritans on Reddit to thank for pointing users in the direction of this information.
shfjorm
Registered Member
Posts
2
Karma
0
Thanks a lot !
Seems to work.
I don't know yet if there are any side effects but I can deal with because it's easy to go back.

(I had to use
Code: Select all
systemctl --user add-wants plasma-workspace-x11.target i3.service
instead of
Code: Select all
systemctl --user add-wants plasma-workspace@x11.target i3.service


Have a nice day !
User avatar
mito
Registered Member
Posts
18
Karma
0
OS
FYI – here's another resource which helped me troubleshooting this issue:
https://maxnatt.gitlab.io/posts/kde-plasma-with-i3wm/#kde-525-and-newer


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]