045e:009c [H87-PRO] 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.

=== 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.

For me it's clearly a Ubuntu's system bug, with my motherboard (Asus H87-PRO socket 1150).

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: syl 4375 F...m rhythmbox
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PAD'/'RME Digi96/8 PAD at 0xf4000000, irq 19'
   Mixer name : ''
   Components : ''
   Controls : 10
   Simple ctrls : 6
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf3080000 irq 17'
   Mixer name : 'Nvidia GPU 14 HDMI/DP'
   Components : 'HDA:10de0014,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
Card2.Amixer.info:
 Card hw:2 'NVidia_1'/'HDA NVidia at 0xe3080000 irq 16'
   Mixer name : 'Nvidia GPU 0a HDMI/DP'
   Components : 'HDA:10de000a,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
DistroRelease: Ubuntu 12.04
MachineType: ASUS All Series
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-36-generic root=UUID=d2f8f163-a1ee-4332-a910-d593309cd2a6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-36-generic N/A
 linux-backports-modules-3.5.0-36-generic N/A
 linux-firmware 1.79.4
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.5.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio bluetooth boinc cdrom dip lp lpadmin netdev plugdev sambashare scanner sudo video
dmi.bios.date: 04/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87-PRO
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.:bvr0501:bd04/08/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1203565/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1203565

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[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)]

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

[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-rc2-saucy/

[Maeda (maeda1-deactivatedaccount)]

Tested with :

linux-headers-3.11.0-031100rc2_3.11.0-031100rc2.201307211535_all.deb
linux-headers-3.11.0-031100rc2-generic_3.11.0-031100rc2.201307211535_amd64.deb
linux-image-3.11.0-031100rc2-generic_3.11.0-031100rc2.201307211535_amd64.deb

Impossible to test the keyboard, as the bluetooth dongle device isn't recognize with this kernel.

[penalvch (penalvch)]

Maeda, as per http://www.asus.com/Motherboards/H87PRO/#support_Download_8 an update is available for your BIOS (0613). 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

Thank you for your understanding.

[Maeda (maeda1-deactivatedaccount)]

Hi !

I don't see why a bios update will change something, as the keyboard's dead keys works perfectly under the first BIOS I had (it's a graphics BIOS and mouses and keyboards works on it).
Nevertheless, I did it and it doesn't change anything : no dead keys are working under Ubuntu with the latest BIOS

Here is the output of the command :

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
0613
06/28/2013

[penalvch (penalvch)]

Maeda, thank you for updating your BIOS. Could you please test for this in Saucy via http://cdimage.ubuntu.com/daily-live/current/ and advise on the results?

[Maeda (maeda1-deactivatedaccount)]

Hi !

I've just tested with Saucy live cd and the dongle is recognized on lsusb, but doesn't appear on the bluetooth software, which cannot activate the bluetooth of course.
Then the keyboard doesn't work at all (neither the mouse) with Saucy.

I made another interesting test : I put my dongle and keyboard on another computer, which have the same version of Ubuntu like me and an Asus H87I-Plus which is socket 1150 Haswell, too.

With bluez v4.98 by default on Ubuntu Precise 12.04, it's the same way as my computer (keyboard paired but impossible to activate).
Then I tried to do the same way : uninstalling the 4.98 and installing the 4.60 of bluez.

Result : keyboard paired, and same problem : dead keys doesn't work neither.

I'll try to test another live-cd of another linux distribution which have same kernel version and if possible same bluez version (4.98 or 4.60).
An idea of which distribution to choose ?

[penalvch (penalvch)]

Maeda, thank you for testing Saucy. Sounds like we have at least two different bugs here:
1) Bluez may have a regression going from 4.60.
2) When the keyboard is correctly detected via Bluez 4.60, one has dead keys. Let us focus on this. However, I would like to include the Bluez folks as a technical gut check on this problem.

Hence, did this keyboard not have dead keys in a release prior to Precise with the H87-PRO motherboard?

[Maeda (maeda1-deactivatedaccount)]

Thank for quick answering.

I think you're right as the problem may be on bluez package.
I have this keyboard since the first LTS release (6.06 Dapper Drake). I jumped each time on LTSs.
Unfortunately, I didn't have this motherboard when having Lucid Lynx (10.04), but it was bluez 4.60 indeed.

I can download Lucid live-cd and try to see if the dead keys are out too, the result could be an important information to know what package is causing trouble.

I'll try that and will inform you as soon as I made the test.

[Maeda (maeda1-deactivatedaccount)]

I could not test with my motherboard directly because the Lucid live cd doesn't want to boot. Then I tried with my other computer which have a H87I-PLUS motherboard (and have the bug too, see my previous tests), and it works immediatly like a charm !

Then : all's working with the Lucid 10.04.4 live cd.

[penalvch (penalvch)]

Maeda, let this report only focus on the motherboard you originally reported against (H87-PRO). Hence, with it, could you please test Natty via http://old-releases.ubuntu.com/releases/natty/ ?

[Maeda (maeda1-deactivatedaccount)]

OK.

Just tested with Natty, and the devices paired, but impossible to use them. On bluetooth windows, devices never get in bold (indicating that they are working).

[penalvch (penalvch)]

Maeda, could you please test Oneiric via http://old-releases.ubuntu.com/releases/oneiric/ ?

[Maeda (maeda1-deactivatedaccount)]

Tested with Oneiric, and the live CD just don't boot, leaving me with a 'udev [...] timeout modprobe kill [...]' nerver ending messages. Same with 'nomodeset' option in the live CD's boot.

As said before, I can test with another computer that have this bug too (H87I-PLUS motherboard) and maybe the live CD will boot.

[penalvch (penalvch)]

Maeda, it would be helpful if we started a separate report to track this problem with your other computer, as it appears to have less problems in regression testing. Could you please do this via executing at a terminal:
ubuntu-bug linux

[Maeda (maeda1-deactivatedaccount)]

OK, if I do understand well, I have to open a bug report using 'ubuntu-bug linux' command on a terminal, but on the other computer with H87I-PLUS motherboard ? Then, I should test all other distributions as advised, and write results on the other bug just opened, am I right ?

[penalvch (penalvch)]

Maeda:
>"I have to open a bug report using 'ubuntu-bug linux' command on a terminal, but on the other computer with H87I-PLUS motherboard ?"

Yes please.

[Maeda (maeda1-deactivatedaccount)]

OK done :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213123

I'll do the Live Cds tests.

[Maeda (maeda1-deactivatedaccount)]

Do we need to mark this bug duplicate or something like that to work only on the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213123 ?

[penalvch (penalvch)]

Maeda, no.

[Maeda (maeda1-deactivatedaccount)]

The main problem is for sure in the adapter BCM2035 and bluez.

See here : https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/453885

Downgrading to bluez 4.60 is the only solution... Solution that won't work with the LTS Trusty. Then, I can't do upgrade to this LTS.

I'm available to test commands and give you logs.

[penalvch (penalvch)]

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

[Maeda (maeda1-deactivatedaccount)]

Hi !

Thanks for answer.
Just downloaded daily-live current and same problem.

lsusb is OK, showing the adapter.
Activating bluetooth using bluetooth-agent stay on ON but say bluetooth is disabled. Returning in bluetooth-agent show Bluetooth OFF.

Trying do to a hciconfig hci0 up return "operation not permitted (1)". With sudo privileges it's "operation not supported (95)".

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Launchpad Janitor (janitor)]

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