[systemd-devel] User services won't start at login after switch from homed user to regular user
Hi, I'm having a problem with user services not starting at login. I had initially set up my user using systemd-homed and everything was working fine, including some user services that I started at login (e.g., offlineimap, spotifyd). However, I wanted to move my home to a different disk (the original home used a full encrypted disk and I couldn't figure out how to have homed recognize the new disk as home) and decided to go back to a regular user rather than a homed user. So I removed the original user (the files were on the encrypted disk, so they weren't deleted), disabled systemd-homed.service, mounted the disk that had my files, created the new user (with a new encrypted home on a different disk, opened automatically through pam at login), copied all the files to the new home and then chowned the files (the user name was the same but the UID of the new user was the default 1000 instead of the default UID set by homed). Everything works fine except that now none of the user services that previously worked will start at login. When I try to enable them, a symlink is created in .config/systemd/user/default.target.wants, but they are not started at login. They all start fine if started manually, but they won't start at login, even though systemctl --user list-unit-files says they are enabled. I'm not 100% sure that this is due to the switch from the homed user to the regular user, but the services stopped working when I made that change. Any advice about getting these services working again? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: Re: Antw: [EXT] Re: Q: Debugging missing requirements
>>> Dave Howorth schrieb am 12.02.2021 um 16:17 in Nachricht <20210212151718.1ff9b...@acer-suse.lan>: > On Fri, 12 Feb 2021 18:04:58 +0300 > Andrei Borzenkov wrote: >> 12.02.2021 10:04, Ulrich Windl пишет: >> Andrei Borzenkov schrieb am 11.02.2021 um >> 15:20 in >> > Nachricht >> > : >> >> On Thu, Feb 11, 2021 at 1:47 PM Ulrich Windl >> >> wrote: >> >>> >> >>> Hi! >> >>> >> >>> Suspecting systemd added some requirement that isn't fulfilled >> >>> after boot, >> >> preventing my units from starting I wonder: >> >>> How can I debug systemd's requirements checking for units that >> >>> are enabled, >> >> but not started at boot (status "inactive (dead)"? >> >> >> >> Usual advice is - enable debug logging. >> > >> > Can I enable this for a specific unit, or just globally? >> >> Not that I am aware of. It is all or nothing. > > But you don't need to look at them all for other units. You can use > --priority to view just the levels you wish to. So there'll be more > information in the log files, but no need to look at it unless you wish > to. Still it would sound like a nice feature: Enabling and disabling unit debugging at run-time. Something like systemctl loglevel=debug unit... > >> >> >> >>> Or another way: Can I list the dependencies that systemd added >> >> automatically? >> >>> >> >> >> >> If you mean implicit or default dependencies - no. They are listed >> >> in man pages, although there is no guarantee that list is >> >> complete. Your best bet is source code. >> > >> > >> > >> > >> >> ___ >> systemd-devel mailing list >> systemd-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
