recentpopularlog in

kme : autostart   5

systemd/User - ArchWiki []
I used this setup for manservant (

<code class="language-ini">
Description=Run manservant on port 9292
# source:

ExecStart=/home/username/.gem/ruby/2.5.0/bin/bundle exec rackup


Then I enabled it with 'systemctl --user enable manservant.service' and I think that was basically it (?).
systemd  initscripts  linux  sysadmin  autostart  manservant  maybesolution 
june 2016 by kme
[ubuntu] Startup programs not starting - Page 2
It sounds like Gnome is starting as a Failsafe session.

I guess Microsoft was doing all right when they plastered all those "Safe Mode" warnings all over the desktop when you F8-ed to Safe Mode.

Some interesting tidbits (that didn't solve my problem)
Just to rule out permission issues, please check the permissions of files in the following directories:
In the first directory, you should see files like *.desktop owned by root with permission 644. Example:
-rw-r--r-- 1 root root 467 2009-11-28 19:46 at-spi-registryd.desktop

In the second, the files should be owned by the user with permission 644. My guess is that the settings in .config override the one in /etc/.
Now when you create your own startup script, it should end up in ~/.config/autostart. If you edit that script, you should have the line:

Where I am trying to get at here is a workaround. If a daemon is not autostarting by itself, you could just save it with a different name or comment in your startup options. You can then make sure that the X-GNOME-Autostart-enabled=true is set in that desktop configuration file
gnome2  ubuntu  autostart  annoyance  solution 
january 2014 by kme

Copy this bookmark:

to read