No, it just means that the journal is not collecting any user session
logs. I'm afraid this is beyond snapd scope at this point. Perhaps you
can try to make you openbox session to be more like what GNOME and KDE
set up, that is with systemd user instance that can be accessed via
dbus. I don't know how you log in, maybe to need to tweak the PAM config
so that pam_systemd is included, though I'm far from being expert here
and the user sesion setup has become crazy complicated.
Anyways, the snapd part is working as expected, such that if a separate
cgroup for the snap cannot be created it stops before breaking the one
your session is in.
** Changed in: snapd (Ubuntu)
Status: Incomplete => Invalid
--
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
