*** This bug is a duplicate of bug 1951491 ***
https://bugs.launchpad.net/bugs/1951491
2022/01/10 12:58:44.388636 tracking.go:185: DEBUG: using session bus
2022/01/10 12:58:44.393780 tracking.go:290: DEBUG: StartTransientUnit failed
with "org.freedesktop.DBus.Error.Spawn.ChildExited": [Process
org.freedesktop.systemd1 exited with status 1]
2022/01/10 12:58:44.393815 cmd_run.go:1187: DEBUG: snapd cannot track the
started application
Indicates that snap asked systemd to create a new scope for the
application (since establishing device filtering in your current cgroup
would break your session), but that failed. Judging by the error
message, `systemd --user` exited or was restarted, hard to tell.
Unfortunately there is nothing snapd can do about that.
** This bug has been marked a duplicate of bug 1951491
Can't run snaps: .slice/session-1.scope is not a snap cgroup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956942
Title:
snap can not start chromium-browser with cgroup v2 and hierarchy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1956942/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
