045e:009c [H87I-PLUS] Microsoft Keyboard Elite for Bluetooth dead keys problem

[Maeda]

In Precise with 4.60 version of bluez I can pair my keyboard and mouse perfectly, but not with the 4.98 that is in Precise by default.

=== The problem is that dead keys of my keyboard (I mean -L or R- CTRL, ALT, SUPER, -L or R- SHIFT, ALT-GR) doesn't work with my current motherboard (whether application I opened, console included). It does work correctly with other motherboards. The new motherboard is an 1150 Haswell one from Asus.

What I can say is :
1/ When booting, my BIOS recognize perfectly the dead keys of my keyboard, meaning that the bluetooth dongle or the motherboard is not directly concerned.
2/ When doing a second installation of Ubuntu, same problem.
3/ When trying the option 'keyboard layout' (whatever layout I choose), I don't see those dead keys flashing, meaning the system doesn't react at all when pressing them.
4/ By chance, I found another keyboard (same model, same brand), same problem, meaning the keyboard is not concerned (it works on the older motherboard, then it was poor chance that the keyboard broked just before reinstalling).
5/ Tried the setxkbmap command (with sudo or without), nothing's better
6/ Tried the xmodmap command, I see the 0x codes for Left SHIFT, all dead keys are there (see attachment)
7/ Normal keyboard (no wireless) works perfectly
8/ Put the dongle on an other usb slot doesn't change anything
9/ Command xev doesn't makes changes when pressing dead keys.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-37-generic 3.5.0-37.58~precise1
ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lolo 2272 F.... pulseaudio
 /dev/snd/controlC0: lolo 2272 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'MID'/'HDA Intel MID at 0xf0434000 irq 45'
   Mixer name : 'Intel Haswell HDMI'
   Components : 'HDA:80862807,80860101,00100000'
   Controls : 6
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'PCH'/'HDA Intel PCH at 0xf0430000 irq 46'
   Mixer name : 'Realtek ALC887-VD'
   Components : 'HDA:10ec0887,10438576,00100302'
   Controls : 41
   Simple ctrls : 20
Date: Fri Aug 16 16:34:35 2013
HibernationDevice: RESUME=UUID=942aa693-ca21-4f2a-966c-97b0fa9ea5ae
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: ASUS All Series
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-37-generic root=UUID=9509f53e-1de4-4f9c-90dd-6c1ef7ded3a9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-37-generic N/A
 linux-backports-modules-3.5.0-37-generic N/A
 linux-firmware 1.79.6
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0306
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87I-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0306:bd04/15/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87I-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
---
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CasperVersion: 1.336ubuntu1
DistroRelease: Ubuntu 13.10
InterestingModules: btusb bnep rfcomm bluetooth
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: ASUS All Series
MarkForUpload: True
Package: bluez 4.101-0ubuntu8b1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Tags: saucy
Uname: Linux 3.11.0-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/01/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0507
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87I-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/01/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87I-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:0D:3A:A7:BB:D3 ACL MTU: 377:10 SCO MTU: 16:0
  DOWN
  RX bytes:358 acl:0 sco:0 events:12 errors:0
  TX bytes:39 acl:0 sco:0 commands:12 errors:0
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc5-saucy/

[Maeda (maeda1-deactivatedaccount)]

Tested with following live CDs :

- 10.04.4 Lucid : works perfect out of the box
- 10.10 Maverick : works perfect out of the box
- 11.04 Natty : pair OK but keyboard never activate itself : there is a B with a lock on it
- 11.10 Oneiric : pair OK but keyboard always on OFF and I don't have the possibility to turn it OFF (gray) -endly, same as 11.04
- 13.10 Saucy (daily) : On Bluetooth's windows : I can turn the ON button, but doesn't change anything (the "+" button still in gray). When returning, still OFF.

Strange behavior : sometimes, there is a windows asking me to grant access to some code like 1001:4545:4... before I can use the Bluetooth manager to pair devices. And when granting access like that, it seems to pair and then never activate devices.

[penalvch (penalvch)]

Maeda, as per http://www.asus.com/Motherboards/H87IPLUS/#support_Download_8 an update is available for your BIOS (0507). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Thank you for your understanding.

[Maeda (maeda1-deactivatedaccount)]

Hi !

Done :
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
0507
07/01/2013

No changes :

- With bluez 4.98 from Precise : same problem : pairing is OK, but never keyboard activate (mouse OK).
- With bluez 4.60 (from Lucid) installed on Precise : pairing is OK, activate and working but not the dead keys.

[penalvch (penalvch)]

Maeda, we have two running bugs here:
1) changing bluez version caues mis-pairing.
2) When you keyboard is properly paired, some keys are dead.

