Branch: refs/heads/master Home: https://github.com/bluez/bluez Commit: d206ab94a79e0c6c96265fca1155caea18405a73 https://github.com/bluez/bluez/commit/d206ab94a79e0c6c96265fca1155caea18405a73 Author: Archie Pusaka <apusaka@xxxxxxxxxxxx> Date: 2024-01-03 (Wed, 03 Jan 2024) Changed paths: M monitor/packet.c Log Message: ----------- monitor: add Qualcomm and Mediatek MSFT opcodes Qualcomm and Mediatek has 0xfd70 and 0xfd30 for their MSFT opcodes, respectively. Signed-off-by: Archie Pusaka <apusaka@xxxxxxxxxxxx> Reviewed-by: Hsin-chen Chuang <chharry@xxxxxxxxxx> Commit: 60d60166e4bfae8555fb671e5a99952586cc6b56 https://github.com/bluez/bluez/commit/60d60166e4bfae8555fb671e5a99952586cc6b56 Author: Vinit Mehta <vinit.mehta@xxxxxxx> Date: 2024-01-03 (Wed, 03 Jan 2024) Changed paths: M client/agent.c M client/mgmt.c Log Message: ----------- mgmt: Fix crash after pair command After pair command, if the user doesn't provide any input on bluetoothctl CLI interface after receiving the prompt(yes/no) below crash is observed: dbus[782]: arguments to dbus_message_get_no_reply() were incorrect, assertion "message != NULL" failed in file /usr/src/debug/dbus/1.14.10-r0/dbus/dbus-message.c line 3250. This is normally a bug in some application using the D-Bus library. /usr/lib/libc.so.6(+0x27534) [0xffffa1b67534] /usr/lib/libc.so.6(__libc_start_main+0x9c) [0xffffa1b6760c] bluetoothctl(+0x188f0) [0xaaaac9c088f0] Aborted (core dumped) Compare: https://github.com/bluez/bluez/compare/7ad5669402c9...60d60166e4bf
