Comment 13 for bug 2006517

I refreshed the pc-kernel on Ubuntu Core.

22/candidate: 5.15.0-66.73.1 2023-02-14 (1224)

Output from uname:
uname -a
Linux BRMD-0009.I2SMicro.com 5.15.0-66-generic #73-Ubuntu SMP Fri Feb 3
14:23:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Logging from journalctl.

Feb 22 21:08:41 ubuntu bluetoothd[1758]: Bluetooth daemon 5.64
Feb 22 21:08:41 ubuntu systemd[1]: Started Service for snap application
bluez.bluez.
Feb 22 21:08:41 ubuntu bluetoothd[1758]: Starting SDP server
Feb 22 21:08:41 ubuntu dbus-daemon[1520]: [system] Activating via
systemd: service name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.7' (uid=0 pid=17>
Feb 22 21:08:41 ubuntu audit[1758]: AVC apparmor="DENIED"
operation="create" profile="snap.bluez.bluez" pid=1758
comm="bluetoothd" family="alg" sock_type="seqpacket" protocol=0
requested_mask="cr>
Feb 22 21:08:41 ubuntu bluetoothd[1758]: Bluetooth management interface
1.21 initialized
Feb 22 21:08:41 ubuntu bluetoothd[1758]: Battery Provider Manager
created
Feb 22 21:08:41 ubuntu bluetoothd[1758]:
src/advertising.c:read_adv_features_callback() Failed to read
advertising features: Not Supported (0x0c)
Feb 22 21:08:41 ubuntu bluetoothd[1758]: Adv Monitor Manager created
with supported features:0x00000001, enabled features:0x00000001, max
number of supported monitors:32, max number of supported >

The software that logs the above error is just the Canonical bluez
snap.
On an ubuntu core22 system: snap install --channel=22/stable bluez

bluez 22/stable: 5.64-2 2022-05-03 (331)

So a vanilla Ubuntu Core22 install -- then install the bluez 22/stable
snap. The bluetoothd system daemon reports the error.

Wendell

On Sat, 2023-02-18 at 01:49 +0000, AceLan Kao wrote:
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you recognize the sender
> and know the content is safe.
>
>
> From the dmesg logs, the kernel you use on desktop(5.15.0-56) and on
> core(5.15.0-58) are not the same, but I've checked the kernel logs,
> there is no update on bt driver part between the 2 kernel versions.
> It'd
> be good if you can help me to update the kernel to make sure the
> kernel
> versions are identical and check the issue again.(I feel the result
> won't change)
>
> The snap package works on desktop, but not on core, this doesn't look
> like a kernel/driver issue. Could you provide more info about which
> function call failed? or provide a simple program that we could try
> on
> our side?
>
> BTW, the difference between the dmesg logs is that rfcomm is loaded
> on
> the desktop, but not on the core system, could you also try to load
> it
> on the core system to see if it makes any difference, thanks.
>
> --