I haven’t been able to connect my Nintendo Pro Controller and Nintendo Joy Cons to bluetooth for over a year, and this issue has persisted from my old laptop to my new one (both running similar environments). I am currently running Fedora 40 on my Dell XPS 15 Laptop, and I’ve spent yesterday trying fixes I’ve seen in reddit and stackexchange forums with no noticeable changes:
- Update all packages/software
- Disconnect all devices from bluetooth, clear cache, restart bluetooth, and reconnect devices
- Go to input.conf and change ClassicBondedOnly to “false”
- Install joycond, and restarting it if it’s not working
- Downgrading to an earlier version of bluez v5.64 (it won’t even start if I downgrade it)
- Restarting my laptop after each of the above things
I should note that my Pro Controller does work if I plug it directly into my laptop and disregard bluetooth, but that obviously isn’t applicable for my JoyCons. Bluetooth does seem to recognize my joycons, but it refuses to properly pair with them (even after setting up joycond) as they just continuously flash (meaning my laptop is unable to register button inputs from them).
Running systemctl status bluetooth gives me an output that I’ve pasted below. Note that the rejected connection is my controller.
Bluetooth Status Log
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Sun 2024-09-22 20:13:29 CDT; 23min ago
Docs: man:bluetoothd(8)
Main PID: 1132 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 38008)
Memory: 3.4M (peak: 6.4M)
CPU: 901ms
CGroup: /system.slice/bluetooth.service
└─1132 /usr/libexec/bluetooth/bluetoothd
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSource/aptx_ll_duple_1
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSource/aptx_ll_duple_0
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSource/faststream
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSource/faststream_duplex
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSink/opus_05
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSource/opus_05
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Sep 22 20:13:45 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: Endpoint registered: sender=:1.117 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Sep 22 20:14:10 2605-4A80-F001-91C0-0-0-6B9B-2F6E-dynamic.midco.net bluetoothd[1132]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device /org/bluez/hci0/dev_B8_78_26_58_7A_2F
I suspect this issue might be some sort of bug with an update for either Bluez or Bluetoothctl as I didn’t even need joycond a couple years ago to wirelessly connect my controller to my laptop. Though if this is a bug, i would expect it to have been patched by now.
If there are any files or additional logs you’d like to see, let me know. Though i should clarify that (as far as i know), I do not own any other Bluetooth devices, so my ability to test hardware on my end is unfortunately limited to my controllers. Thanks in advance for helping.