Bug 1467192 - Bluetooth keyboard: Repeated keystrokes
Bluetooth keyboard: Repeated keystrokes
Status: NEW
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
25
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Don Zickus
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-03 03:00 EDT by vasilis
Modified: 2017-07-04 05:35 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description vasilis 2017-07-03 03:00:17 EDT
Since FC19 I am using a MAC Bluetooth keyboard with my Linux with no problem.
Starting from the upgrade to FC20, and even clean installation of FC25 the Bluetooth keyboard randomly started repeating characters. It happens a couple of times per day, and it lasts for a a few minutes, rendering the keyboard unusable. During that period, the keyboard seems to be stuck on characters with a result liiiiiiiiiiikeeeeeeeeeeeeeee thiiiiiiiiiiiiiiisssssssssss.
I've tried different USB Bluetooth dongles with no success. Recently I've bought a Logitech K810 keyboard and exactly the same problem.

Various things I've tested:
1. Initially I though it might be EM interference, so I changed the position of the receiver, my GSM phone etc, with no success.

2. I've tried to monitor the communication with btmon during all day to check when it happens if there is something abnormal in the communication 

Here is dump of btmon during the problem
Result on terminal:        //////IIIIIIIInNPPPPPPPPP
btmon output:
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83183.709610
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 00 00 38 00 00 00 00 00                    ....8.....                          /
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83184.092029
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 00 00 00 00 00 00 00 00                    ..........                          none
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83184.204611
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 02 00 00 00 00 00 00 00                    ..........                          L_Shift
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83184.205813
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 02 00 0c 00 00 00 00 00                    ..........                          L_Shift i
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83184.633393
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 02 00 00 00 00 00 00 00                    ..........                          L_Shift
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83184.722031
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 00 00 00 00 00 00 00 00                    ..........                          none
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83184.834473
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 00 00 11 00 00 00 00 00                    ..........                          n
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83184.947012
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 02 00 11 00 00 00 00 00                    ..........                          LS n
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83185.105822
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 02 00 00 00 00 00 00 00                    ..........                          LS
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83185.149508
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 02 00 13 00 00 00 00 00                    ..........                          LS p
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83185.509456
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 02 00 00 00 00 00 00 00                    ..........                          LS
> ACL Data RX: Handle 11 flags 0x02 dlen 14                       [hci0] 83185.576964
      Channel: 65 len 10 [PSM 0 mode 0] {chan 0}
        a1 01 00 00 00 00 00 00 00 00                    ..........                          none
> HCI Event: Inquiry Complete (0x01) plen 1                       [hci0] 83186.850713
        Status: Success (0x00)

There is nothing abnormal. e.g. each key is pressed for 0.2-0.3s, which doesn't justify the repeating with my current keyboard settings.

3. Disable the upowerd service to stop asking the keyboard for the battery level. Nothing.
4. Currently I've changed the power management of the Bluetooth from "auto" to "on", but I have to wait at least one day to check.

Additional info:
[NEW] Device 34:88:5D:5E:0C:2F Logitech K810
[Vasilis Keyboard]# info 34:88:5D:5E:0C:2F
Device 34:88:5D:5E:0C:2F
        Name: Logitech K810
        Alias: Logitech K810
        Class: 0x000540
        Icon: input-keyboard
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
        UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v046DpB319d120


Any other ideas what can be the cause of the problem?
Comment 1 vasilis 2017-07-03 03:35:06 EDT
Update: Changing power control to "on" from "auto" didn't help as well
Comment 2 vasilis 2017-07-04 05:35:42 EDT
Could somehow increase the priority of the bluetooth and the hid driver?

Note You need to log in before you can comment on or make changes to this bug.