Bluetooth Devices will not pair on Pop_OS! 20.04 LTS using KDE Plasma 5.18.5

ALazyDope · 07-26-2020, 06:14 PM

I attempted to connect to Sony WH-XB900N Bluetooth Headphones, and in both Plasma's bluetooth settings and Blueman, I was unable to connect, in both cases the device would appear in the selection, but then would get stuck connecting until it timed out and device shutoff. Sometimes it would appear to pair on the computer's end, but the headphones would still be in pairing mode, and audio would not be sent, still using the headphones I have wired in. Bluetooth seemed to stop working after I changed my hostname, and I was curious if this could have anything to do with it.

ALazyDope · 07-26-2020, 11:27 PM

Bluetooth has worked before, but it seemed that after changing my hostname, that it stopped working, and nothing was able to connect after that

mochsner · 07-30-2020, 10:34 AM

Running into a similar issue here on Pop_OS 20.04 with natively supported Darter Pro, using new Bose 700 headphones.

@ALazyDope, I'm wondering if this could be something related to LE bluetooth? I'll letchya know if I find anything

ALazyDope · 07-30-2020, 07:16 PM

It worked for a while but just suddenly stopped after I booted up one day

mochsner · 07-30-2020, 08:02 PM

I was actually able to resolve this earlier today by following Victor's answer here to force Bluetooth to use regular Bluetooth rather than LE (Low energy). Feel free to try it out & let us know if that works for you!

Since I have no reason to use LE, I'm just keeping it disabled long-term.

ALazyDope · 07-31-2020, 02:07 PM

Even after applying the fixes provided, there is no change, Bluetooth still fails to connect

cordx · 07-31-2020, 02:10 PM

have you tried using bluetoothctl?

ALazyDope · 07-31-2020, 02:16 PM

Code:

~$ bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 48:F1:7F:8E:9E:A9 Discovering: yes
[bluetooth]# devices
[bluetooth]# devices
[NEW] Device 38:18:4C:03:54:A3 WH-XB900N
[bluetooth]# devices
Device 38:18:4C:03:54:A3 WH-XB900N
[CHG] Device 38:18:4C:03:54:A3 RSSI: -41
[CHG] Device 38:18:4C:03:54:A3 RSSI: -49
[bluetooth]# pair 38:18:4C:03:54:A3
Attempting to pair with 38:18:4C:03:54:A3
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# pair 38:18:4C:03:54:A3
Attempting to pair with 38:18:4C:03:54:A3
Failed to pair: org.bluez.Error.AlreadyExists
[CHG] Device 38:18:4C:03:54:A3 RSSI: -41
[bluetooth]# connect 38:18:4C:03:54:A3
[bluetooth]# connect 38:18:4C:03:54:A3
Attempting to connect to 38:18:4C:03:54:A3
Failed to connect: org.bluez.Error.Failed
[bluetooth]#

cordx · 07-31-2020, 02:27 PM

these are the two pages i used to help get mine working:
https://computingforgeeks.com/connec...inux-terminal/
https://wiki.archlinux.org/index.php/Bluetooth

starting by checking the service status and making sure that nothing is blocked with rfkill is probably a good idea. i didn't ever quite understand what the point of registering additional agents (KeyboardOnly) was, but since both mentioned it i did so. after that using the show command (in bluetoothctl) will let you know if the controller is ready and then info [dev] will let you know the status of the device. help will list the other options you have.

ALazyDope · 07-31-2020, 02:41 PM

rfkill is unblocked

Code:

~$ rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0     blocked unblocked

show gives me this which seems to say the controller is available

Code:

~$ bluetoothctl
Agent registered
[bluetooth]# show
Controller 48:F1:7F:8E:9E:A9 (public)
        Name: Byron-GPC
        Alias: Byron-GPC
        Class: 0x001c0104
        Powered: yes
        Discoverable: yes
        DiscoverableTimeout: 0x00000000
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        Modalias: usb:v1D6Bp0246d0535
        Discovering: no

and then this after running scan on

Code:

