Bluetooth Devices will not pair on Pop_OS! 20.04 LTS using KDE Plasma 5.18.5
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
it sounds like you are still trying to fix what isn't working instead of re-installing. if so, did you ever run any searches for the error messages shown by systemctl to see if there were any possible leads there?
this link popped up in a different thread today and i figured i would pass it along just in case: https://wiki.archlinux.org/index.php/Bluetooth_headset
since it had parts that mentioned "If you are getting a connection error org.bluez.Error.Failed", "If pairing fails, you can try", "Pairing works, but connecting does not" among others along with some different solution options/troubleshooting steps.
And of course it worked for all of and hour and then stopped again, with new errors this time when trying to restart the adapter
Code:
Bluetooth: hci0: urb 00000000bab45ccb failed to resubmit (113)
bluetoothd[5165]: Failed to set mode: Failed (0x03)
Restarting the computer and pairing the device again seems to have fixed the issue, but it seems that this may be more software issue than hardware, and I'm not sure where to start
I am also getting the error
Code:
usb 1-5: device descriptor read/64, error -110
usb usb1-port5: unable to enumerate USB device
However I am unsure if it is related
The headset works for a while, but eventually I keep getting this error is journalctl
Code:
bluetoothd[3096]: Start: Connection timed out (110)
pulseaudio[3315]: Transport Acquire() failed for transport /org/bluez/hci0/dev_38_18_4C_03_54_A3/sep1/fd0 (Input/output error)
bluetoothd[3096]: avdtp_start failed
pulseaudio[3315]: Transport Acquire() failed for transport /org/bluez/hci0/dev_38_18_4C_03_54_A3/sep1/fd0 (Operation Not Authorized)
i would make sure to check systemctl status bluetooth in case you haven't already. after that the only method i really know is to start running web searches for the error messages you are encountering and hope there is a post out there somewhere that has found a solution to one that works for your system.
Quote:
Originally Posted by ALazyDope
I am also getting the error
Code:
usb 1-5: device descriptor read/64, error -110
usb usb1-port5: unable to enumerate USB device
However I am unsure if it is related
i noticed when i was working with mine that bluetooth was recognized as a usb device so this may be related. i would consider that probable especially if the message is being displayed when the other problems with bluetooth are occurring.
Quote:
Originally Posted by ALazyDope
The headset works for a while, but eventually I keep getting this error is journalctl
Code:
bluetoothd[3096]: Start: Connection timed out (110)
pulseaudio[3315]: Transport Acquire() failed for transport /org/bluez/hci0/dev_38_18_4C_03_54_A3/sep1/fd0 (Input/output error)
bluetoothd[3096]: avdtp_start failed
pulseaudio[3315]: Transport Acquire() failed for transport /org/bluez/hci0/dev_38_18_4C_03_54_A3/sep1/fd0 (Operation Not Authorized)
you had mentioned trying to find a usb bluetooth adapter before. one of the unfortunate possibilities is that your present bluetooth adapter may be broken. you said that you feel like this is more of a software as opposed to hardware issue, but from my experience the only way to know that would be to have a different piece of known good hardware to test that with.
Thank you, yes, I haven't gotten a moment to try to find a compatible adapter, so I haven't gotten around to testing it yet, but since there was a brief period after rebooting my pc that the bluetooth works perfectly fine, I was unsure if it was something deeper
~$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 09:25:05 EDT; 4h 11min ago
Docs: man:bluetoothd(8)
Main PID: 3096 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 19021)
Memory: 3.9M
CGroup: /system.slice/bluetooth.service
└─3096 /usr/lib/bluetooth/bluetoothd
Aug 21 09:43:44 Byron-GPC bluetoothd[3096]: connect error: Operation already in progress (114)
Aug 21 09:43:47 Byron-GPC bluetoothd[3096]: connect error: Operation already in progress (114)
Aug 21 09:44:18 Byron-GPC bluetoothd[3096]: /org/bluez/hci0/dev_38_18_4C_03_54_A3/sep1/fd0: fd(48) ready
Aug 21 09:50:11 Byron-GPC bluetoothd[3096]: Start: Connection timed out (110)
Aug 21 09:50:11 Byron-GPC bluetoothd[3096]: avdtp_start failed
Aug 21 09:50:13 Byron-GPC bluetoothd[3096]: Abort: Connection timed out (110)
Aug 21 09:52:05 Byron-GPC bluetoothd[3096]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Aug 21 09:52:05 Byron-GPC bluetoothd[3096]: No matching connection for device
Aug 21 09:53:14 Byron-GPC bluetoothd[3096]: Failed to set mode: Failed (0x03)
Aug 21 09:54:10 Byron-GPC bluetoothd[3096]: Failed to set mode: Failed (0x03)
Thank you, yes, I haven't gotten a moment to try to find a compatible adapter, so I haven't gotten around to testing it yet, but since there was a brief period after rebooting my pc that the bluetooth works perfectly fine, I was unsure if it was something deeper
for your sake i wish there were a way to know for sure. you have certainly put plenty of time and effort into trying to find out. at some point if a software solution isn't forthcoming, it just seems like trying a hardware one would be worth a shot.
you had mentioned having other bluetooth devices before (an xbox controller maybe?). are these devices having similar issues or is anything working as expected?
So I've just recently moved, and as such had to completely disconnect my power to my PC. After powering it back up again, bluetooth works normally. Bluetooth then stopped working after my connected xbox wireless controller went into automatic sleep mode. After this all bluetooth devices stopped connecting, but when I shut off the power supply, turn it back on, and reboot the computer, bluetooth works normally again. I think the way that the xbox controller goes into sleep is messing with my bluetooth controller, and causing issues in the cache, but after a full power loss, the cache is maybe cleared?
those definitely sound like interesting developments. it has been a while since i have looked at this thread and i'm not sure you ever mentioned the system specs. is this a tower pc with connected monitor (or all-in-one) you are talking about? more specifically, not a laptop?
since the triggering event seems to be related to your xbox controller like you mentioned, one way try and get a better look at the why might be to fire up journalctl -f again. shut the system down, make sure everything is working well after you turn it on, run journalctl -f before connecting the xbox controller and see if anything helpful pops up.
Quote:
Originally Posted by ALazyDope
So I've just recently moved, and as such had to completely disconnect my power to my PC. After powering it back up again, bluetooth works normally.
as we both learned (i think... i know i did) when looking at this, the bluetooth adapter is on the usb bus. i have read about issues with some computers not providing enough power to usb (mostly external though) devices if too many are attached to the same controller.
Quote:
Originally Posted by ALazyDope
Bluetooth then stopped working after my connected xbox wireless controller went into automatic sleep mode. After this all bluetooth devices stopped connecting, but when I shut off the power supply, turn it back on, and reboot the computer, bluetooth works normally again.
power supplies can also die over time. i realize that just adds to the list of possible causes, but might be worth keeping an eye on.
Quote:
Originally Posted by ALazyDope
I think the way that the xbox controller goes into sleep is messing with my bluetooth controller, and causing issues in the cache, but after a full power loss, the cache is maybe cleared?
again, it's been a while since i read through all of this. i seem to remember the bluetooth controller getting stuck searching and not able to connect. that might possibly be related to losing contact when the xbox controller goes to sleep. maybe journalctl will have something to say about that?
i am not sure what cache you are referring to. ostensibly any connections or configs the bluetooth controller creates should be cleared (and, hence, any cache) when it is shut off which would be easier than powering down the whole system.
i am listening about the cache though. feel free to explain what you were thinking.
Well I am unsure how devices are managed on linux, since there seems to be some sort of filesystem associated with usb and pci devices, and since the issue appears in journalctl as an inability to write to these directories, I was just taking a bit of a guess.
i don't understand the intricacies of all of that either. i have read something along the lines of "everything in linux is considered a file" and believe that is in regards to mounted devices as well.
i remember some output you got about not being able two write to hci0 which seemed to be a descriptor of where the bluetooth device (headset or xbox controller for you, speaker for me) was supposed to be. i was able to find that file in both terminal and file manager when it was connected and paired. as soon as i disconnected, it was gone. so, at least in theory, severing connections or making the bluetooth controllable unpairable (i forget the exact terminology) in bluetoothctl or maybe even btmod should remove that file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
