When connecting my bluetooth keyboard I found a problem with blueman. When you click search it finds the bluetooth keyboard and when you double click on the bluetooth keyboad it says connecting but doesn't display the 6 digit number transmitted by the keyboard. You need this 6 digit number to type in on the bluetooth keyboard in order to connect. I tried the same thing on blueberry and when I double click on the keyboard and it displays this 6 digit number and I typed this into the bluetooth keyboard and was able to connect. Reproducible: Always
Could you try running blueman via "blueman-applet --loglevel debug"? There may be something useful in the logs. See: https://github.com/blueman-project/blueman/wiki/Troubleshooting#debugging-blueman
Created attachment 1961177 [details] blueman-applet --loglevel debug blueman-applet --loglevel debug listing
When you double click on the device (blue tooth keyboard) and small screen pops up (pairing request) asking for you to enter the code. I don't have the code, the code is supplied by the keyboard. This code by the keyboard needs to be displayed so that I can enter the code on the blue tooth keyboard. I have attached the debug listing you requested.
> AgentManager:20 on_register_failed: /org/bluez/obex/agent/blueman org.bluez.obex.Error.AlreadyExists Agent already exists Can you try that again, but running "pkill blueman-applet" or "killall blueman-applet" first (to kill the already-running instance)? Once you have a new instance of blueman-applet running in debug mode and spewing stuff to your terminal, try pairing with the keyboard.
Created attachment 1961437 [details] blueman-applet --loglevel debug Try 2 Attached is requested listing, try 2
Created attachment 1992757 [details] Blueman pairing request This is the pairing request issued by Blueman. It is asking me to enter the code. The problem is the code is supplied by the keyboard and is a random number.
Created attachment 1992758 [details] Blueberry pairing request. The is the blueberry pairing request. It supplies the code provided by the keyboard and when this code is typed in on the keyboard you are able to connect.
I have supplied two attachments. One from Blueman and one from Blueberry. On Blueman you are unable to connect because you need the code supplied by the keyboard which is a random number that keeps changing. It would be great if this could be fixed in F38 because Blueberry is unsupported and it is unknown if Blueberry will still work on F39. But at present I'm unable to connect my bluetooth keyboard using Blueman.
I would be willing to test a change to Blueman to fix the keyboard problem.
Interesting. I do not have a bluetooth keyboard, so I can't really test this. When connecting to a phone or another PC, the code is displayed fine for me. Could you try reporting this upstream? I'll be happy to backport any fix that may be developed for this.
I have two bluetooth keyboards made by different manufacturers that have a problem in Blueman. Could you give me some info on how I report this upstream? I did try to do a search about reporting upstream but didn't come up with anything useful.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.