Bug 541701 - HID does not reconnect after rebooting
HID does not reconnect after rebooting
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-11-26 14:04 EST by mail@romal.de
Modified: 2010-12-03 21:44 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 21:44:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description mail@romal.de 2009-11-26 14:04:23 EST
Description of problem:

pairing does work and devices work afterwards, but after rebooting mouse & keyboard are dead.

no visible error messages in /var/log/messages.

Deleting and repairing does fix the problem, until the next reboot. I'm using MS Intellimouse Explorer & keyboard

Nov 26 20:00:49 orilla kernel: input: Microsoft Mouse as /devices/pci0000:00/0000:00:02.0/usb3/3-10/3-10.1/3-10.1:1.0/bluetooth/hci0/hci0:7/input10
Nov 26 20:00:49 orilla kernel: generic-bluetooth 0005:045E:0098.0005: input,hidraw3: BLUETOOTH HID v0.10 Mouse [Microsoft Mouse] on 00:0D:3A:A5:7A:55

Nov 26 20:02:39 orilla bluetoothd[1219]: link_key_request (sba=00:0D:3A:A5:7A:55, dba=00:0D:3A:A4:EE:BA)
Nov 26 20:02:39 orilla bluetoothd[1219]: ioctl_connadd(): Bad file descriptor(9)
Nov 26 20:02:40 orilla kernel: input: Microsoft Keyboard as /devices/pci0000:00/0000:00:02.0/usb3/3-10/3-10.1/3-10.1:1.0/bluetooth/hci0/hci0:6/input11
Nov 26 20:02:40 orilla kernel: generic-bluetooth 0005:045E:0099.0006: input,hidraw4: BLUETOOTH HID v0.10 Keyboard [Microsoft Keyboard] on 00:0D:3A:A5:7A:55

Sometimes I get this:

Nov 26 20:01:05 orilla bluetoothd[1219]: Host is down (112)

The same HW worked on F11 without problems.

Sometimes choosing reconnect from gnome-bluetooth helps.

Version-Release number of selected component (if applicable):

[root@orilla ~]# rpm --query --all | grep -i blue
[root@orilla ~]# 

How reproducible:
Every time.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Bug Zapper 2010-11-04 01:14:15 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
Comment 2 Bug Zapper 2010-12-03 21:44:13 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

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