baybal

``` static void avctp_control_confirm(struct avctp *session, GIOChannel *chan, struct btd_device *dev) { const bdaddr_t *src; const bdaddr_t *dst; if (session->control != NULL) { error("Control: Refusing unexpected connect"); g_io_channel_shutdown(chan, TRUE, NULL);...

Pipewire

@Vudentz still the same issue with A2DP volume on linux 5.14, pipewire 0.3.34, bluez 5.61. HFP volume sync works fine. Still same `avctp.c:avctp_control_confirm() Control: Refusing unexpected connect`

Update. I found out that this doesn't happen with my bluetooth stereo. Only the BT handsfree. Maintainers please provide suggestions how to debug this. Can it be that it's mSBC...

BTsnoop log [dump.btsnoop.log](https://github.com/bluez/bluez/files/7403910/dump.btsnoop.log)

``` -event21 DEVICE_ADDED GS (AVRCP) seat0 default group13 cap:k -event5 KEYBOARD_KEY +33.252s *** (-1) pressed event5 KEYBOARD_KEY +33.416s *** (-1) released event5 KEYBOARD_KEY +33.434s *** (-1) released -event21 KEYBOARD_KEY +36.214s...

> In my case (ASUS Vivobook S), without keyd running, keyd monitor reports the following: > > 1. Press and then release Copilot key: > > ``` > AT Translated...

The bitlk-12d663c1-e3ff-44ff-9c88-c0d4c2b20624 entry is clearly shown to have DISC-MAX of 0, which means discard is not enabled. If I use cryptsetup manually `sudo cryptsetup --allow-discards open --type=bitlk --allow-discards /dev/nvme0n1p3 windows`,...

> workaround: > > ``` > cryptsetup --allow-discards --persistent refresh luks > ``` Unfortunately, not an option for bitlocker