Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 242591 - start hidd fails at boot
start hidd fails at boot
Status: CLOSED DUPLICATE of bug 230017
Product: Fedora
Classification: Fedora
Component: bluez-utils (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Woodhouse
Depends On:
  Show dependency treegraph
Reported: 2007-06-04 18:53 EDT by Brian G. Anderson
Modified: 2007-11-30 17:12 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-21 06:54:28 EDT
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 Brian G. Anderson 2007-06-04 18:53:10 EDT
Description of problem:
starting hidd always fails with a "Can't listen on HID control channel: Address
already in use"

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

How reproducible:

Steps to Reproduce:
1. service hidd restart
Actual results:
start fails with message

Expected results:

Additional info:
This is a Dell Lattitude D620.  Bluetooth works and I can send an receive files
from my phone using obex-ftp.  This is a fresh install of FC7.
Comment 1 Brian G. Anderson 2007-06-04 19:04:06 EDT
After some experimentation,  I found that if I stop bluetooth services and then
start hidd it succeeds.  I can restart the bluetooth services after this. 
However, if I switch the order, hidd won't start.
Comment 2 Brian G. Anderson 2007-06-04 19:13:27 EDT
Curiously, once I stop bluetooth, restart hidd, and restart bluetooth,  I can
start and stop hidd with no further problems.
Comment 3 Evert Verhellen 2007-06-28 17:42:03 EDT
I can confirm Brian's workaround. I adjusted the startup priority of the HIDD
service from 26 to 24 and updated the symbolic links with "chkconfig hidd
resetpriorities". After rebooting, doing "hidd --search" discovers my Bluetooth
mouse correctly.
Comment 4 David Woodhouse 2007-07-21 06:54:28 EDT

*** This bug has been marked as a duplicate of 230017 ***

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