You are not logged in.
I've recently encountered this problem since I've moved arch over to an SSD. I'm not sure if this is directly related though. I've implemented a user session as per the systemd/user wiki page. The logs suggest that all of my system and session services seem to stop correctly except for the user-session service. I get a message on shutdown which is something like "a stop job is running for user-session@1000.service". Running systemctl daemon-reload before shutdown fixes this for some reason, even when I haven't edited any of the units. The systemctl -a output is the same before and after the reload, so I don't know how to find out what it is actually doing to fix this. Is there any way to find out what this changes in order to diagnose the problem?
Offline
I have the same problem using systemd user sessions on two separate computers, one without an SSD.
`systemctl daemon-reload` also fixes this for me.
Last edited by kotharia (2013-07-13 07:44:15)
Offline