From: JP Freeley <jpf321@gmail.com>
To: Filippo Giunchedi <filippo@esaurito.net>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Unable to get on on the D-Bus
Date: Wed, 26 Jul 2006 16:06:16 -0400 [thread overview]
Message-ID: <44C7CB38.2090104@gmail.com> (raw)
In-Reply-To: <20060726181802.GC6678@esaurito.net>
[-- Attachment #1.1: Type: text/plain, Size: 1939 bytes --]
Thanks for your reply.
I tried as you suggested:
# /etc/init.d/dbus restart
Stopping system message bus: dbus.
Starting system message bus: dbus.
# /etc/init.d/bluetooth restart
Restarting bluetooth: hcid sdpd.
Here is my log (/var/log/daemon.log) (nothing in /var/log/messages)
Jul 27 15:59:36 hcid[1549]: Bluetooth HCI daemon
Jul 27 15:59:36 hcid[1549]: Service could not become the primary owner.
Jul 27 15:59:36 hcid[1549]: Unable to get on D-Bus
Jul 27 15:59:36 sdpd[1551]: Bluetooth SDP daemon
I am happy to try 3.1-3, where will it be available? for "sid"?
mirrors.kernel.org/debian?
I am unfamliar with "reportbug" so if you point me to the correct place,
I would be happy to utilize it.
Thanks for your help,
jpf
Filippo Giunchedi wrote:
> Hi,
>
> On Wed, Jul 26, 2006 at 05:16:56AM -0400, JP Freeley wrote:
>
>> I have moved to the debian "sid" branch as it has 3.1 bluez included.
>>
>> When I first apt-get'd the necessary packages everything seemed to work OK.
>> After REBOOT I am getting the following messages about HCID:
>>
>> Jul 27 03:41:37 hcid[1460]: Bluetooth HCI daemon
>> Jul 27 03:41:37 sdpd[1462]: Bluetooth SDP daemon
>> Jul 27 03:41:37 hcid[1460]: Service could not become the primary owner.
>> Jul 27 03:41:37 hcid[1460]: Unable to get on D-Bus
>> Jul 27 03:41:38 dund[1481]: Bluetooth DUN daemon version 3.1
>>
>
> try to restart dbus (/etc/init.d/dbus restart) and bluetooth
> (/etc/init.d/bluetooth restart).
> Also could you please retry with 3.1-3 (available from tomorrow I hope).
>
> Last remark: please use the 'reportbug' utility when reporting a bug on a debian
> system: it will go through the proper channels and we can easily keep track of
> them.
>
> thanks,
> filippo
> --
> Filippo Giunchedi - http://esaurito.net
> PGP key: 0x6B79D401
> random quote follows:
>
> What a strange illusion it is to suppose that beauty is goodness.
> -- Lev Tolstoj
>
[-- Attachment #1.2: Type: text/html, Size: 2535 bytes --]
[-- Attachment #2: Type: text/plain, Size: 348 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-07-26 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 9:16 [Bluez-devel] Unable to get on on the D-Bus JP Freeley
2006-07-26 15:42 ` Marcel Holtmann
2006-07-26 18:18 ` Filippo Giunchedi
2006-07-26 20:06 ` JP Freeley [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=44C7CB38.2090104@gmail.com \
--to=jpf321@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=filippo@esaurito.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