I have followed the fix suggestion in bug #1589889. This has resulted in some progress in that I can now connect to the headphones, and once the headphones did register the laptop. But they disconnected straight away, and hasn't registered again since then.
I've tried the blueman manager as it tends to put out a bit more information than the standard bluetooth manager and i get the following:
Connection Failed: blueman.bluez.errors.DBusFailedError: Protocol not available
This device registers as several different components and when I specifically try to connect to the serial port I get the following message
Connection Failed: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/blueman/services/meta/SerialService.py", line 29, in connect
port_id = create_rfcomm_device(Adapter(props['Adapter']).get_properties()['Address'], props['Address'], 1)
File "_blueman.pyx", line 218, in _blueman.create_rfcomm_device (_blueman.c:2127)
Exception: Can't connect RFCOMM socket
I have followed the fix suggestion in bug #1589889. This has resulted in some progress in that I can now connect to the headphones, and once the headphones did register the laptop. But they disconnected straight away, and hasn't registered again since then.
I've tried the blueman manager as it tends to put out a bit more information than the standard bluetooth manager and i get the following:
Connection Failed: blueman. bluez.errors. DBusFailedError : Protocol not available
This device registers as several different components and when I specifically try to connect to the serial port I get the following message
Connection Failed: Traceback (most recent call last): python3/ dist-packages/ blueman/ services/ meta/SerialServ ice.py" , line 29, in connect rfcomm_ device( Adapter( props[' Adapter' ]).get_ properties( )['Address' ], props['Address'], 1) create_ rfcomm_ device (_blueman.c:2127)
File "/usr/lib/
port_id = create_
File "_blueman.pyx", line 218, in _blueman.
Exception: Can't connect RFCOMM socket