Description of problem: After a recent kernel upgrade about 1 week ago my bluetooth keyboard stopped pairing. When I try to manually repair after deleting the device I see failure everytime, with this error in /var/log/messages: Mar 3 10:58:40 hostname bluetoothd[523]: Agent replied with an error: org.freedesktop.DBus.Error.UnknownMethod, No such method 'DisplayPinCode' Steps to reproduce: 1. Open Bluetooth panel 2. Start searching for device to pair 3. Start keyboard serach function 4. Select device from list of possible devices 5. Wait until it times out waiting for a PIN code box to show up. I'm able to pair the keyboard fine with my Nexus 4. The problem seems to be that Gnome doesn't know how to prompt for a PIN code anymore. Version-Release number of selected component: gnome-abrt-0.3.5 Additional info: reporter: libreport-2.1.12 kernel: 3.13.5-200.fc20.x86_64 type: libreport
I continue to test this with each kernel update from Fedora. Still no luck at all. Same symptoms.
I upgraded this morning to Gnome 3.12 via the rhughes COPR, and was able to pair properly after restarting. The PIN dialogue was displayed and worked properly.
Same problem here with a Logitech DiNovo keyboard. kernel-3.14.4-200.fc20.x86_64 bluez-5.18-1.fc20.x86_64 gnome-shell-3.10.4-2.fc20.x86_64 messages includes: May 27 23:15:01 pootle bluetoothd: ** Message: vendor 0x0 product: 0x0 May 27 23:15:01 pootle bluetoothd[819]: Agent replied with an error: org.freedesktop.DBus.Error.UnknownMethod, No such method 'DisplayPinCode' Installing bluedevil and pairing using bluedevil-wizard provides a workaround.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.