Bug 1039738
Summary: | Apple Wireless Keyboard (Bluetooth) often won't pair, won't connect | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Clarke Wixon <clarke> |
Component: | bluez | Assignee: | Don Zickus <dzickus> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | dwmw2, dzickus, ikke, info, kalevlember, marcel, masood, nicku, redhat-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-06-29 13:27:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Clarke Wixon
2013-12-09 21:31:06 UTC
A little more info: Here's another batch of dmesg entries, from a reboot instance when I couldn't obtain a keyboard connection at all, after a good number of attempts: [ 29.979164] Bluetooth: RFCOMM TTY layer initialized [ 29.979183] Bluetooth: RFCOMM socket layer initialized [ 29.979184] Bluetooth: RFCOMM ver 1.11 [ 68.895312] Bluetooth: hci0 corrupted ACL packet [ 72.907443] Bluetooth: hci0 corrupted ACL packet [ 72.907602] Bluetooth: hci0 ACL packet for unknown connection handle 12 [ 88.228154] Bluetooth: hci0 corrupted ACL packet [ 88.228313] Bluetooth: Frame is too short (len 1) [ 130.392135] Bluetooth: hci0 corrupted ACL packet [ 130.392388] Bluetooth: hci0 ACL packet for unknown connection handle 12 [ 130.392391] Bluetooth: hci0 ACL packet for unknown connection handle 12 [ 140.788508] Bluetooth: hci0 corrupted ACL packet [ 140.788651] Bluetooth: Frame is too short (len 1) [ 143.375662] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 143.375674] Bluetooth: HIDP socket layer initialized [ 143.383622] Bluetooth: hci0 ACL packet for unknown connection handle 16 This is on kernel 3.11.10-301.fc20.x86_64 now. And later, trying to connect via bluetoothctl once again: [NEW] Controller 00:02:72:33:87:F6 omnipotus [default] [NEW] Device 00:1B:63:FA:84:9B Apple Wireless Keyboard Agent registered [bluetooth]# connect 00:1B:63:FA:84:9B Attempting to connect to 00:1B:63:FA:84:9B [CHG] Device 00:1B:63:FA:84:9B Connected: yes [bluetooth]# info 00:1B:63:FA:84:9B Device 00:1B:63:FA:84:9B Name: Apple Wireless Keyboard Alias: Apple Wireless Keyboard Class: 0x002540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) Modalias: usb:v05ACp022Cd0136 Failed to connect: org.bluez.Error.Failed [CHG] Device 00:1B:63:FA:84:9B Connected: no [CHG] Device 00:1B:63:FA:84:9B Connected: yes [bluetooth]# connect 00:1B:63:FA:84:9B Attempting to connect to 00:1B:63:FA:84:9B [CHG] Device 00:1B:63:FA:84:9B Connected: no Failed to connect: org.bluez.Error.Failed [CHG] Device 00:1B:63:FA:84:9B Connected: yes [CHG] Device 00:1B:63:FA:84:9B Connected: no [CHG] Device 00:1B:63:FA:84:9B Connected: yes [CHG] Device 00:1B:63:FA:84:9B Connected: no [bluetooth]# exit [DEL] Controller 00:02:72:33:87:F6 omnipotus [default] Note that even when it says "Connected: yes" typing on the bluetooth keyboard doesn't do anything. And that little set of attempts yields the following in dmesg: [80103.555446] Bluetooth: hci0 corrupted ACL packet [80103.555474] Bluetooth: hci0 ACL packet for unknown connection handle 0 [80143.432805] Bluetooth: hci0 corrupted ACL packet [80147.446949] Bluetooth: hci0 corrupted ACL packet [80147.447054] Bluetooth: hci0 ACL packet for unknown connection handle 12 [80152.873144] Bluetooth: hci0 ACL packet for unknown connection handle 16 Just to confirm, it is not just you. I suffer also from this on F20. kernel-3.12.6-300.fc20.x86_64 Same problem here Sometimes the keyboard connects after it rebooting works for few minutes and then bluetooth stops responding. Even the l2ping on my mobile doesn't reply anymore. bluez-5.13-1 $ dmesg | grep -i bluetooth [ 6.254295] Bluetooth: Core ver 2.16 [ 6.254309] Bluetooth: HCI device and connection manager initialized [ 6.254315] Bluetooth: HCI socket layer initialized [ 6.254316] Bluetooth: L2CAP socket layer initialized [ 6.254320] Bluetooth: SCO socket layer initialized [ 10.222907] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.222909] Bluetooth: BNEP filters: protocol multicast [ 10.222916] Bluetooth: BNEP socket layer initialized [ 330.501936] Bluetooth: RFCOMM TTY layer initialized [ 330.501947] Bluetooth: RFCOMM socket layer initialized [ 330.501948] Bluetooth: RFCOMM ver 1.11 [ 383.206518] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 383.206528] Bluetooth: HIDP socket layer initialized [ 388.979576] Bluetooth: hci0 corrupted ACL packet [ 388.979606] Bluetooth: Frame is too short (len 1) [ 389.018282] Bluetooth: hci0 ACL packet for unknown connection handle 16 [ 1346.936614] Bluetooth: hci0 corrupted ACL packet [ 1346.936642] Bluetooth: hci0 ACL packet for unknown connection handle 185 [ 1349.710461] Bluetooth: hci0 corrupted ACL packet [ 1395.894516] Bluetooth: hci0 corrupted ACL packet [ 1395.894542] Bluetooth: hci0 ACL packet for unknown connection handle 12 [ 1395.894546] Bluetooth: hci0 ACL packet for unknown connection handle 8 [ 2393.659881] Bluetooth: hci0 corrupted ACL packet [ 2393.663641] Bluetooth: Wrong link type (-2) [ 2393.663652] Bluetooth: hci0 ACL packet for unknown connection handle 517 [ 2393.860845] Bluetooth: hci0 corrupted ACL packet [ 2394.698495] Bluetooth: hci0 corrupted ACL packet [ 2482.699519] Bluetooth: hci0 ACL packet for unknown connection handle 11 [ 2482.699526] Bluetooth: hci0 ACL packet for unknown connection handle 8 Well, OK. My problem seems to have been resolved by some combination of bug 1027465 getting fixed and a hardware workaround for my Apple Magic Trackpad, or perhaps some other thing that has changed that I'm unaware of. My Trackpad is an old one, and apparently the battery spring terminal has lost some of its bounce. So any movement on my desk at all caused the batteries to lose connection and the trackpad to disconnect and try to renegotiate. I stuck a folded piece of foil in the battery compartment and everything seems fine now, not just with the Trackpad, but also with the keyboard. No more connection problems at all. I have no idea why this Trackpad issue caused problems with the keyboard, but eh, sometimes it's better not to ask too many questions. Unless someone else is still having trouble, I'm inclined to close this. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |