Bug 242591
Summary: | start hidd fails at boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brian G. Anderson <bikehead> |
Component: | bluez-utils | Assignee: | David Woodhouse <dwmw2> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | bjohnson, evert.verhellen, redhat-bugzilla, silfreed |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-07-21 10:54:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian G. Anderson
2007-06-04 22:53:10 UTC
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. Curiously, once I stop bluetooth, restart hidd, and restart bluetooth, I can start and stop hidd with no further problems. 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. |