Press caps lock on Apple wireless keyboard and the keyboard stops working

[WeiKeTing]

I am typing using the Apple wireless keyboard,When I press 'caps lock',the keyboard don't work any more!
So I go use keyboard on the Macbook.The key case have change,but the light on the key do not light on.
I have to off the bluetooth then make it on again.Then reconnect the wireless keyboard.
Yes,It work again.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: bluez 4.101-0ubuntu13
ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
Uname: Linux 3.16.0-3-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 13 17:12:23 2014
InstallationDate: Installed on 2014-03-08 (126 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: Apple Inc. MacBookPro9,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-4B7AC7E43945597E
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-4B7AC7E43945597E
dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
dmi.product.name: MacBookPro9,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 7C:D1:C3:79:A7:25 ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:119665 acl:5720 sco:0 events:2443 errors:0
  TX bytes:13420 acl:640 sco:0 commands:718 errors:0

[Launchpad Janitor (janitor)]

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

[Lando Nachtmann (lanna)]

This problems seems to affect other BT keyboards as well:
After hitting CapsLock, I have to do a re-connect of the Bluetooth keyboard. In my case a Fujitsu LX360 keyboard at a CSR bluetooth dongle (USB ID 0a12:0001).

[Tim O'Neil (interval1066)]

I can confirm this is an issue with three bluetooth keyboards (Perix, Neptor, & some other one) I've used on my Bluez stack; installed both the distro's default 4.101-0 stack (Mint 17), and the latest 5.23 release. Some kind of d-bus/kernel thing?

[Sascha Jurthe (sascha-jurthe)]

Same problem occurs with Microsoft Wedge BT Keyboard.

[Cláudio Fernandes (squeral)]

Same issue with Apple Keyboard...

[MP (trelirodia)]

Same issue with Microsoft Sculpt Mobile using Kubuntu 14.10 (64-bit)

[Marc (lefthy)]

Same issue here with another Wireless Apple Keyboard with bluez version 5.35 on Gentoo (64-bit). There are no logs written whatsoever. Keyboard just disconnects.

[Tommaso (tommaso-rigon)]

Same issue with Apple Keyboard!

[Juan Villa (gianpamx)]

It's been more than a year but is there any news on this? Same problem with:

Microsoft Sculpt Mobile Keyboard

The only line that I got from dmesg after turning the keyboard off and on again is:
unknown main item tag 0x0

Also, the bluetooth keyboard stops responding when pressing caps lock in the Bluetooth Keyboard or on a usb keyboard

[Vladimir Hulagov (vhulagov)]

Same issue with Gembird KB-316BT on Ubuntu 15.04.

Error reproduces on fresh compiled kernel 4.4.0-rc8+ from git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
and 4.5.0-rc1+ from Torvalds repository.
And bluez ver. 5.37.

In dmesg after keyboard was connected:
[121633.384618] calling hidp_init+0x0/0x20 [hidp] @ 16917
[121633.384628] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[121633.384638] Bluetooth: HIDP socket layer initialized
[121633.384648] initcall hidp_init+0x0/0x20 [hidp] returned 0 after 14 usecs
[121633.386807] hid-generic 0005:04E8:7021.001C: unknown main item tag 0x0
[121633.387265] input: Bluetooth v3.0 keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:768/0005:04E8:7021.001C/input/input40
[121633.388196] hid-generic 0005:04E8:7021.001C: input,hidraw4: BLUETOOTH HID v0.01 Keyboard [Bluetooth v3.0 keyboard] on 7c:7a:91:eb:67:f6

strace for bluetoothd stuck on:
10:28:39.270670 read(3, "\3\0\0\0\0\0\0\0", 16) = 8
10:28:39.275259 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
10:28:39.275588 read(8, "\21\0\0\0\10\0\220_\25&,\334\0\5", 512) = 14
10:28:39.275915 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
10:28:39.276167 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
10:28:39.276386 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
10:28:39.276603 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
10:28:39.276866 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=16, events=POLLIN}, {fd=18, events=POLLIN}, {fd=21, events=0}, {fd=20, events=POLLIN}, {fd=19, events=POLLIN}, {fd=23, events=0}, {fd=17, events=POLLIN}, {fd=9, events=POLLIN}, {fd=24, events=POLLIN}, {fd=7, events=POLLIN}, {fd=25, events=0}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}, {fd=26, events=0}, {fd=26, events=POLLOUT}, {fd=8, events=POLLIN}, {fd=22, events=POLLIN}], 22, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
10:28:39.277599 read(3, "\5\0\0\0\0\0\0\0", 16) = 8
10:28:39.281864 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=16, events=POLLIN}, {fd=18, events=POLLIN}, {fd=21, events=0}, {fd=20, events=POLLIN}, {fd=19, events=POLLIN}, {fd=23, events=0}, {fd=17, events=POLLIN}, {fd=9, events=POLLIN}, {fd=24, events=POLLIN}, {fd=7, events=POLLIN}, {fd=25, events=0}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}, {fd=26, events=0}, {fd=26, events=POLLOUT}, {fd=8, events=POLLIN}, {fd=22, events=POLLIN}], 22, 4294967295

When keyboard connected and Caps Lock was pressed, but if i turn off the keyboard strace shows fall of POLLIN/POLLOUT events in infinite cycle...

debugfs shows events with lag from 3 to 20 sec:
$ cat /sys/kernel/debug/hid/0005:04E8:7021.0026/events
report (size 8) (numbered) = 03 6a dc 2c 26 15 5f 90
GenericDeviceControls.BatteryStrength = 106
 00
Keyboard.00e0 = 0
Keyboard.00e1 = 0
Keyboard.00e2 = 0
Keyboard.00e3 = 0
Keyboard.00e4 = 0
Keyboard.00e5 = 0
Keyboard.00e6 = 0
Keyboard.00e7 = 0
Keyboard.0017 = 0

but wireshark continue recieving characters without any lag from bluetooth (bnep0) after issue occur, so i suggest that problem not in btintel/btusb kernel modules subsystem, but in...

[Jesper Broge Jørgensen (fnugk)]

I can confirm that this is still an issue in 17.10 with an apple keyboard

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Waleed Abdulla (waleedka)]

Same issue on Ubuntu 18.04 with Apple bluetooth keyboard. It only started happening recently, though. I've been using the same computer and the same keyboard for a few months without problems. But recently I started noticing that the keyboard occasionally goes into crazy mode where it either responds very slowly (I hit a key and it prints after 30 seconds), or it keeps printing a random key non-stop. The switch to crazy mode seems to happen when I hit CAPS Lock or Left Option+Shift (which is mapped to switch to international language).

[Ced (cedric-headroom)]

I had the same problem.
By pressing shift or caplock the MagicKeyboard wouldn't work anymore.

It turns out that the problem comes from the fact that I use the keyboard on both ubuntu and windows (dual boot).

When I connect the keyboard on ubuntu, it no longer works on windows because the keyboard and ubuntu share a sync key that windows does not know.
When I associate the keyboard on windows, it still works on ubuntu (when it shouldn't) until I press caplocks.
In fact, I think the bug is that the keyboard works a bit under ubuntu while the key is not good, if it returned an error we would find the problem right away.

To solve the problem, I reassociated the keyboard with windows and then I copied the connection key and I copied it in the bluetooth configuration of ubuntu.
Since my two OS share the same connection key for the keyboard, I don't have any more problems between the two OS and Capslock works well.

I followed this tutorial : https://desktopi18n.wordpress.com/2018/02/02/bluetooth-mouse-in-dual-boot-of-windows-10-and-linux/

Translated with www.DeepL.com/Translator (free version)