![]() ![]() Jun 15 13:09:30 ubuntu audit: AVC apparmor="DENIED" operation="capable" profile= "/snap/ core/13308/ usr/lib/ snapd/snap- confine" pid=8624 comm="snap-confine" capability=38 capname="perfmon" Jun 15 13:09:30 ubuntu audit: AVC apparmor="DENIED" operation="capable" profile= "/snap/ core/13308/ usr/lib/ snapd/snap- confine" pid=8624 comm="snap-confine" capability=12 capname="net_admin" Jun 15 13:09:30 ubuntu dbus-daemon: Activated service 'org.freedeskto p.systemd1' failed: Process org.freedesktop. systemd1' requested by ':1.60' (uid=1000 pid=8624 comm="/ snap/bin/ firefox " label="unconfined") Jun 15 13:09:30 ubuntu dbus-daemon: Activating service name='org. This is what I get in journalctl when trying to start firefox: Perhaps reviewing the user logs (journalctl -user) could help uncover the problem. I'm afraid I don't know enough about your setup to guess what could be wrong there and why the user instance may have exited. ![]() In the log it's clearly indicated that it failed and systemd exited, thus no scope and the app cannot be run, because the confinement would break your session cgroup (.slice/session-1.scope). The setup is done by talking to your `systemd -user` instance. Unfortunately this is the only way to set this up on a cgroup v2 system. The scope is needed so that the app can run in a separate cgroup which is then confined to access specific devices. When snap starts the /usr/bin/snap binary tries to create a scope for the application. Perhaps reviewing the user logs (journalctl -user) could help uncover the problem.ģ 15:21:45.540312 tracking.go:45: DEBUG: creating transient scope ģ 15:21:45.547127 tracking.go:290: DEBUG: StartTransientUnit failed with ".Spawn.ChildExited": In the log it's clearly indicated that it failed and systemd exited, thus no scope and the app cannot be run, because the confinement would break your session cgroup (.slice/ session- 1.scope). ChildExited" : ģ 15:21:45.547174 cmd_run.go:1187: DEBUG: snapd cannot track the started applicationģ 15:21:45.547199 cmd_run.go:1188: DEBUG: snap refreshes will not be postponed by this process Ok, so the logs you attached earlier are:ģ 15:21:45.540312 tracking.go:45: DEBUG: creating transient scope snap.chromium. ![]() UpgradeStatus: Upgraded to impish on (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ![]() InstallationDate: Installed on (568 days ago) Also, it doesn't mention the error message I'm seeing. Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? But I tried the same thing substituting chromium-browser for firefox, and it didn't help: chromium fails with the same error message. With firefox, I was able to fix the problem with: slice/session- 1.scope is not a snap cgroup where NNN is my uid On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). I just upgraded from hirsute to impish using do-release-upgrade. ![]()
0 Comments
Leave a Reply. |