jpwhiting at kde.org
Fri Nov 7 21:47:17 GMT 2014
Yep, I see what $XDG_CONFIG_DIRS/autostart/*.desktop is for, my only
question is that if there are non .desktop files in there too, we are
showing them in the autostart kcm, yet we aren't autostarting them :)
I really need to get the kcm patch ready for review, not showing those
scripts and documenting on userbase that startup scripts to be ran
before go into .config/plasma-workspace/env/ and anything to run after
needs to have a .desktop file in .config/autostart/ fixes all problems
from what I see.
On Fri, Nov 7, 2014 at 1:44 PM, Thomas Lübking
<thomas.luebking at gmail.com> wrote:
> On Freitag, 7. November 2014 21:28:15 CEST, Jeremy Whiting wrote:
>> 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.
> $XDG_CONFIG_DIRS/autostart/*.desktop is supposed to be started AFTER the
> session is initialized, what is different from
> ~/.config/plasma-workspace/env/ (etc.) which is supposed to be run BEFORE
> the session starts, ie. you'd export session wide env vars there, but launch
> applications which must talk to <service here> in the autostart folder.
> Check your $XDG_CONFIG_DIRS and $XDG_CONFIG_HOME variables, see whether
> that's the reason and otherwise i'd suggest to file a bug against whatever
> component holds the session startup script.
More information about the kde-core-devel