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
Yes, I have dbus installed and presumably running:
% ps -ef | grep dbus
100 1412 1 0 03:41 ? 00:00:00 /usr/bin/dbus-daemon
--system
Here are my installed versions:
% apt-show-versions | grep -e dbus -e bluez
libdbus-1-2/sid uptodate 0.62-4
libdbus-glib-1-2/sid uptodate 0.62-4
bluez-utils/sid uptodate 3.1-2
bluez-firmware/sid uptodate 1.0-3
dbus/sid uptodate 0.62-4
bluez-hcidump/sid uptodate 1.31-1
libbluetooth2/sid uptodate 3.1-1
On boot-up here are the reported versions:
Kernel ver. 2.4.32
BlueZ Core 2.4
HCI USB 2.7
l2cap 2.3
rfcomm 1.1
I should mention, I suppose, that I am running low on available disk
space, I will work towards cleaning that up, could this be the root of
this error?
Thanks,
jpf
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi,
> 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
do you have a correct installed bluez-hcid.conf for the D-Bus service?
Regards
Marcel
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
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
>
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