Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
MOD:
I got is 3/4 working. the icons are not showing up right away.
marking solved
instructions
Quote:
Session Scripts
E16 can automatically run user scripts or applications during Startup, Restart, and Shutdown. This facilitates the loading of system tray applets, rss readers, screen savers, and other daemons (e.g. dbus), and allows for cleanup of programs that don’t terminate properly when e16 quits (this is especially common with KDE applications in e16 and the arts daemon or dcop server keeps running).
The session script feature is controlled by the configuration keys (shown with default values):
misc.session.enable_script is a boolean. When set to 1, e16 will execute the script in the misc.session.script key. By default, this feature is disabled. When enabled, it will do nothing until the home directory ($ECONFDIR — normally ~/.e16) is configured.
The default session.script is located in $EROOT/scripts/session.sh ($EROOT is normally /usr/share/e16 or /usr/local/share/e16). It will look for directories in the user’s $ECONFDIR/ (~/.e16/) called:
~/.e16/ ($ECONFDIR)
Init/
Start/
Stop/
and run any and/or all scripts or executables in each when e16 starts, restarts, and shuts down. If no scripts or executables are present, or if any of the directories Init, Start, and Stop do not exist, nothing will happen and e16 will start up as usual. So, in order to use session scripts, all the user has to do is to populate the Init, Start, and Stop directories with scripts, applications, or links to applications that should run during Startup, Restart, or when e16 is stopped.
The user may write a custom script and place it anywhere. Simply modify the config file by using:
$ eesh set misc.session.script myscript
and modify it (be sure to chmod +x the file otherwise it won’t run). The session script is called with one of three command parameters; init, start, and stop. Any custom script should have a code block similar to this in order to function properly in e16.
case "$1" in
init)
# do blah
# or do function init
start)
# do blah
# of do function start
stop)
# do blah
# or do function stop
esac
Automatic script running can be enabled/disabled in the Settings Dialog under "Session", or by setting misc.session.enable_script key to 1/0:
$ eesh set misc.session.enable_script 1/0
This process is very flexible since when used, the user can turn off individual scripts and applications by chmod -x or simply leave the startup directories empty or remove them.
commands issued
Quote:
eesh set misc.session.enable_script 1
eesh set misc.session.script $HOME/bin/e16.autostart.sh
scripts
Quote:
Location = $HOME/bin/e16.autostart.sh
#!/bin/sh
case "$1" in
init)
# do blah
# or do function init
start)
e16autostart.sh
# do blah
# of do function start
stop)
# do blah
# or do function stop
esac
#DEBUG
echo "Srarted" > $HOME/e16startappsstarted
# Start DBUS session bus: for automount
if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval $(dbus-launch --sh-syntax --exit-with-session)
fi
#mapfile -t startapps < /usr/local/bin/e16startapps
#mapfile -t startapps < /home/userx/Dropbox/GNUstep/e16startapps
mapfile -t startapps < $HOME/bin/e16startapps
for p in ${startapps[@]} ;
do
which "$p" >/dev/null && "$p" &
echo "Sp" >> $HOME/e16startappsstarted
done
$HOME/bin/e16loadbackgrounds
----------------------------------
userx@slackdog.pen:~
$ bin/e16.autostart.sh
bin/e16.autostart.sh: line 8: syntax error near unexpected token `)'
bin/e16.autostart.sh: line 8: `start)'
userx@slackdog.pen:~
#!/bin/sh
case "$1" in
init)
# do blah
# or do function init
start) <--- line 8
e16autostart.sh
# do blah
# of do function start
stop)
# do blah
# or do function stop
esac
fixed add ;; in each case
it still does not work on login. I tested all of the scripts on the cli this one "bin/e16.autostart.sh" does not fire off the e16autostart.sh
this script in ~/.e16/Start/e16autostart.sh works
Code:
$.e16/Start/e16autostart.sh
HEHEHEHH
/media/storage/wallpaper/backgrounds
Loading files from list ...
Done loading files from list.
Randomizing files ...
Files Now Randomized.
starting timer
available 0dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-158.4.4564/cryptography.hazmat.bindings._openssl.cpython-38-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-158.4.4564/cryptography.hazmat.bindings._padding.cpython-38-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-158.4.4564/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.