Bug 158722
Summary: | bluetooth initscript should start erlier | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Hans-Gerd van Schelve <van-schelve> |
Component: | bluez-utils | Assignee: | Ric Wheeler <rwheeler> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | mherbert |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 13:31:30 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
Hans-Gerd van Schelve
2005-05-25 08:01:36 UTC
Unfortunately we're also constrained by the use of dbus -- we have to start bluetooth after dbus is running. What's the failure mode? You're using dialup over rfcomm? Doesn't the ppp just keep failing until the /dev/rfcommX device exists, and then manage to start correctly after that? Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |