From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Bug in oFono 1.15+ Handsfree GetProperties()
Date: Sun, 05 Jul 2015 06:07:46 -0500 [thread overview]
Message-ID: <55991002.4000006@gmail.com> (raw)
In-Reply-To: <E541850BD1A4194EB55388101C8C0DF37A5F8D76CB@MXCL03.fgremc.it>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
Hi Chris,
On 07/06/2015 11:38 AM, BARDEN Christopher (MM) wrote:
> Hello,
>
> Using the DBus API, I noticed that the first call to GetProperties() in
> the Handsfree interface always fails with an “InProgress” error. I have
> verified that this behavior isn’t there in 1.14, but does seem to be in
> both 1.15 and 1.16. Any subsequent calls to GetProperties() are
> successful and return the properties of that interface successfully. I
> couldn’t find a bug tracker to submit this to, so I thought this would
> be the most appropriate place. What is your recommendation for working
> around this issue?
Looks like someone forgot to mark the GetProperties method as ASYNC
which might cause this.
Try git commit 454b7e63e38b8df034a3c5e1d9b8562ca92ceb0b to see if it
fixes this issue.
The very first call to GetProperties triggers a +CNUM query to the
driver. Once the query is performed, the results are cached and the
reply is returned. All subsequent replies will be generated on the
cached results. If you have multiple clients that are trying to utilize
GetProperties during the initial query time, then all-but-one will
receive an InProgress error.
Here's the commit for reference:
diff --git a/src/handsfree.c b/src/handsfree.c
static const GDBusMethodTable handsfree_methods[] = {
- { GDBUS_METHOD("GetProperties",
+ { GDBUS_ASYNC_METHOD("GetProperties",
NULL, GDBUS_ARGS({ "properties", "a{sv}" }),
handsfree_get_properties) },
{ GDBUS_ASYNC_METHOD("SetProperty",
Regards,
-Denis
prev parent reply other threads:[~2015-07-05 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 16:38 Bug in oFono 1.15+ Handsfree GetProperties() BARDEN Christopher
2015-07-05 11:07 ` Denis Kenzior [this message]
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=55991002.4000006@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.