https://bugs.kde.org/show_bug.cgi?id=439481
--- Comment #21 from Konstantin Kharlamov <hi-an...@yandex.ru> --- (In reply to David Edmundson from comment #20) > Because you're creating a within a system that covers something we have > already only worse as it's via a propriety undocumented env var. I might be missing something: I don't currently see a way to properly cover replacing a WM while having Plasma systemd-boot enabled. An approach that has been suggested (here and on duplicates) is basically editing systemd-service dependencies, so a custom WM is started instead of kwin_x11. There's a problem though: that would render you unable to start Plasma with kwin anymore. IOW, with the KDEWM-way documented on wiki (and on github, which I assume was the original source) allows you to choose in SDDM between a "vanilla" Plasma session with kwin and the custom one with i3wm/whatever-wm. The "edit dependencies" approach requires you to hack around in a VTY if you wanted to switch between the kwin and i3wm sessions. And no more nice GUI option for you. > Turning the question around, if you were to build from scratch, why would > choosing a WM go via an env var? I see! So, what you're up against is specifically having the env. variable. That means if we'd find a way to implement the functional with systemd but without the variable, that might be accepted. Okay. With that said, I don't currently have a solution to that problem. I'll have to think, perhaps I'll figure something out. -- You are receiving this mail because: You are watching all bug changes.
