[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

I've just tried to connect my Ubuntu via Samsung Avila bluetooth modem for the first time and encountered this bug. I thought I did something wrong, discovered manual rfcomm connect command, and after that Network Manager discovered the modem and connected to my moblie provider nicely and quickly :

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

Same problem here under Lucid. /dev/rfcomm0 is not created I must do it manually with a "sudo rfcomm bind 0" -- 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 su

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

** Changed in: bluez (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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 B

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

I had the same problem after upgrading to karmic. It used to work with hardy/intrepid/jaunty. The hints on this page solved the issue for me. Thanks -- Automatic rfcomm binding at startup doesn't work in Karmic https://bugs.launchpad.net/bugs/416056 You received this bug notification because you

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

OK, I checked the channel and now the modem is recognized. I have another problem, Gnome PPP, at startup of Ubuntu, the first time I try to connect, falls asleep for about 1 minute. From the second time this does not happen anymore. This trick works just as well? Since the settings gnomePPP I have

Re: [Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

That's a device binding issue then, Please check the channel. My Nokia E71 chooses an arbitrary bluetooth channel for DUN at startup. Usually it ticks with channel 4, but it changes sometimes. rfcomm needs to be informed of the correct channel at rfcomm.conf, it isn't able to find the channel by it

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

No, bluetooth is turned on. I also redid the pairing and restarted the phone I do not understand ... -- 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,

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

@mantakbilug: I get that message when bluetooth in Nokia is turned off for example. -- 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. --

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

I applied the trick, but I get the following error from gnome PPP: --> Cannot open /dev/rfcomm0: Host is down What could be not working? -- Automatic rfcomm binding at startup doesn't work in Karmic https://bugs.launchpad.net/bugs/416056 You received this bug notification because you a

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

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

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

I still can't connect, also following the advice. I can connect only entering the command rfcomm connect /dev/rfcomm0 00:00:00:00:00:00 1 at startup. In this way I can connect by network manager (And not by GnomePPP), after setting the broadband. This solution has 3 problems: 1)I give the comm

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

** Tags added: rfcomm -- 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://

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

** Description changed: - Description: Ubuntu karmic (development branch) + Description: Ubuntu Karmic (development branch) Release: 9.10 The bluetooth modem of my Nokia phone doesn't work in Ubuntu Karmic. The error message reads: "Cannot open /dev/rfcomm0: No such file or direc

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

** Description changed: Description: Ubuntu karmic (development branch) Release: 9.10 - - The modem bluetooth of my Nokia phone don't work in Ubuntu karmic - the device /dev/rfcomm0 do not exist. - I don't now howto create this device. - + The bluetooth modem of my Nokia phone doesn

[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work in Karmic

** Summary changed: - Cannot open /dev/rfcomm0: No such device + Automatic rfcomm binding at startup doesn't work in Karmic -- 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 B