Created attachment 168007 [details] Bluetoothctl Log SUMMARY This controller: https://web.archive.org/web/20231030230144/https://www.amazon.com/Controller-Joysticks-Compatible-Vibration-PlayStation-4/dp/B0CCTXQ6P5?th=1 Fails to connect properly via bluetooth under Plasma 6. For some reason, however, it does connect properly on the Steam Deck. (Back on my Plasma 5 desktop, before I update to Plasma 6, it used to randomly decide whether or not it wanted to; it was inconsistent back then). STEPS TO REPRODUCE 1. Enable bluetooth 2. Run "bluedevil-wizard" via the terminal (unpair the device from the systemsettings menu if it was previously paired - this is included in my log) 3. Attempt to pair the device 4. Get this error via the terminal from the wizard: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." OBSERVED RESULT PS4 bluetooth controller fails to pair/connect properly but may still register itself in the bluetooth paired devices menu in systemsettings. EXPECTED RESULT PS4 controller to pair and connect without issue. SOFTWARE/OS VERSIONS Linux: Gentoo (OpenRC & LLVM-based) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION Log attached with this report.
Forgot to list my kernel: 6.7.1-tkg-pds-gentoo-llvm-zen2 (https://github.com/frogging-family/linux-tkg)
Have you tried pairing it via upstream bluetoothctl command? I see you monitored it, but did you try to pair directly using it? This highly likely to be an upstream BlueZ issue, as Plasma is just a bunch of glue and plumbing on top. https://github.com/bluez/bluez/issues
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I thought I did at the time, but I'll try again soon when I have a moment. I meant to respond sooner but I was stranded away from home for a while and I forgot to get back to this once I got back.
Created attachment 171999 [details] new_BRHE-PS4-Controller_bluetoothctl.log It does seem that it's specifically this controller for me; a while ago I was forced to buy a new controller because of some button and trigger issues (got an official Sony PS4 controller for comparison), and reconnecting (using the controller's "guide" button) after pairing with the official one works as intended but testing the same process with the BRHE one fails to reconnect after disconnecting and using the guide button. What's odd about this to me is that the BRHE controller doesn't fail to reconnect on the Steam Deck (I tested there as well), so this seems isolated to my system somehow. (bluetoothctl version: 5.76) I take it that this belongs upstream...?
Also forgot to mention my current kernel: 6.8.9-tkg-eevdf-gentoo-llvm-zen2 (https://github.com/frogging-family/linux-tkg)
Ah, forget what I said about the BRHE one being able to reconnect on the Steam Deck; I'm tired (01:48 in the morning) and I'm not thinking completely straight at the moment.
Created attachment 172024 [details] Screenshot of Failed GUI Pair of Official Sony PS4 Controller Huh, but when I try to pair the official controller via the Plasma bluetooth wizard, it fails... This is really odd.
Can you try pairing your device through command line with bluetoothctl? This will let us know if there's an underlying system problem. Instructions to connect using bluetoothctl: 1. `sudo systemctl restart bluetooth` 2. `bluetoothctl` 3. `scan on` 4. Write down the MAC for the device: `[bluetooth]# [NEW] Device 88:C9:XXXXXX Device-name 5. `connect <MAC>` 6. `quit` Please reply with your results. Thanks.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.