https://bugs.kde.org/show_bug.cgi?id=389144
--- Comment #4 from Max Harmathy <max.harma...@web.de> --- (In reply to Kai Uwe Broulik from comment #3) > So, what prevents you from using shutdown scripts instead? There's not much > going on in startkde after ksmserver has quit. Then the code following ksmserver in startkde should probably be moved to a shutdown script itself. As for our specific use case: We will find a solution (probably not upstream suitable), that won't require too much refactoring on our side. But that should not be an issue for this ticket. > I agree this is a bug but requires significant re-engineering of the startup > and session handling code that is decades old and probably becomes obsolete > with Wayland anyway. Well with wayland there is "startplasmacompositor" which starts "kwin" which starts "startplasma" which is more or less a copy of "startkde". Thus basically there is the same problem for now. Or are there plans to replace ksmserver? > > although the documentation in plasma-desktop states they would be executed > > by startkde > > Where can I find this documentation? I guess I got confused by the comment of Autostart::load in https://cgit.kde.org/plasma-desktop.git/tree/kcms/autostart/autostart.cpp That is probably just a copy and paste slip. The autostart documentation correctly only states that "$HOME/.config/plasma-workspace/env" is executed by "startkde". https://cgit.kde.org/plasma-desktop.git/tree/doc/kcontrol/autostart/index.docbook -- You are receiving this mail because: You are watching all bug changes.
