SUMMARY AutoStart will not start bash scripts or non Flatpak/Snap based installed applications. STEPS TO REPRODUCE 1. Create a bash script which attempts to start another application, calls a python script, etc... 2. Add this script to AutoStart as a login script 3. Reboot and see if it runs or 1. Add an AutoStart entry for an application that is not a Flatpak or Snap application (something installed via .deb or APT) 2. Reboot and see if it runs OBSERVED RESULT It doesn't start the application on login unless it is installed via Flatpak or Snap. Scripts don't seem to execute either. EXPECTED RESULT It starts the script or application on login. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-46-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 16.0 GiB of RAM Graphics Processor: AMD Radeon RX 5500 ADDITIONAL INFORMATION This shortcut was created through the AutoStart GUI, marked executable, and placed in the ~/.config/autostart directory. [Desktop Entry] Comment[en_US]= Comment= Exec=/home/abystus/Documents/startup.sh GenericName[en_US]= GenericName= Icon=dialog-scripts MimeType= Name[en_US]=startup.sh Name=startup.sh Path=/home/abystus/Documents/ StartupNotify=true Terminal=false TerminalOptions= Type=Application X-KDE-AutostartScript=true X-KDE-SubstituteUID=false X-KDE-Username= Script: (marked executable, at location /home/abystus/Documents/): #!/bin/bash /usr/bin/python /home/abystus/Dropbox/Source/Python/setmicvolumeteams.py Do note that script could be performing any action creating a new file, starting an application, etc... For some odd reason it will not execute on login, and I've even tried creating my own .desktop file to no avail with and without Terminal=true. The python script runs fine if ran from a terminal, so I know it works.
This will be easy to debug in Plasma 6, at least.
Dropbox never autostarts. Have been waiting for months to see this bug fixed. Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-45-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8500 CPU @ 3.00GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Dell Inc. Product Name: OptiPlex 7060
Even using Stacer to have it autostart has no effect. Life goes on...
I've run into this bug twice now on Devuan and Debian bookworm installs. So frustrating. I stumbled on a workaround on this site: https://www.simplified.guide/kde/automatically-run-program-on-startup My fresh install did not have a '~/.config/autostart-scripts' directory. Using the 'Autostart - System Settings' GUI did not create the symlink either. After adding the script in the GUI like normal, run: ~$ mkdir .config/autostart-scripts ~$ cd .config/autostart-scripts ~$ ln -s /path/to/your/script Where /path/to/your/script is the path you gave the GUI (not the path of the .desktop file - why do we need a desktop file)
Very likely related to the old systemd version on those distros (though not on Devuan, which will be experiencing a different issue), whose autostart code that we're using was known to be flaky. Can affected folks on Neon upgrade to the new Neon based on Ubuntu 24.04 and see if that has fixed the issue for them? Thanks!
Wanted to write in to report that KDE Neon Plasma 6.2 has this (Dropbox) issue resolved for me. Yay! :)
I had a feeling. Most of these issues were related to old versions of systemd.