You are not logged in.
Hi folks. I've been using Arch for years but am still a N00b because shit always breaks for no reason and I can't get it fixed without having someone on the forum tell me some secret trick.
Often this is because I didn't read the wiki carefully enough but in this case, there is basically nothing on the wiki-- it's all pretty basic and seems like it should just work.
And in fact it DID just work the last tme I tried it-- about in April-- I installed bluez-5.44-1 and bluez-utils-5.44-1 and paired with my phone and transferred a picture and all was well.
Fast forward to now, a couple of pacman -Syu later, a couple of restarts later, and now bluetooth is just a giant pile of shit.
The module is loaded:
[root@ember bluetooth]# lsmod | grep btusb
btusb 40960 0
btrtl 16384 1 btusb
btbcm 16384 1 btusb
btintel 16384 1 btusb
bluetooth 487424 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb
usbcore 208896 7 uvcvideo,usbhid,ehci_hcd,xhci_pci,btusb,xhci_hcd,ehci_pci
Systemctl status bluetooth shows normal performance:
[root@ember bluetooth]# systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2017-06-16 21:34:00 PDT; 7min ago
Docs: man:bluetoothd(8)
Main PID: 1935 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─1935 /usr/lib/bluetooth/bluetoothd
journalctl doesn't show anything.
It's not rfkill:
[root@ember bluetooth]# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
It just never connects.
My phone can't see my computer, my computer can't see my phone. When I run bluetoothctl and tell it to scan, the scan never completes.
[root@ember bluetooth]# bluetoothctl
[NEW] Controller C8:FF:28:5B:31:BC ember [default]
[NEW] Device 5A:5A:5A:A6:31:1C S3020S
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[bluetooth]#scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]#
Isn't it supposed to tell me that Discovering: YES, and then show me nearby devices? it never does.
When I use gnome-bluetooth or blueman it just doesn't give me any love: no errors, no failure notices, but no connection either. In gnome-bluetooth case, the spinning circle just spins.
I recently upgraded to bluez-5.45-1 and so I tried downgrading, but that was not effective either.
I don't know what to do- I've read the wiki page up and down. What should I try next?
Thanks in advance.
Last edited by johnnynyquist (2017-06-17 05:10:53)
Offline
Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code
Offline
Thanks for the tip. Backtick notation didn't work.
Anyway, it occurs to me that one thing that did change was the phone... which is a Galaxy S6 and apparently the recent upgrade caused bluetooth issues with headset pairings.. so why not laptops? anyway, maybe that is the explanation.
Offline
Try runnig agent on before scan.
Offline