| Summary: | autosters systemsetting's module does not start pre-KDE scripts | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Salvatore Brigaglia <opensourcecat> |
| Component: | kcm_autostart | Assignee: | Laurent Montel <montel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Salvatore Brigaglia
2009-02-25 14:34:22 UTC
"pre-KDE startup" scripts are put under ~/.kde/env. As the folder name implies, those scripts are used to setup the environment for the whole KDE session, so they are "sourced", not "executed".
Here is the relevant part in startkde.
# Source scripts found in <localprefix>/env/*.sh and <prefixes>/env/*.sh
# (where <localprefix> is $KDEHOME or ~/.kde, and <prefixes> is where KDE is installed)
#
# This is where you can define environment variables that will be available to
# all KDE programs, so this is where you can run agents using e.g. eval `ssh-agent`
# or eval `gpg-agent --daemon`.
# Note: if you do that, you should also put "ssh-agent -k" as a shutdown script
#
# (see end of this file).
# For anything else (that doesn't set env vars, or that needs a window manager),
# better use the Autostart folder.
libpath=`kde4-config --path lib | tr : '\n'`
for prefix in `echo "$libpath" | sed -n -e 's,/lib[^/]*/,/env/,p'`; do
for file in "$prefix"*.sh; do
test -r "$file" && . "$file"
done
done
|