From: Niv <nivv@cs.bgu.ac.il>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] headset wont work <sdp?>
Date: Fri, 13 Jan 2006 03:47:02 +0200 [thread overview]
Message-ID: <43C70696.4010307@cs.bgu.ac.il> (raw)
In-Reply-To: <43C6DBA0.9050002@cs.bgu.ac.il>
blacky niv # hcid -n
hcid[28261]: Bluetooth HCI daemon
hcid[28261]: Can't open system message bus connection: Failed to connect
to socket /var/run/dbus/system_bus_socket: No such file or directory
hcid[28261]: Starting security manager 0
hcid[28261]: Registering DBUS Path: /org/bluez/Device/hci0
Segmentation fault
blacky niv # ls -la /var/run/dbus/system_bus_socket
ls: /var/run/dbus/system_bus_socket: No such file or directory
blacky niv # locate system_bus_socket
blacky niv # /etc/init.d/dbus
dbus dbus.init-0.60
blacky niv # /etc/init.d/dbus
dbus dbus.init-0.60
blacky niv # /etc/init.d/dbus start
* Starting D-BUS system messagebus
... [ ok ]
blacky niv # hcid -n
hcid[28466]: Bluetooth HCI daemon
hcid[28466]: Starting security manager 0
hcid[28466]: Registering DBUS Path: /org/bluez/Manager/default/Controller
hcid[28466]: Registering DBUS Path: /org/bluez/Manager/hci0/Controller
hcid[28466]: Registering DBUS Path: /org/bluez/Device/hci0
wait a min , aint dbus in the dependend /etc/init.d/bluetooth ?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-01-13 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 22:08 [Bluez-users] headset wont work <sdp?> Niv
2006-01-12 18:14 ` Niv
2006-01-12 22:43 ` Niv
2006-01-13 1:47 ` Niv [this message]
2006-01-13 3:20 ` Niv
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=43C70696.4010307@cs.bgu.ac.il \
--to=nivv@cs.bgu.ac.il \
--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 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.