FWIW systemd --user is expected to have been started as part of your
session. This is supposed to be fully automatic. I don't think you can
start it yourself, as it's up to systemd/logind to properly start the
process and move it to the right cgroup. I've added systemd to the bug
report, so maybe this time it will get some traction.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
