I've got very similar hardware, and can't reproduce this. It looks very much like a driver issue with the wireless/bluetooth coexistence code in iwlwifi.
Looks like your bluetooth device is this USB entry:
Bus 002 Device 003: ID 8086:0189 Intel Corp.
Now, what would be a good test would be if you could toggle the bluetooth connection in the same way you usually do as reported in this bug report: via the bluetooth UI, then attaching the output of 'rfkill list'. I expect to see there only 2 or 3 entries rather than 4.
I've got very similar hardware, and can't reproduce this. It looks very much like a driver issue with the wireless/bluetooth coexistence code in iwlwifi.
Looks like your bluetooth device is this USB entry:
Bus 002 Device 003: ID 8086:0189 Intel Corp.
Now, what would be a good test would be if you could toggle the bluetooth connection in the same way you usually do as reported in this bug report: via the bluetooth UI, then attaching the output of 'rfkill list'. I expect to see there only 2 or 3 entries rather than 4.