Wrong bluetooth pairing PIN reported for Logitech K810

[Knut Remi Løvli]

I've been unable to pair my Logitech K810. I figured out that the new device setup wizard reports the wrong PIN. I used bluez-hcidump before trying to pair from the setup wizard. The setup wizard PIN differs from the one reported by bluez-hcidump. The PIN reported by bluez-hcidump was correct.

Here's the command I used:
sudo hcidump -at | grep pass

Minimal steps to reproduce:
1. Run "Configure new device..." from the bluetooth applet menu
2. Install bluez-hcidump.
3. Put the keyboard in pairing mode (button underneath) and pick profile (F1, F2 or F3)
4. Run 'sudo hcidump -at | grep pass' from the terminal
5. Select the keyboard from the list of devices in the setup wizard and continue
6. Observe how the PIN differs from the one in hcidump.

Bluetooth module (probably not relevant):
(Intel?) Bluetooth 4.0, 3.0+HS, 2.1+EDR
Not entirely sure as the specs for my Gigabyte GA-F2A88XN-WIFI motherboard were unclear.

1) Ubuntu release:
Ubuntu 14.04 LTS

2) Package version:
3.8.2.1-0ubuntu4

3) What I expected to happen:
I expected to see the same bluetooth pairing PIN as in bluez-hcidump.

4) What happened instead:
Some PIN whose origin I do not know was reported.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-bluetooth 3.8.2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jun 20 19:19:48 2014
InstallationDate: Installed on 2014-06-19 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marcos Alano (mhalano)]

The solution is easy: Just grab the same code from hcidump. The implementation is hard, because ssems need an exception for this model. Any news about that? Someone posts this bug on Gnome Bugzilla?