This might not end up being related, but interesting nonetheless: I was hacking on the stable Firefox snap using https://snapcraft.io/overlay
After mounting the overlay `sudo /snap/overlay/current/overlay $(realpath /snap/firefox/current)` I tried to start firefox and it did not launch. I haven't seen this happening with other snaps. The journal contains: Aug 01 10:40:59 thinkpad kernel: audit: type=1400 audit(1722501659.347:4687): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/proc/379042/maps" pid=379042 comm="5" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Aug 01 10:40:59 thinkpad firefox_firefox.desktop[379021]: Content snap command-chain for /snap/firefox/4630/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Do we know if this bug also came with the AppArmor denial? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072395 Title: [snap] Chromium with core24 base won't start: desktop-launch not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2072395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