Given changing bluez version from that which is released brings you in unsupported territory, we would want to get the bluez problem fixed first before we would focus on the dead keys.

Sending to bluez (Ubuntu). Please send back if found to be a kernel problem.

[Maeda (maeda1-deactivatedaccount)]

OK thanks, I understand your opinion.

Let's see with bluez's guys, then :-)

[Maeda (maeda1-deactivatedaccount)]

Well... No bluez's guy working on it ?

[Maeda (maeda1-deactivatedaccount)]

Here is an entry of /var/log/syslog when attempting to pair the keyboard :

Discovery session 0x7f429baa9730 with :1.79 activated
bluetoothd[1143]: Stopping discovery
bluetoothd[1143]: Agent /org/bluez/agent/wizard replied with an error: org.freedesktop.DBus.Error.AccessDenied, Rejected send message, 1 matched rules; type="method_call", sender=":1.2" (uid=0 pid=1143 comm="/usr/sbin/bluetoothd ") interface="org.bluez.Agent" member="RequestPinCode" error name="(unset)" requested_reply="0" destination=":1.79" (uid=1000 pid=3871 comm="bluetooth-wizard ")

This could be a help for bluez's guys.

[penalvch (penalvch)]

Maeda, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect 1213123

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

apport information

[Maeda (maeda1-deactivatedaccount)]

Done, see files just before this message.

It's simple : Bluetooth won't activate itself, then impossible to pair anything... That's bad news.
Do you see something wrong on files ?

Thanks.

[Maeda (maeda1-deactivatedaccount)]

Hi !
I made some other tests that are relevant :

With another brand/model keyboard (Logitech k400r) :

Precise : dongle doesn't work
Saucy daily (20130925) : bluetooth won't activate

In both cases, lsusb show the dongle, same behavior as my usb dongle/keyboard.
--
With Precise and bluez 4.60 (my workaround) and this keyboard, all's working, including dead keys, like my previous motherboard. Same behavior, but without the problem of dead keys, which isn't a bug that you should be aware of, as this is a (bad ?) workaround.
--
In conclusion, there definitely IS a problem between Asus haskell's motherboards and bluez (and Ubuntu ?).
As my motherboard is a pretty new one from Asus (and as the h87-pro have the same bug), I think bluez (or ubuntu) needs to patch something, as some other guys will bought them !

Just tell me which log to see, or how to make those more verbose. I'm ready to test all you want.
Maybe the title should be change so that the name/brand of the keyboard will not be written.

Thanks.

[Maeda (maeda1-deactivatedaccount)]

Here is what happened in syslog when attempting to pair the keyboard with Precise (not a live cd) and the default bluez package :
==
Oct 13 17:47:27 bluetoothd[1094]: Discovery session 0x7ff7c4e06470 with :1.79 activated
Oct 13 17:47:40 bluetoothd[1094]: Stopping discovery
Oct 13 17:48:10 bluetoothd[1094]: 00:0D:3A:A6:9D:4F: error updating services: Software caused connection abort (103)
==
I see the keyboard in bluetooth's devices, and pairing say 'Yes' and the switch to activate the keyboard is grayed.

Any ideas ?

[Maeda (maeda1-deactivatedaccount)]

Just done a test with Saucy live cd and some bluez commands.

Nothing from bluez package is working !
==
ubuntu@ubuntu:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 003 Device 010: ID 045e:009c Microsoft Corp. Wireless Transceiver for Bluetooth 2.0
Bus 003 Device 009: ID 045e:3500 Microsoft Corp.
Bus 003 Device 002: ID 060b:2401 Solid Year
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
==
ubuntu@ubuntu:~$ bluez-simple-agent
Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 117, in <module>
    path = manager.DefaultAdapter()
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter
==
ubuntu@ubuntu:~$ sudo bluez-simple-agent
Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 117, in <module>
    path = manager.DefaultAdapter()
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter
==
ubuntu@ubuntu:~$ bluez-test-adapter
Traceback (most recent call last):
  File "/usr/bin/bluez-test-adapter", line 25, in <module>
    adapter_path = manager.DefaultAdapter()
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter
==
What's wrong with bluetooth in Saucy ?

[Maeda (maeda1-deactivatedaccount)]

I want to upgrade to Trusty, but if I don't have keyboard or mouse, it will not be easy. As this problem occurs with another brand/model/usb adapter, I don't have any solution...

Dongle detected, but Bluetooth don't activate itself... Just downloaded Trusty 14.04.1 and same problem. I can turn Bluetooth ON, but it stay like that, and when returning, Bluetooth is OFF.

Any ideas on logs to check ?

[penalvch (penalvch)]

Maeda, to see if this is resolved in a later release, could you please test for this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Launchpad Janitor (janitor)]

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]