Ok, from a bit more testing yesterday evening it seems all scripts put into ~/.config/plasma-workspace/env/ work fine for startup, and in ~/.config/plasma-workspace/shutdown/ for shutdown. These are correctly shown in the kcm and are sourced at startup and shutdown. With that solution there's probably no need for ~/.config/ksmserver-autostart or whatnot. The way I see it this should be documented well, and the kcm needs to be adjusted to not show scripts from ~/.config/autostart since kinit wont be starting those.
On Fri, Nov 7, 2014 at 1:24 PM, Ingo Klöcker <kloec...@kde.org> wrote: > On Thursday 06 November 2014 22:01:13 Jeremy Whiting wrote: >> Hey all, >> >> In kdelibs4 times one used to be able to put any script into >> ~/.kde/Autostart/ make it executable and when startkde ran it would >> launch those scripts. In kf5/plasma next time ~/.config/autostart >> should be able to do likewise, but doesn't seem to. On one hand the >> autostart kcm shows scripts there under a Scripts header and lets you >> choose whether they should be ran at startup, or shutdown, or Pre-KDE >> startup, yet they are never launched. >> >> I took a look at the kinit klauncher autostart code and it only ever >> looked for .desktop files under these autostart paths, even in my >> clone of kdelibs it never looked for anything without a .desktop >> extension. How did launching of non .desktop file stuff ever work? > > Hmm. I've always put shell scripts that should be run on each start in > ~/.kde/env. (IIRC all *.sh files in this folder are source'd by KDE > start script.) > > What's the kf5-equivalent for this folder? > > > Regards, > Ingo
