From: Sergio Ruiz <sejoruiz@gmail.com>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Problems running the tests in BlueZ 5.18
Date: Mon, 05 May 2014 15:19:43 +0200 [thread overview]
Message-ID: <53678FEF.4050104@gmail.com> (raw)
In-Reply-To: <20140505073728.GA24502@t440s.lan>
Hi Johan.
On 05/05/14 09:37, Johan Hedberg wrote:
> Hi Sejo,
>
> First thing that comes to mind: have you passed --enable-experimental to
> configure when building BlueZ, and have you passed -E to bluetoothd when
> running it? At least the former is needed for the thermometer plugin
> (about the latter I'm not completely sure).
>
> Johan
First, I'd like to thank you for your answer, it solved the problems I
was having.
The thing is that now I can only run the tests when I log in as root.
Despite is not a big problem, I'd like to know if there is a way of
executing the tests without having to grant root permissions (I'm
worried about security issues on the system) Is it enough to add the
current user to the lp group? Or maybe I need to modify the policies
that are set in bluetooth.conf? (by the way, now I don't have a proper
bluetooth.conf file, so I'm not sure where are those policies set now)
Finally, I'm still not able to run the proximity test. It points to the
same problem (the interface org.bluez.ProximityMonitor1 doesn't exist)
I'm not going to use this service, and since I haven't seen anything
related to the test in bluetooth.conf, I have assumed that is not
completely implemented, but still I'd like to help if some testing is
needed.
Thank you again for your help.
prev parent reply other threads:[~2014-05-05 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 18:53 Problems running the tests in BlueZ 5.18 Sejo Ruiz
2014-05-05 7:37 ` Johan Hedberg
2014-05-05 13:19 ` Sergio Ruiz [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=53678FEF.4050104@gmail.com \
--to=sejoruiz@gmail.com \
--cc=johan.hedberg@gmail.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 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.