This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/897255
Title:
RFCOMM channel 1 and automatic channel choosing broken cause of DUN
Status in bluez package in Ubuntu:
Invalid
Bug description:
I want to set up a bluetooth RFCOMM connection between two devices
with some script. I use python bluez bindings for that.
I discovered that setting up a server, using the first free channel, won't
throw an error but doesn't give me a reliable connection either using some code
like provided by http://people.csail.mit.edu/albert/bluez-intro/x232.html with
port = bluetooth.PORT_ANY
The first free port discovered is port 1.
After "playing" around (getting frustrated investigating possible
other mistakes or sources of error), I finally set it to port = 5
(some fixed port > 1).
It worked. Trying to set up a second server on the same port threw an
error. Like it should.
After learning about the command "sdptool browse local" i saw, that
some DUN service occupied RFCOMM channel 1. But no one threw an error.
I did not found a file which set up the DUN service and I don't know a
method how to get the process which owns this DUN service or set it
up.
I think it is an error cause choosing the first free RFCOMM channel
should just work and acquiring a already used channel should result in
an informative and unique error message. Also it would be nice to know
which process set up and owns some bluetooth service.
----
Ubuntu 11.10
$ apt-cache policy bluez bluez-compat bluez-tools bluez-utils python-bluez
bluez:
Installed: 4.96-0ubuntu4
Candidate: 4.96-0ubuntu4
Version table:
*** 4.96-0ubuntu4 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386
Packages
100 /var/lib/dpkg/status
4.96-0ubuntu3 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
bluez-utils:
Installed: 4.96-0ubuntu4
Candidate: 4.96-0ubuntu4
Version table:
*** 4.96-0ubuntu4 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric-updates/universe
i386 Packages
100 /var/lib/dpkg/status
4.96-0ubuntu3 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric/universe i386
Packages
python-bluez:
Installed: 0.18-1build1
Candidate: 0.18-1build1
Version table:
*** 0.18-1build1 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric/universe i386
Packages
100 /var/lib/dpkg/status
bluez-compat:
Installed: (none)
Candidate: 4.96-0ubuntu4
Version table:
4.96-0ubuntu4 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric-updates/universe
i386 Packages
4.96-0ubuntu3 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric/universe i386
Packages
bluez-tools:
Installed: (none)
Candidate: 0.1.38+git662e-2ubuntu1
Version table:
0.1.38+git662e-2ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ oneiric/universe i386
Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/897255/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
