Purpose of the autostart-scripts directory
Clash Royale CLAN TAG#URR8PPP
A user can place .desktop files in his ~/.config/autostart/ directory to run a script on login (session start) in Gnome, or indeed any Freedesktop-compliant environment.
But, on my openSUSE Leap 42.2 Gnome 3 system, in addition to each user's ~/.config/autostart/ directory, each user also has a ~/.config/autostart-scripts/ directory. I would assume that this directory would serve as a dumping ground for any quick and dirty scripts that a user would want to run on login without having to wrap those scripts in a .desktop file, but the scripts I place in that directory do not run on login.
Search engines have provided very little in the way of details about this directory. Does anyone know the purpose of the ~/.config/autostart-scripts directory and the requirements for the scripts in it to run?
scripting login gnome3 freedesktop
edited May 23 '17 at 12:40
Community♦
1
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
add a comment |
A user can place .desktop files in his ~/.config/autostart/ directory to run a script on login (session start) in Gnome, or indeed any Freedesktop-compliant environment.
But, on my openSUSE Leap 42.2 Gnome 3 system, in addition to each user's ~/.config/autostart/ directory, each user also has a ~/.config/autostart-scripts/ directory. I would assume that this directory would serve as a dumping ground for any quick and dirty scripts that a user would want to run on login without having to wrap those scripts in a .desktop file, but the scripts I place in that directory do not run on login.
Search engines have provided very little in the way of details about this directory. Does anyone know the purpose of the ~/.config/autostart-scripts directory and the requirements for the scripts in it to run?
scripting login gnome3 freedesktop
edited May 23 '17 at 12:40
Community♦
1
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
Glad that I'm not the only one wondering about this cryptic directory. Obviously your synopsis per the Freedesktop spec for theautostartdirectory is straight from the Freedesktop docs; and as forautostart-scripts, KDE Plasma 5 behaves exactly as you assume: it executes any executables in that directory. Not knowing much about GNOME 3, I don't know why it didn't "work" (what does "work" really even mean here?) for you there, but Plasma 5 observes that behavior.
– villapx
Jan 7 at 21:29
Indeed, Plasma 5 hasautostart-scriptshardcoded in its source (along withplasma-workspace/shutdownandplasma-workspace/env): here it is on GitHub. Googling this directory name yields absolutely nothing, though, so it's not part of any standard. I assume the KDE folks just chose it kind of arbitrarily
– villapx
Jan 7 at 21:40
add a comment |
A user can place .desktop files in his ~/.config/autostart/ directory to run a script on login (session start) in Gnome, or indeed any Freedesktop-compliant environment.
But, on my openSUSE Leap 42.2 Gnome 3 system, in addition to each user's ~/.config/autostart/ directory, each user also has a ~/.config/autostart-scripts/ directory. I would assume that this directory would serve as a dumping ground for any quick and dirty scripts that a user would want to run on login without having to wrap those scripts in a .desktop file, but the scripts I place in that directory do not run on login.
Search engines have provided very little in the way of details about this directory. Does anyone know the purpose of the ~/.config/autostart-scripts directory and the requirements for the scripts in it to run?
scripting login gnome3 freedesktop
edited May 23 '17 at 12:40
Community♦
1
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
A user can place .desktop files in his ~/.config/autostart/ directory to run a script on login (session start) in Gnome, or indeed any Freedesktop-compliant environment.
But, on my openSUSE Leap 42.2 Gnome 3 system, in addition to each user's ~/.config/autostart/ directory, each user also has a ~/.config/autostart-scripts/ directory. I would assume that this directory would serve as a dumping ground for any quick and dirty scripts that a user would want to run on login without having to wrap those scripts in a .desktop file, but the scripts I place in that directory do not run on login.
Search engines have provided very little in the way of details about this directory. Does anyone know the purpose of the ~/.config/autostart-scripts directory and the requirements for the scripts in it to run?
scripting login gnome3 freedesktop
scripting login gnome3 freedesktop
edited May 23 '17 at 12:40
Community♦
1
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
edited May 23 '17 at 12:40
Community♦
1
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
edited May 23 '17 at 12:40
Community♦
1
edited May 23 '17 at 12:40
Community♦
1
edited May 23 '17 at 12:40
Community♦
1
1
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
asked Mar 1 '17 at 6:36
palswimpalswim
1,72911733
1,72911733
Glad that I'm not the only one wondering about this cryptic directory. Obviously your synopsis per the Freedesktop spec for theautostartdirectory is straight from the Freedesktop docs; and as forautostart-scripts, KDE Plasma 5 behaves exactly as you assume: it executes any executables in that directory. Not knowing much about GNOME 3, I don't know why it didn't "work" (what does "work" really even mean here?) for you there, but Plasma 5 observes that behavior.
– villapx
Jan 7 at 21:29
Indeed, Plasma 5 hasautostart-scriptshardcoded in its source (along withplasma-workspace/shutdownandplasma-workspace/env): here it is on GitHub. Googling this directory name yields absolutely nothing, though, so it's not part of any standard. I assume the KDE folks just chose it kind of arbitrarily
– villapx
Jan 7 at 21:40
add a comment |
Glad that I'm not the only one wondering about this cryptic directory. Obviously your synopsis per the Freedesktop spec for theautostartdirectory is straight from the Freedesktop docs; and as forautostart-scripts, KDE Plasma 5 behaves exactly as you assume: it executes any executables in that directory. Not knowing much about GNOME 3, I don't know why it didn't "work" (what does "work" really even mean here?) for you there, but Plasma 5 observes that behavior.
– villapx
Jan 7 at 21:29
Indeed, Plasma 5 hasautostart-scriptshardcoded in its source (along withplasma-workspace/shutdownandplasma-workspace/env): here it is on GitHub. Googling this directory name yields absolutely nothing, though, so it's not part of any standard. I assume the KDE folks just chose it kind of arbitrarily
– villapx
Jan 7 at 21:40
Glad that I'm not the only one wondering about this cryptic directory. Obviously your synopsis per the Freedesktop spec for the
autostart directory is straight from the Freedesktop docs; and as for autostart-scripts, KDE Plasma 5 behaves exactly as you assume: it executes any executables in that directory. Not knowing much about GNOME 3, I don't know why it didn't "work" (what does "work" really even mean here?) for you there, but Plasma 5 observes that behavior.– villapx
Jan 7 at 21:29
Glad that I'm not the only one wondering about this cryptic directory. Obviously your synopsis per the Freedesktop spec for the
autostart directory is straight from the Freedesktop docs; and as for autostart-scripts, KDE Plasma 5 behaves exactly as you assume: it executes any executables in that directory. Not knowing much about GNOME 3, I don't know why it didn't "work" (what does "work" really even mean here?) for you there, but Plasma 5 observes that behavior.– villapx
Jan 7 at 21:29
Indeed, Plasma 5 has
autostart-scripts hardcoded in its source (along with plasma-workspace/shutdown and plasma-workspace/env): here it is on GitHub. Googling this directory name yields absolutely nothing, though, so it's not part of any standard. I assume the KDE folks just chose it kind of arbitrarily– villapx
Jan 7 at 21:40
Indeed, Plasma 5 has
autostart-scripts hardcoded in its source (along with plasma-workspace/shutdown and plasma-workspace/env): here it is on GitHub. Googling this directory name yields absolutely nothing, though, so it's not part of any standard. I assume the KDE folks just chose it kind of arbitrarily– villapx
Jan 7 at 21:40
add a comment |
1 Answer
1
active
oldest
votes
I never determined the actual purpose for this directory's existence, but I did tweak my system to make it work as I would expect it to work.
I added a system autostart Desktop file at /etc/xdg/autostart/exec-autostart:
[Desktop Entry]
Exec=autostart-exec.sh
Icon=system-run
# NotShowIn=GNOME # Run in all X environments
Terminal=false
TerminalOptions=
Type=Application
This referenced a script that would call each script in the autostart-scripts directory (using the directory determination from the Autostart spec):
#!/bin/sh
shopt -s nullglob # Ensure shell expansion with 0 files expands to an empty list, rather than trying to read the "*.sh" file
if [ -z "$XDG_CONFIG_HOME" ]; then
XDG_CONFIG_HOME=~/.config
fi
for f in "$XDG_CONFIG_HOME/autostart-scripts/"*.sh; do
test -x "$f" && . "$f" || true
done
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f348321%2fpurpose-of-the-autostart-scripts-directory%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I never determined the actual purpose for this directory's existence, but I did tweak my system to make it work as I would expect it to work.
I added a system autostart Desktop file at /etc/xdg/autostart/exec-autostart:
[Desktop Entry]
Exec=autostart-exec.sh
Icon=system-run
# NotShowIn=GNOME # Run in all X environments
Terminal=false
TerminalOptions=
Type=Application
This referenced a script that would call each script in the autostart-scripts directory (using the directory determination from the Autostart spec):
#!/bin/sh
shopt -s nullglob # Ensure shell expansion with 0 files expands to an empty list, rather than trying to read the "*.sh" file
if [ -z "$XDG_CONFIG_HOME" ]; then
XDG_CONFIG_HOME=~/.config
fi
for f in "$XDG_CONFIG_HOME/autostart-scripts/"*.sh; do
test -x "$f" && . "$f" || true
done
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
add a comment |
I never determined the actual purpose for this directory's existence, but I did tweak my system to make it work as I would expect it to work.
I added a system autostart Desktop file at /etc/xdg/autostart/exec-autostart:
[Desktop Entry]
Exec=autostart-exec.sh
Icon=system-run
# NotShowIn=GNOME # Run in all X environments
Terminal=false
TerminalOptions=
Type=Application
This referenced a script that would call each script in the autostart-scripts directory (using the directory determination from the Autostart spec):
#!/bin/sh
shopt -s nullglob # Ensure shell expansion with 0 files expands to an empty list, rather than trying to read the "*.sh" file
if [ -z "$XDG_CONFIG_HOME" ]; then
XDG_CONFIG_HOME=~/.config
fi
for f in "$XDG_CONFIG_HOME/autostart-scripts/"*.sh; do
test -x "$f" && . "$f" || true
done
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
add a comment |
I never determined the actual purpose for this directory's existence, but I did tweak my system to make it work as I would expect it to work.
I added a system autostart Desktop file at /etc/xdg/autostart/exec-autostart:
[Desktop Entry]
Exec=autostart-exec.sh
Icon=system-run
# NotShowIn=GNOME # Run in all X environments
Terminal=false
TerminalOptions=
Type=Application
This referenced a script that would call each script in the autostart-scripts directory (using the directory determination from the Autostart spec):
#!/bin/sh
shopt -s nullglob # Ensure shell expansion with 0 files expands to an empty list, rather than trying to read the "*.sh" file
if [ -z "$XDG_CONFIG_HOME" ]; then
XDG_CONFIG_HOME=~/.config
fi
for f in "$XDG_CONFIG_HOME/autostart-scripts/"*.sh; do
test -x "$f" && . "$f" || true
done
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
I never determined the actual purpose for this directory's existence, but I did tweak my system to make it work as I would expect it to work.
I added a system autostart Desktop file at /etc/xdg/autostart/exec-autostart:
[Desktop Entry]
Exec=autostart-exec.sh
Icon=system-run
# NotShowIn=GNOME # Run in all X environments
Terminal=false
TerminalOptions=
Type=Application
This referenced a script that would call each script in the autostart-scripts directory (using the directory determination from the Autostart spec):
#!/bin/sh
shopt -s nullglob # Ensure shell expansion with 0 files expands to an empty list, rather than trying to read the "*.sh" file
if [ -z "$XDG_CONFIG_HOME" ]; then
XDG_CONFIG_HOME=~/.config
fi
for f in "$XDG_CONFIG_HOME/autostart-scripts/"*.sh; do
test -x "$f" && . "$f" || true
done
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
answered Mar 7 '17 at 20:23
palswimpalswim
1,72911733
1,72911733
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f348321%2fpurpose-of-the-autostart-scripts-directory%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Glad that I'm not the only one wondering about this cryptic directory. Obviously your synopsis per the Freedesktop spec for the
autostartdirectory is straight from the Freedesktop docs; and as forautostart-scripts, KDE Plasma 5 behaves exactly as you assume: it executes any executables in that directory. Not knowing much about GNOME 3, I don't know why it didn't "work" (what does "work" really even mean here?) for you there, but Plasma 5 observes that behavior.– villapx
Jan 7 at 21:29
Indeed, Plasma 5 has
autostart-scriptshardcoded in its source (along withplasma-workspace/shutdownandplasma-workspace/env): here it is on GitHub. Googling this directory name yields absolutely nothing, though, so it's not part of any standard. I assume the KDE folks just chose it kind of arbitrarily– villapx
Jan 7 at 21:40