[bluetooth]# show
Controller 48:F1:7F:8E:9E:A9 (public)
        Name: Byron-GPC
        Alias: Byron-GPC
        Class: 0x001c0104
        Powered: yes
        Discoverable: yes
        DiscoverableTimeout: 0x00000000
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        Modalias: usb:v1D6Bp0246d0535
        Discovering: yes

and finally info on the headset gives

Code:

[bluetooth]# info 38:18:4C:03:54:A3
Device 38:18:4C:03:54:A3 (public)
        Name: WH-XB900N
        Alias: WH-XB900N
        Class: 0x00240404
        Icon: audio-card
        Paired: no
        Trusted: no
        Blocked: no
        Connected: no
        LegacyPairing: no
        Modalias: usb:v054Cp0CDCd0452

cordx · 07-31-2020, 02:53 PM

did you run all of these agent KeyboardOnly, default-agent and power on before the above? if so, can you try trusting first to see if that might help with the other two steps?

ALazyDope · 07-31-2020, 04:32 PM

Code:

Device 38:18:4C:03:54:A3 (public)
        Name: WH-XB900N
        Alias: WH-XB900N
        Class: 0x00240404
        Icon: audio-card
        Paired: no
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: yes
        Modalias: usb:v054Cp0CDCd0452
        TxPower: 4

Did all the agent stuff and nothing seemed to change about my controller, and when I trusted the device, it seemed to attempt to connect, but it never completed, giving Failed to connect: org.bluez.Error.InProgress, and audio would still not play through the device

cordx · 07-31-2020, 04:57 PM

my situation was fairly similar in that i could get paired and trusted, but not connected (two out of three, but still not working). what helped get the third yes was running journalctl -f in a separate terminal while i ran the whole process with bluetoothctl. journalctl -f will let you see system logs as they are written. hopefully in those messages is an error that is more descriptive and helpful than the one from bluetoothctl

you can try running journalctl -f before you attempt pairing again. that may show an error. if it does not, i would sever the connection entirely (untrust and disconnect - you can probably do those through blueman) and then run journalctl -f as you go through the entire process in case that might yield a more helpful error.

in my case that process helped find a page that said some bluetooth pulseaudio modules weren't loading and that was all i needed to fix to get up and running.

ALazyDope · 07-31-2020, 05:46 PM

After a long while of leaving it connecting I got this error

Code:

Failed to connect: org.freedesktop.DBus.Error.NoReply

I also can't find the device in paired-devices despite when trying to pair it returns

Code:

Failed to pair: org.bluez.Error.AlreadyExists

Code:

