This message is a placeholder that will be edited in the future
Snapd cooperates with systemd to track processes of snap applications. Normally this is transparent to the user but in certain configurations this may not work due to how the identity of the user was established by the Linux kernel, and the low-level mechanisms in userspace.
When a user logs in locally or remotely, PAM initialized a systemd user session. Systemd user session provides interaction points that snapd relies on when launching snaps. When a given user identity is switched with mechanisms that manipulate the effective user ID, no such session is created and snapd cannot operate normally.
If you are seeing this message then one of the following cases are happening:
- You are using an older Linux distribution that does not support systemd running in user session. You may consider upgrading to a more recent release where that is no longer the case.
- You are running an up-to-date Linux distribution but you are creating processes with a given user ID without launching the corresponding user session. You may consider using the logind linger functionality to work around that
loginctl enable-linger USER.