Bug 103971 - /etc/init.d/bluetooth errors
Summary: /etc/init.d/bluetooth errors
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On: 88859
Blocks: CambridgeTarget
TreeView+ depends on / blocked
Reported: 2003-09-08 16:55 UTC by Chris Ricker
Modified: 2007-04-18 16:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-09-11 21:30:03 UTC

Attachments (Terms of Use)

Description Chris Ricker 2003-09-08 16:55:50 UTC
I get the following error when booting up, and also when upgrading from




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

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

Comment 1 David Woodhouse 2003-09-08 23:18:54 UTC
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.

Comment 2 Chris Ricker 2003-09-09 13:28:49 UTC
It autoloads other modules just fine....

Comment 3 Chris Ricker 2003-09-11 21:29:48 UTC
I don't see this any more with kernel-2.4.22-1.2040.nptl from RHN

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