From: Felipe Ferreri Tonello <eu@felipetonello.com>
To: Mark Spruiell <mes@zeroc.com>, linux-bluetooth@vger.kernel.org
Subject: Re: Connection failures on Ubuntu
Date: Wed, 11 Nov 2015 10:53:53 +0000 [thread overview]
Message-ID: <56431E41.6030404@felipetonello.com> (raw)
In-Reply-To: <CABOZqnh3p4NXcGMyeT3UjYH+OdU4phV0bGPtoUJa2KzEZjp5iw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]
Hi Mark,
On 10/11/15 17:20, Mark Spruiell wrote:
> I'm not able to connect to a service running on Ubuntu 15.10. The
> system-provided BlueZ version is 5.35.
>
> I can reproduce it using the test scripts. On Ubuntu:
>
> ./test-profile -s -u b85280dd-b78a-4a45-be4b-b6fec4abd86f -n "Test Server" -C 5
>
> sdptool shows the service:
>
> Service Name: Test Server
> Service RecHandle: 0x10009
> Service Class ID List:
> UUID 128: b85280dd-b78a-4a45-be4b-b6fec4abd86f
> Protocol Descriptor List:
> "L2CAP" (0x0100)
> "RFCOMM" (0x0003)
> Channel: 5
>
> On a different host (this one running Fedora 22 with BlueZ 5.29), I
> start a client:
>
> ./test-profile -u b85280dd-b78a-4a45-be4b-b6fec4abd86f -c
>
> and then
>
> ./test-device connect <ubuntu-addr> b85280dd-b78a-4a45-be4b-b6fec4abd86f
> Traceback (most recent call last):
> File "./test-device", line 104, in <module>
> device.ConnectProfile(args[2])
> 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.Failed: Connection refused
>
> Other times I will get:
>
> dbus.exceptions.DBusException: org.bluez.Error.Failed: Resource
> temporarily unavailable
>
> These hosts are already paired. Things work fine when both hosts are
> using Fedora 22.
>
> Any suggestions on how I can diagnose this further?
I had this type of problem on Ubuntu when trying to register master's
build of bluetoothd to D-Bus on Ubuntu as well and not on Fedora.
Try to tweak /etc/dbus-1/system.d/bluetooth.conf user permissions just
for development.
--
Felipe
[-- Attachment #2: 0x92698E6A.asc --]
[-- Type: application/pgp-keys, Size: 4908 bytes --]
next prev parent reply other threads:[~2015-11-11 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 17:20 Connection failures on Ubuntu Mark Spruiell
2015-11-11 10:53 ` Felipe Ferreri Tonello [this message]
2015-11-14 0:39 ` Mark Spruiell
2015-11-14 0:51 ` Mark Spruiell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56431E41.6030404@felipetonello.com \
--to=eu@felipetonello.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mes@zeroc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).