Comment 18 for bug 2004416

The full set of messages related to this bug seems to be:

Jan 31 22:26:18 t935 wireplumber[1791]: 0x56370f33ca08: error 24
Jan 31 22:26:18 t935 wireplumber[1791]: RFCOMM write error: Connection reset by peer
Jan 31 22:26:18 t935 acpid[876]: input device has been disconnected, fd 18
Jan 31 22:26:18 t935 bluetoothd[885]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Jan 31 22:26:18 t935 wireplumber[1791]: (bluez_output.04_5D_4B_29_06_26.1-24) running -> error (Received error event)
Jan 31 22:26:18 t935 dbus-daemon[888]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.80" (uid=1000 pid=1791 comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=885 comm="/usr/lib/bluetooth/bluetoothd" label="unconfined")
Jan 31 22:26:18 t935 pipewire[1789]: pw.node: (bluez_output.04_5D_4B_29_06_26.1-60) running -> error (Received error event)
Jan 31 22:26:18 t935 gsd-media-keys[2098]: Unable to get default sink

Although sometimes the first couple are missing. So it seems like a full Bluetooth stack issue always starting in bluetoothd (BlueZ). That's not to say it's definitely a software bug because it sounds like the headset might have disconnected to begin with.