i installed cachy os recently, and had bluetooth working before on a different linux install with the same pc. i have an xbox one controller, bluetooth is on, and it detects the device, but it fails to connect after a bit, giving the message “The Setup of Xbox Wireless Controller has failed”. i tried looking up the issue, but there wasn’t much that came up.
edit: i forgot to mention, when i try to connect it with a wire, it connects, but inputs don’t work. i tried it with an offbrand switch pro controller that was also working before, with a cord i know worked with that controller before, and it also connected without inputs.
Is your system up-to-date? There was a kernel regression recently wrt. bluetooth. Latest kernel should have the bluetooth fixes tho, so update first if you haven’t already.
i updated and restarted, and it’s doing the same things
Can you give me the exact details of your bluetooth chip and/or dongle that you’re using?
Hardware: Intel Wireless-AC 3168 Bluetooth
Driver: btusb
edit: lmk if you need more info
Hello,
Im having the exact same problem as NeoThe1.
Luckily for me the the spare wired controller works, my xbox controller worked with previous versions of cachyos.
in my last install i went back to a previous kernel and that seemed to fix the situation which shows where the problem lies.
Best Wishes.
1 Like
Im having the exact same problem as NeoThe1.
Luckily for me the the spare wired controller works, my xbox controller worked with previous versions of cachyos.
in my last install i went back to a previous kernel and that seemed to fix the situation which shows where the problem lies.
Best Wishes.
Do you know which kernel version first started to show these regressions?
Yes the one used in the current version of Cachyos.
That’s 6.11.6, 6.11.5 doesn’t have this issue? You can download previous versions of the kernel from https://archive.cachyos.org
Hello all,
I’m having a bluetooth problem which appears to be quite interesting.
I’m on a fresh CachyOS install (less than 24h) and using an ASUS USB-BT500 dongle.
I was trying to connect to my LG SL8Y soundbar, but although the device is recognizable, it won’t connect (trying to connect for 10-15 seconds before failing).
I did the most obvious troubleshooting by trying to connect to my phone (hoping to eliminate some audio/pipewire/something issue) but to no avail.
Now comes the most interesting part: when I tried to establish connection FROM my phone to PC it just worked like charm…
Can’t try the same method for soundbar, cause it has no option to initiate connection, it can only listen for incoming attempts.
Any ideas what in the world can cause such one-sided issue?
New install today, seems this is still an issue? Getting “The setup of XXXX has failed” with every BT device I try to pair.
What do you do after you download 6.11.5? Also, where is 6.11.5 - I looked a few places in your link and found 6.11.4 here: CachyOS - Repo
Edit: Seems I actually have 6.12.8-2-cachyos (64-bit), but am getting these errors and can’t get any BT devices to connect. They fail to pair with that message above, but then show up in the list of paired devices anyway - but if I try to click ‘Connect’ there it says it failed to receive a response from the device.
Can you confirm that the bluetooth service is enabled? systemctl status bluetooth. If so, please provide some logs from dmesg if it exists.
❯ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Thu 2025-01-09 11:29:11 CST; 11min ago
Invocation: 04edf0c5edc24f568002e0f17d6b9e09
Docs: man:bluetoothd(8)
Main PID: 713 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 28376)
Memory: 2.4M (peak: 2.9M)
CPU: 47ms
CGroup: /system.slice/bluetooth.service
└─713 /usr/lib/bluetooth/bluetoothd
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/op>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/op>
Jan 09 11:29:24 SSBGFH3PX2 bluetoothd[713]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/>
hit post limit so switched to pastebin, this reply no longer relevant/needed - see link above instead
So it seems that you are hitting the same issue as this person. Unfortunately there hasn’t been any updates since 2023. I’m not sure how to proceed this either. I believe the kernel needs to accomodate for this dongle.
Sorry, just getting back to this (it’s my work PC and I’m hybrid).
I’ve found that it is only the Surface BT Keyboard and the MS BT Ergo Mouse that won’t connect - My Xbox Wireless Controller (elite 2) and my headphones (Sony WH-1000XM2) have connected without any issues, so it doesn’t seem like the dongle itself is having problems - unless I’m missing something. The dongle is a TP-Link UB400.
The devices show up like they are paired after they fail too, which is kinda strange - they won’t connect though (the headphones do, they are just turned off right now):
Okay a bit more info, I was able to get the devices to pair using bluetoothctl, so it seems like it is an issue with the KDE bluetooth gui?
Example:
bluetoothctl
scan on
### wait for device to be listed with MAC
scan off
pair XX:XX:XX:XX:XX:XX ### pair with device MACI’m not sure. There aren’t really any bluedevil specific logs AFAICS but it could very well be.