Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 103971
| Summary: | /etc/init.d/bluetooth errors | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | Chris Ricker <chris.ricker> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | ||
| 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: | 2003-09-11 21:30:03 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: | |||
| Bug Depends On: | 88859 | ||
| Bug Blocks: | 100644 | ||
Well for cosmetic reasons I suppose the rfcomm tool could refrain from actually opening its socket unless it needs to, but the modprobe shouldn't fail and there shouldn't be any errors. Bug #88859 seems to have recurred, but that isn't the problem in this case. It looks like the kernel isn't even managing to run modprobe. Does it manage to autoload any other modules? Reassigning to kernel. It autoloads other modules just fine.... I don't see this any more with kernel-2.4.22-1.2040.nptl from RHN |
I get the following error when booting up, and also when upgrading from bluez-utils-2.3-9 to bluez-utils-2.3-12: Can't open RFCOMM control socket: No such file or directory It's coming from this part of the init script: if [ -x /usr/bin/rfcomm -a -f /etc/bluetooth/rfcomm.conf ]; then /usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all fi That appears to require a socket which isn't present on my system (probably b/c I don't have bluetooth hardware) I also see the following in dmesg once this error occurs: request_module[bt-proto-3]: fork failed, errno 1