Jul 31 18:44:56 Byron-GPC kernel: debugfs: Directory '256' with parent 'hci0' already present!
Jul 31 18:44:56 Byron-GPC kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0/hci0:256'
Jul 31 18:44:56 Byron-GPC kernel: CPU: 13 PID: 23672 Comm: kworker/u65:1 Tainted: P           OE     5.4.0-7634-generic #38~1595345317~20.04~a8480ad-Ubuntu
Jul 31 18:44:56 Byron-GPC kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Master SLI/ac, BIOS P3.30 06/17/2019
Jul 31 18:44:56 Byron-GPC kernel: Workqueue: hci0 hci_rx_work [bluetooth]
Jul 31 18:44:56 Byron-GPC kernel: Call Trace:
Jul 31 18:44:56 Byron-GPC kernel:  dump_stack+0x6d/0x9a
Jul 31 18:44:56 Byron-GPC kernel:  sysfs_warn_dup.cold+0x17/0x35
Jul 31 18:44:56 Byron-GPC kernel:  sysfs_create_dir_ns+0xb8/0xd0
Jul 31 18:44:56 Byron-GPC kernel:  kobject_add_internal+0xbd/0x2b0
Jul 31 18:44:56 Byron-GPC kernel:  kobject_add+0x7e/0xb0
Jul 31 18:44:56 Byron-GPC kernel:  ? kfree_const+0x17/0x30
Jul 31 18:44:56 Byron-GPC kernel:  ? kmemdup_nul+0x11/0x60
Jul 31 18:44:56 Byron-GPC kernel:  device_add+0x132/0x6b0
Jul 31 18:44:56 Byron-GPC kernel:  hci_conn_add_sysfs+0x49/0xc0 [bluetooth]
Jul 31 18:44:56 Byron-GPC kernel:  hci_conn_complete_evt.isra.0+0xcf/0x420 [bluetooth]
Jul 31 18:44:56 Byron-GPC kernel:  ? __switch_to_asm+0x34/0x70
Jul 31 18:44:56 Byron-GPC kernel:  hci_event_packet+0x1594/0x2a90 [bluetooth]
Jul 31 18:44:56 Byron-GPC kernel:  ? __switch_to_asm+0x40/0x70
Jul 31 18:44:56 Byron-GPC kernel:  ? __switch_to_asm+0x34/0x70
Jul 31 18:44:56 Byron-GPC kernel:  ? __switch_to_asm+0x40/0x70
Jul 31 18:44:56 Byron-GPC kernel:  ? __switch_to_asm+0x34/0x70
Jul 31 18:44:56 Byron-GPC kernel:  ? __switch_to_asm+0x40/0x70
Jul 31 18:44:56 Byron-GPC kernel:  ? __switch_to_asm+0x34/0x70
Jul 31 18:44:56 Byron-GPC kernel:  hci_rx_work+0x19b/0x360 [bluetooth]
Jul 31 18:44:56 Byron-GPC kernel:  ? __schedule+0x2eb/0x740
Jul 31 18:44:56 Byron-GPC kernel:  process_one_work+0x1eb/0x3b0
Jul 31 18:44:56 Byron-GPC kernel:  worker_thread+0x4d/0x400
Jul 31 18:44:56 Byron-GPC kernel:  kthread+0x104/0x140
Jul 31 18:44:56 Byron-GPC kernel:  ? process_one_work+0x3b0/0x3b0
Jul 31 18:44:56 Byron-GPC kernel:  ? kthread_park+0x90/0x90
Jul 31 18:44:56 Byron-GPC kernel:  ret_from_fork+0x22/0x40
Jul 31 18:44:56 Byron-GPC kernel: kobject_add_internal failed for hci0:256 with -EEXIST, don't try to register things with the same name in the same directory.
Jul 31 18:44:56 Byron-GPC kernel: Bluetooth: hci0: failed to register connection device

After reading through this I might have an idea as to what the issue is, but I'd have no idea where to start

cordx · 08-01-2020, 01:50 AM

first off, thank you for the use of code tags to make things easier to read. thanks as well for not posting hours worth of logs to try and sift through.

it seems the ones you have posted are right on the money and a more technical way of saying "Failed to pair: org.bluez.Error.AlreadyExists" or "i can't pair with a device that is already paired" even though it is clearly designated as not paired in bluetoothctl.

the way i ran my issue down was to search for the line that seemed most relevant. to me that line is: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0/hci0:256'

is it possible you lost power to either device while they were paired? i don't think that helps solve the issue, but might explain why your system still believes they are connected. it might also help avoid the same thing happening again.

those things being said, the oldest computer solve i know is turning it off then back on again. in this case before even running the previously suggested search, i would recommend using bluetoothctl to untrust and disconnect the device. there is also an option to "remove" the device, but i have never used it so i stop short of suggesting you try that. i don't have my bluetooth running just now to check, but if you can look at blueman after this to see if you can remove the headphones from there that might help. after those steps, i would even go so far as to "power off" the controller with bluetoothctl and then do the same if you have a hardware switch or keyboard combination that also does so. i would check rfkill to see if everything was blocked. then i would reboot your computer and power your headphones off.

the idea here is that your computer seems to have some kind of configuration set that links to your headphones at /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0/hci0:256 (where hci0 is your bluetooth adapter located on the usb bus and 256 possibly somehow identifies your headphones) and hopefully severing the connection entirely will remove that configuration.

then start your computer and bluetooth back up with the headphones turned off, make sure the agents are registered and the controller is powered on before powering the headphones on and trying to connect again. since you have seen how journalctl -f works, it probably wouldn't be a bad idea to run it again in case it has any new messages that might be helpful.