From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] unique bus name
Date: Thu, 31 Jan 2008 01:15:27 +0200 [thread overview]
Message-ID: <6347D128-2294-454F-B475-43D7104434F1@gmail.com> (raw)
In-Reply-To: <200801302220.m0UMKKCN012585@alumnus.caltech.edu>
Hi,
On Jan 31, 2008, at 0:20, Russell A. Bell wrote:
> Quoth the 'AudioDevices' wiki:
>
> 'The ":X.Y" in the following examples is the unique bus name
> of the audio service. You get it in the reply to the ActivateService
> method call:
> $dbus-send --system --print-reply --dest=org.bluez /org/bluez
> org.bluez.Manager.ActivateService string:audio'
>
> When I make this call I get three numbers back, for example:
>
> method return sender=:1.0 -> dest=:1.1
> string ":1.2"
>
> which is the 'unique bus name of the audio service'? I think 1.0 is
> the source (i.e., the bluetooth transceiver); the destination would
> seem to be :1.1; what is :1.2 ?
:1.0 is the sender of the method return to the ActivateService method
call, i.e. hcid. :1.1 is the destination of the method method return,
i.e. dbus-send. :1.2 is the value returned as the single parameter of
the method return, i.e. the unique name of the audio service.
>
> When I try to use either of them to CreateHeadset I get:
>
> Error org.freedesktop.DBus.Error.ServiceUnknown: The name :1.x was
> not provided by any .service files
>
> for 1.1 or 1.2
That's because :1.1, i.e. the first dbus-send process, doesn't exist
any more. And because :1.2, which for a short moment was the audio
service, failed to initialize for some reason and exited.
> /var/log/debug contains:
>
> Jan 30 13:14:29 randytool hcid[8110]: Child PID 8115 got the unique
> bus name :1.2
> Jan 30 13:14:29 randytool hcid[8110]: name_listener_add(:1.2)
> Jan 30 13:14:29 randytool hcid[8110]: /org/bluez:
> org.bluez.Database.AddServiceRecord()
> Jan 30 13:14:29 randytool hcid[8110]: Service owner exited: :1.2
> Jan 30 13:14:29 randytool hcid[8110]: Audio service (audio) exited
> with status 1
>
>
> Does this indicate that the service record was created then
> deleted immediately?
It seems the audio service is failing to start for some reason. Could
you try running it manually as root with "/usr/lib/bluetooth/
bluetoothd-service-audio -s" as see what messages you get? You'll need
to rename or remove the /etc/bluetooth/audio.service file before that
so hcid doesn't complain about duplicate services.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-01-30 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 22:20 [Bluez-users] unique bus name Russell A. Bell
2008-01-30 23:15 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-31 20:28 Russell A. Bell
2008-01-31 20:48 ` Johan Hedberg
2008-02-01 21:07 Russell A. Bell
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=6347D128-2294-454F-B475-43D7104434F1@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
/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