On Tue, Oct 20, 2026 at 11:03 AM Vincent Lefevre <[email protected]> wrote:
>
> Some of the obtained errors for the webex meeting actually seem
> to be harmless, as shown by microphone tests I've done with
>
>   https://mozilla.github.io/webrtc-landing/gum_test.html
>
> (internal microphone, with audio back to my headset, so the same
> settings as yesterday). The journalctl logs show:
>
> Oct 20 10:45:19 qaa bluetoothd[1292]: profiles/audio/a2dp.c:load_remote_sep() 
> Unable to load LastUsed: rseid 1 not found
> Oct 20 10:45:20 qaa kernel: Bluetooth: hci0: SCO packet for unknown 
> connection handle 513
> Oct 20 10:45:20 qaa kernel: input: WH-1000XM3 (AVRCP) as 
> /devices/virtual/input/input42
> Oct 20 10:45:20 qaa systemd-logind[1310]: Watching system buttons on 
> /dev/input/event24 (WH-1000XM3 (AVRCP))
> Oct 20 10:45:30 qaa wireplumber[2492]: pw.node: 
> (bluez_input.38_18_4C_4B_AC_93.0-148) running -> error (Received error event)
> Oct 20 10:45:30 qaa wireplumber[2492]: pw.node: 
> (bluez_output.38_18_4C_4B_AC_93.1-146) running -> error (Received error event)
> Oct 20 10:45:30 qaa wireplumber[2492]: spa.bluez5: Failure in Bluetooth audio 
> transport /org/bluez/hci0/dev_38_18_4C_4B_AC_93/fd64
> Oct 20 10:45:30 qaa pipewire[2488]: pw.node: 
> (bluez_input.38_18_4C_4B_AC_93.0-148) running -> error (Received error event)
> Oct 20 10:45:30 qaa pipewire[2488]: pw.node: 
> (bluez_output.38_18_4C_4B_AC_93.1-146) running -> error (Received error event)
> Oct 20 10:45:30 qaa bluetoothd[1292]: 
> /org/bluez/hci0/dev_38_18_4C_4B_AC_93/sep1/fd1: fd(34) ready
>
> but here, everything is working correctly.
>
> Such errors are annoying because this means that it is impossible
> to know what could be the cause of issues like I had yesterday.
>
> Now, it is less clear that this is a bug in bluez rather than in
> pipewire (or wireplumber). It seems that the AI answer was focusing
> on the first error (which is what one should usually do), i.e. the
> "load_remote_sep() Unable to load LastUsed: rseid 1 not found"
> line above from bluez, but it actually seems to be harmless.

There is a lot of AI-generated text to read and this email seems to
contradict the other emails. Could you summarize whether there is
still anything that needs to be fixed in bluez?

I also get a bit concerned about AI bugs because sometimes, the AI
gives people suggestions on things to change in their system and it's
unclear whether there are any AI-suggested changes that could cause
additional bugs. Is this bug reproducible from a new Debian Testing
(or Unstable) install?

Thank you,
Jeremy Bícha

Reply via email to