systemd not seeing my user units after reboot

From	"Victor A. Stoichita" <victor@svictor.net>
Newsgroups	linux.debian.user
Subject	systemd not seeing my user units after reboot
Date	2019-08-23 07:50 +0200
Message-ID	<yyaCt-7U2-1@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi,

I have some custom systemd units in ~/.config/systemd/user
In Debian 9 I could start my ~/.config/systemd/user/foo.service 
after reboot and login simply with 
$ systemctl --user start foo.service

Since I upgraded to Debian 10, I need to issue a prior
$ systemctl --user daemon-reload

If I don’t daemon-reload first, systemctl answers that "Unit 
foo.service not found". This carries the additional problem that 
when foo.service is enabled to start automatically after boot, it 
no longer starts automatically.

Could it be relevant that my home folder is encrypted with 
ecryptfs? How can I check whether it is now decrypted before or 
after systemd starts its user instance?
I’m interested in any other pointers about what could have changed 
in the upgrade and how I could to debug this.

Victor

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

systemd not seeing my user units after reboot  "Victor A. Stoichita" <victor@svictor.net> - 2019-08-23 07:50 +0200
  Re: systemd not seeing my user units after reboot Sven Hartge <sven@svenhartge.de> - 2019-08-23 08:50 +0200
    Re: systemd not seeing my user units after reboot "Victor A. Stoichita" <victor@svictor.net> - 2019-08-23 15:20 +0200
      Re: systemd not seeing my user units after reboot Sven Hartge <sven@svenhartge.de> - 2019-08-23 16:10 +0200
        Re: systemd not seeing my user units after reboot "Victor A. Stoichita" <victor@svictor.net> - 2019-08-23 17:20 +0200
          Re: systemd not seeing my user units after reboot Sven Hartge <sven@svenhartge.de> - 2019-08-23 20:20 +0200

csiph-web