[Feature-Request] Dual-booting between Windows & Ubuntu 22.04 Flavor cause Bluetooth Speaker/Pairing Keys to Reset
Closed this issue · 2 comments
FEATURE REQUEST:
Easier way to share one Bluetooth device between multiple operating systems in one machine.
blueman: 2.2.4
BlueZ: 5.64
Distribution: Pop!_OS 22.04 LTS
Desktop environment: GNOME 42.9/X11
- I have consulted the Troubleshooting page and done my best effort to follow.
I dual boot between a Windows 11 machine and Linux OS machine. Both operating systems share one Bluetooth speaker. Fir security reasons, the Pairing Keys for either Operating System is different and thus the Bluetooth speaker must be constantly paired and connected after each reboot of one machine.
I have found a workaround, on the internet which requires extracting the Pairing Key from the Windows Registry or from /var/lib/bluetooth and then inserting that key into the other operating system. This is the process that I have to do if for some reason the pairing key value changes due to an error or something unexpected.
The way I do this is manual, requiring the terminal, in any of the above Operating Systems, i.e. Windows/Linux/MacOS.
If possible, can a easier method be implemented in blueman gui such as a textbox that takes the paring key e.g. a3 b3 23 d2 85 97 09 7a b2 c6 b3 3f 70 74 68 ea and have the process be quicker, less time consuming?
Thank you,
:)
Note:
I also notice that upon pairing in Linux, the system volume does not match the volume of the speaker, thus the overall volume is really low. I have to hit the volume button on the actual speaker so that the system's volume indicator and volume adjusts to the bluetooth speaker's actual volume. Don't know if this is a bug or just something I am doing wrong.
Not sure blueman is the place for this but if I understand you correctly you are looking for the LinkKey key stored in /var/lib/bluetooth/adaptermac/devicemac/info?
I'm personally very hesitant to add something like this as it requires us to expose it over dbus which makes it available for anything that runs as your user. It's not accessible by normal users for a reason.
[General]
Name=HD 4.40BT
Class=0x240404
SupportedTechnologies=BR/EDR;
Trusted=true
Blocked=false
Services=00001108-0000-1000-8000-00805f9b34fb;0000110b-0000-1000-8000-00805f9b34fb;0000110c-0000-1000-8000-00805f9b34fb;0000110e-0000-1000-8000-00805f9b34fb;0000111e-0000-1000-8000-00805f9b34fb;00001200-0000-1000-8000-00805f9b34fb;
[DeviceID]
Source=1
Vendor=2578
Product=1
Version=0
[LinkKey]
Key=4377D47B4D19C8F0EDF9C6E8365BE86D
Type=4
PINLength=0ps: Don't worry about me exposing the key, I re-pair this device very often :-).
Hello,
Yes, I understand your security concerns. Its just a bit annoying the steps one has to go through to make sure the same LinkKey stays consistent across reboots of two different operating systems. In my case, it's my personal Windows and Linux home laptop and nobody else uses it. Which there existed an affordable external Bluetooth speaker that would store the LinkKey of individual operating systems or a similar feature on the OS side. It's really frustrating.
Thank you for the reply,
MB