Bugzilla Bug 181176

all previous versions of bluez-utils run: "rfcomm -f /etc/bluetooth/rfcomm.conf
bind all" on startup. Now I must run it by hand, otherwise I can't use my
cellphone as modem. Do I miss something?


Reproducible: Always

Steps to Reproduce:
1. blug in usb-bluetooth dongle

Actual Results:  
rfcomm bindings are not set

Expected Results:  
rfcomm bindings should be set:
# rfcomm
rfcomm0: 00:15:D3:0D:B0:43 channel 8 connected [tty-attached]

(In reply to comment #0)
> Do I miss something?

Kinda; this is supposed to be handled by dbus now... 

http://wiki.bluez.org/wiki/Serial

(In reply to comment #1)
> Kinda; this is supposed to be handled by dbus now... 
> 
> http://wiki.bluez.org/wiki/Serial

I've set Autostart=true in /etc/bluetooth/serial.service. But "rfcomm" shows
nothing and /dev/rfcomm0 does not exist.

log:
serial[4754]: Bluetooth Serial Port daemon
serial[4754]: Registered manager path:/org/bluez/serial
sina hcid[4751]: HCI dev 0 up

any hints?

Created an attachment (id=121392) [edit]
rfcomm.py

Try this little python script from the wiki:
$ rfcomm.py 00:0B:0D:00:1B:XX 1
Connected /dev/rfcomm0 to 00:0B:0D:00:1B:XX
Press CTRL-C to disconnect

the serial service isn't really finished yet, as you can read here:
http://thread.gmane.org/gmane.linux.bluez.user/12239/focus=12241

"simply call "rfcomm bind all"."

(In reply to comment #3)
> 
> the serial service isn't really finished yet, as you can read here:
> http://thread.gmane.org/gmane.linux.bluez.user/12239/focus=12241
> 
> "simply call "rfcomm bind all"."
> 

So I guess we should add that rfcomm bind all part back to the init script for
now.

I also think that would be a wise idea :-)

(In reply to comment #5)
> I also think that would be a wise idea :-)
> 

Added back in 3.11-r2.