Hi,
<snip>
Am 28.05.2012 19:39, schrieb Vinicius Costa Gomes:
Hi Steffen,
On 12:24 Mon 28 May, Steffen Becker wrote:
I always got a "security block"-issue while tried to connect. I
searched your mail-archive & you told me, this problem is solved in
kernel 3.3 and later.
I installed kernel 3.4 and - hooray - no "security block" anymore!
*But* the connection still doesn't work. I connect them - they are
connected for about 2 seconds - then connection is refused.
So I really hope you can have a look at the following lines and tell
me how to solve this problem.
PS:
I'm sorry for wasting your time, but this case isn't "just for fun
for me"; it's important that it works. So I even would donate/pay
something if you can help me solve this problem.
Here is what I get when I use test-network:
# bluez-test-network 00:02:72:AE:58:73 NAP
Traceback (most recent call last):
File "/usr/bin/bluez-test-network", line 40, in <module>
device = adapter.FindDevice(address)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line
70, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line
145, in __call__
**keywords)
File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line
651, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist
From this and the hcidump, the answer is that it could not find a
server running in the remote side (i.e. the SDP service search returned
nothing).
[snip]
Hm, i don't really understand what you mean with "could not find a
server running": How can I start such a server on the remote side?
Regards,
Steffen
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
