After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 725865 - Unable to pair bluetooth keyboard after recent yum update
Unable to pair bluetooth keyboard after recent yum update
Status: RESOLVED OBSOLETE
Product: gnome-bluetooth
Classification: Core
Component: wizard
3.10.x
Other Linux
: Normal major
: ---
Assigned To: gnome-bluetooth-general-maint@gnome.bugs
gnome-bluetooth-general-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2014-03-07 00:24 UTC by Kirk Bridger
Modified: 2015-07-29 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kirk Bridger 2014-03-07 00:24:37 UTC
Filed in Fedora bug tracker too: https://bugzilla.redhat.com/show_bug.cgi?id=1072048

Description of problem:
After a recent kernel upgrade about 2 weeks 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 search 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.
Comment 1 garrett.mitchener 2014-06-20 15:14:15 UTC
I'm seeing this on Fedora 20 after switching over to kernel 3.14. A Microsoft bluetooth keyboard that used to work just fine no longer does. I removed the keyboard from the bluetooth settings and was unable to reconnect, apparently because the PIN can't be displayed: I see the same error message.

I used a command line process to connect to this keyboard, and it works, sort of: I successfully paired the keyboard using bluetoothctl. It connects okay, then a second later it disconnects, then it reconnects when I hit a key, then disconnects, and so on.
Comment 2 Kirk Bridger 2014-06-20 16:19:26 UTC
I was able to resolve this problem, as described above, by moving to the rhughes Gnome 3.12 repo.

However a kernel update in the last couple of days has borked it again - now the keyboard can be paired via the PIN, but once it disconnects due to hard-coded keyboard power saving practices, it doesn't reconnect properly.  After waking it up it connects, stays active and working for about 3 seconds, then disconnects.  This continues until I remove the device entirely and re-pair it.

This keyboard has a very aggressive power timeout (like 3 minutes), meaning if I'm not typing within a 3 minute span I have to re-pair the keyboard.

But Garrett, your specific problem, the one in this bug, is probably solved by Gnome 3.12.

I'll file a separate bug for this new behaviour.
Comment 3 Kirk Bridger 2014-06-20 16:29:36 UTC
New bug created: https://bugzilla.gnome.org/show_bug.cgi?id=731975
Comment 4 John 2014-10-21 14:59:38 UTC
Logitech bluetooth k810 keyboard doesn't pair 
It is detected correctly, but pairing fails.
Gnome-bluetooth just says 'connecting to keyboard... setting up keyboard failed'
Comment 5 Bastien Nocera 2015-07-29 12:35:47 UTC
Bug 740829 fixes pairing for some keyboards, bug 746033 fixes it for Apple keyboards. Both of those are already fixed in gnome-bluetooth 3.14.1 and 3.16.1.

Please make sure you use the latest versions of gnome-bluetooth and file separate bugs for each device that might still have problems.