From: Steven Davies <linux-bluetooth-list@steev.me.uk>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: Unable to connect to device after connected_callback() has run
Date: Sat, 26 Sep 2015 21:02:12 +0100 [thread overview]
Message-ID: <5606F9C4.2060307@steev.me.uk> (raw)
In-Reply-To: <CAD0=r8zVkFUQC7Xw3i5MG-oees0tScSJz=5Toao=rSNo4xckrA@mail.gmail.com>
Hi Jakub,
>> Following on from my problems with GATT discovery, I now have another
>> issue: I have a Python program which waits for the Connected=True
>> PropertiesChanged callback from dbus, then sends a WriteValue to a
>> GattCharacteristic1 interface.
>>
>> The issue is that immediately after the Connected=True message comes
>> back, a WriteValue fails with "DBusException: org.bluez.Error.Failed:
>> Not connected". However, calling the WriteValue a few seconds later
>> executes correctly.
>
> I had same issue, and I sent patches to fix it around 2 weeks ago.
> Which version of bluetoothd are you using ?
> Can you retry when running from repository master ?
Apologies for clicking send too soon on the last message. I can see you
and Luiz created patches for this so I'll pull the latest from master
and try. Currently I'm using the 5.34 release. I'll report back once
I've done that.
Thanks
Steven Davies
next prev parent reply other threads:[~2015-09-26 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 19:35 Unable to connect to device after connected_callback() has run linux-bluetooth-list
2015-09-26 19:45 ` Jakub Pawlowski
2015-09-26 19:59 ` Steven Davies
2015-09-26 20:02 ` Steven Davies [this message]
2015-09-26 20:30 ` Steven Davies
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=5606F9C4.2060307@steev.me.uk \
--to=linux-bluetooth-list@steev.me.uk \
--cc=linux-bluetooth@vger.kernel.org \
/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).