AppArmor for bluez: insufficient to create profile

[Ian Smith]

After a recent upgrade, I could no longer connect my headphones. After examining syslog, I found repeated errors like the following:

Aug 2 21:05:55 xxx kernel: [ 10.872693] audit: type=1400 audit(1659488755.939:36): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1284 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"

Aug 2 20:46:23 xxx kernel: [ 11.867683] audit: type=1400 audit(1659487583.931:111): apparmor="DENIED" operation="connect" profile="snap.bluez.obex" name="/run/dbus/system_bus_socket" pid=1372 comm="obexd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

Aug 2 21:07:06 xxx kernel: [ 81.271562] audit: type=1107 audit(1659488826.602:56): pid=1180 uid=102 auid=4294967295 ses=4294967295 subj=? msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=2665 label="snap.brave.brave" peer_pid=1177 peer_label="unconfined"

Disabling AppArmor temporarily while I re-paired all my devices fixed the issue. Re-enabling afterward didn't break anything, but resulted in the last error above.

[Tony Espy (awe)]

This bug list is meant to track issues with snaps maintained in this project (meant for usage on Ubuntu Core only). If you have issues with bluetooth on Ubuntu Desktop, please use the Ubuntu bluez bug list: https://bugs.launchpad.net/ubuntu/+source/bluez