Note that this is for the chromium snap and it is the snapd package that
provides the apparmor policy for the chromium snap.
Also, the bluez accesses should not be what is preventing the chromium
snap from starting-- these are harmless denials. I've adjusted the title
of the to reflect this. Assigning to Olivier since he is taking care of
the chromium snap. Olivier, please adjust this bug as needed.
** Package changed: apparmor (Ubuntu) => snapd (Ubuntu)
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Summary changed:
- apparmor prevents Chromium (snap) to run the 2nd time
+ Chromium (snap) fails to run the 2nd time
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767880
Title:
Chromium (snap) fails to run the 2nd time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767880/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
