The package maintainer did this change:
bluez (4.45-0ubuntu1) karmic; urgency=low
* debian/bluez.bluetooth.default:
- Drop. Doesn't do anything now.
* debian/bluez.bluetooth.init:
- Drop most calls in this script as now all it serves as
is to workaround a problem with dbus not being ready early
enough. Once dbus is started by an upstart service, this
should be able to be converted to an upstart service too.
As a result, rfcomm is not started automatically anymore. It broke my
ppp configuration to connect to 3G network. Now I must manually run:
# rfcomm bind all
every boot in order for things to work out.
It is now up to the package maintainer to decide where to go from here:
1. Restore rfcomm call from inside the bluetooth init script
2. Insert rfcomm call somewhere else
3. Force all users who need to manually add "rfcomm bind all" to initialization
scripts manually.
For now, as a quick & dirty trick, edit /etc/rc.local at the end and add
this line:
/usr/bin/rfcomm bind all &
before the "exit 0" line.
Hope this helps.
Bye.
--
Automatic rfcomm binding at startup doesn't work in Karmic
https://bugs.launchpad.net/bugs/416056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
