Where Are Linux Autostart Entries Stored?
Linux desktops autostart apps from .desktop files in your autostart folder, with system wide defaults layered beneath.
Last updated
Desktop Linux borrows Windows' startup folder idea with freedesktop paperwork. Each autostart entry is a .desktop file naming the command, its delay, and which desktops may run it.
User entries override system ones by filename, so disabling a vendor autostart never requires editing vendor files. The common failure is an entry that looks right but references a missing binary or a Wayland incompatible flag. Logs name the culprit while the desktop stays silent.
Where Linux stores this, by platform
~/.config/autostart
One .desktop file per autostarted app. User files override /etc/xdg/autostart by name. Check Exec paths and session compatibility when entries silently fail.
Frequently asked questions
How do I stop a system service from autostarting?
Copy its .desktop file from /etc/xdg/autostart into ~/.config/autostart and add Hidden=true. The user copy overrides the system one without touching packages, surviving updates that would restore edited system files.
Why does my autostart entry not run?
Check the executable bit, absolute Exec paths, and OnlyShowIn desktop limits. Wayland sessions ignore some X11 oriented entries, and a failing Exec silently does nothing. Desktop logs reveal the attempt.
Notice an outdated path? Let us know.