linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Au <alan.au@netcommwireless.com>
To: <linux-bluetooth@vger.kernel.org>
Subject: ConnectProfile continuously failing with InProgress error
Date: Fri, 6 Nov 2015 16:40:27 +1100	[thread overview]
Message-ID: <563C3D4B.30102@netcommwireless.com> (raw)

Hi,

I've been writing an application that invokes Device1.ConnectProfile to 
connect to a remote device. That works fine in the normal case. But 
during development sometimes the app crashes after invoking 
ConnectProfile but before the ConnectProfile async invocation returns. 
In this case bluetoothd seems to sometimes get stuck in a bad state in 
which all subsequent calls to ConnectProfile (or Connect) for the same 
device will continuously return a org.bluez.Error.InProgress failure. I 
need to reboot the box to recover.

This is reproducible with bluetoothctl. By running "connect" to a remote 
device that is not there and then exiting bluetoothctl before the 
connect result comes back. It may take a few tries but eventually 
bluetoothctl will show that any connects to that same device will always 
fail with org.bluez.Error.InProgress.

Example log:

% bluetoothctl
[NEW] Controller 18:F1:45:2F:44:EC [default]
[NEW] Device 00:07:80:31:CC:DD PT/INR Meter
[bluetooth]# connect 00:07:80:31:CC:DD
Attempting to connect to 00:07:80:31:CC:DD
[bluetooth]# exit
[DEL] Controller 18:F1:45:2F:44:EC [default]
% bluetoothctl
[NEW] Controller 18:F1:45:2F:44:EC [default]
[NEW] Device 00:07:80:31:CC:DD PT/INR Meter
[bluetooth]# connect 00:07:80:31:CC:DD
Attempting to connect to 00:07:80:31:CC:DD
Failed to connect: org.bluez.Error.InProgress
[bluetooth]# connect 00:07:80:31:CC:DD
Attempting to connect to 00:07:80:31:CC:DD
Failed to connect: org.bluez.Error.InProgress
[bluetooth]#

Note that this remains the same even after waiting for an hour or more.

I'm using 5.33. Any ideas?

Thanks.

Alan

______________________________________________________________________
This communication contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above.  If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited.  If you have received this communication in error, please notify me by telephone immediately.
______________________________________________________________________

             reply	other threads:[~2015-11-06  5:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  5:40 Alan Au [this message]
2015-11-06 10:22 ` ConnectProfile continuously failing with InProgress error Luiz Augusto von Dentz
2015-11-09  1:38   ` Alan Au

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=563C3D4B.30102@netcommwireless.com \
    --to=alan.au@netcommwireless.com \
    --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).