DBus-Problem

Wed Apr 10 05:43:30 PDT 2013

2013/4/10 Sandeep Gopisetty <sandeep.gopisetty at igate.com>

>  Hi Krzysztof Konopko****
>
> ** **
>
> You are talking about /etc/dbus-1/system.conf,the config file is as follows
>

No, I'm talking about the config file you used to launch the daemon:
dbus-daemon --config-file=/data/bluetooth/dbus/etc/dbus-1/system.conf


> ****
>
> ** **
>
> <!-- This configuration file controls the systemwide message bus.****
>
>      Add a system-local.conf and edit that rather than changing this****
>
>      file directly. -->****
>
> ** **
>
> <!-- Note that there are any number of ways you can hose yourself****
>
>      security-wise by screwing up this file; in particular, you****
>
>      probably don't want to listen on any more addresses, add any more****
>
>      auth mechanisms, run as a different user, etc. -->****
>
> ** **
>
> <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration
> 1.0//EN"****
>
>  "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">****
>
> <busconfig>****
>
> ** **
>
>   <!-- Our well-known bus type, do not change this -->****
>
>   <type>system</type>****
>
> ** **
>
>   <!-- Run as special user -->****
>
>   <user>messagebus</user>****
>
> ** **
>
>   <!-- Fork into daemon mode -->****
>
>   <fork/>****
>
> ** **
>
>   <!-- We use system service launching using a helper -->****
>
>   <standard_system_servicedirs/>****
>
> ** **
>
>   <!-- This is a setuid helper that is used to launch system services -->*
> ***
>
>
> <servicehelper>/data/bluetooth/bluetooth_arm/bluez_dbus/libexec/dbus-daemon-launch-helper</servicehelper>
> ****
>
> ** **
>
>   <!-- Write a pid file -->****
>
>   <pidfile>/var/run/dbus/pid</pidfile>****
>
> ** **
>
>   <!-- Enable logging to syslog -->****
>
>   <syslog/>****
>
> ** **
>
>   <!-- Only allow socket-credentials-based authentication -->****
>
>   <auth>EXTERNAL</auth>****
>
> ** **
>
>   <!-- Only listen on a local socket. (abstract=/path/to/socket****
>
>        means use abstract namespace, don't really create filesystem****
>
>        file; only Linux supports this. Use path=/whatever on other****
>
>        systems.) -->****
>
>   <listen>unix:path=/var/run/dbus/system_bus_socket</listen>****
>
> ** **
>
>   <policy context="default">****
>
>     <!-- All users can connect to system bus -->****
>
>     <allow user="*"/>****
>
> ** **
>
>     <!-- Holes must be punched in service configuration files for****
>
>          name ownership and sending method calls -->****
>
>     <deny own="*"/>****
>
>     <deny send_type="method_call"/>****
>
> ** **
>
>     <!-- Signals and reply messages (method returns, errors) are allowed**
> **
>
>          by default -->****
>
>     <allow send_type="signal"/>****
>
>     <allow send_requested_reply="true" send_type="method_return"/>****
>
>     <allow send_requested_reply="true" send_type="error"/>****
>
> ** **
>
>     <!-- All messages may be received by default -->****
>
>     <allow receive_type="method_call"/>****
>
>     <allow receive_type="method_return"/>****
>
>     <allow receive_type="error"/>****
>
>     <allow receive_type="signal"/>****
>
> ** **
>
>     <!-- Allow anyone to talk to the message bus -->****
>
>     <allow send_destination="org.freedesktop.DBus"/>****
>
>     <!-- But disallow some specific bus services -->****
>
>     <deny send_destination="org.freedesktop.DBus"****
>
>           send_interface="org.freedesktop.DBus"****
>
>           send_member="UpdateActivationEnvironment"/>****
>
>   </policy>****
>
> ** **
>
>   <!-- Config files are placed here that among other things, punch****
>
>        holes in the above policy for specific services. -->****
>
>   <includedir>system.d</includedir>****
>
> ** **
>
>   <!-- This is included last so local configuration can override what's***
> *
>
>        in this standard file -->****
>
>   <include ignore_missing="yes">system-local.conf</include>****
>
> ** **
>
>   <include if_selinux_enabled="yes"
> selinux_root_relative="yes">contexts/dbus_contexts</include>****
>
> ** **
>
> </busconfig>****
>
> ** **
>
> ** **
>
> I checked the following****
>
> ** **
>
> cat /var/run/dbus/pid****
>
> 2049****
>
> ** **
>
> Please suggest me what modifications I need to do in this config file.****
>
> ** **
>
> Thanks & Regards****
>
> Sandeep Gopisetty****
>  ------------------------------
>
> *From:* Krzysztof Konopko [mailto:krzysztof.konopko at gmail.com]
> *Sent:* Wednesday, April 10, 2013 5:37 PM
> *To:* dbus at freedesktop.org
> *Cc:* Sandeep Gopisetty
> *Subject:* Re: DBus-Problem****
>
> ** **
>
> Apologize for not sending to the mailing list in the first place.****
>
> ** **
>
> It looks like you've got all your service and policy files missing or
> wrong.  Check where you system.conf file points to find service and
> additional policy (configuration) files.****
>
> ** **
>
> HTH,****
>
> Kris****
>
> ** **
>
> 2013/4/10 Sandeep Gopisetty <sandeep.gopisetty at igate.com>****
>
> Hi Krzysztof Konopko****
>
>  ****
>
> Thanks for your immediate reply****
>
> Previous issue was solved,ehen I manually added message group in
> /etc/group and user in /etc/shadow.****
>
> Now I am able to run dbus-daemon –system.****
>
>  ****
>
> Now I am stuck with the following****
>
>  ****
>
> Even the D-BUS is running hcid –n is giving the same error****
>
>  ****
>
> *hcid[1710]: Bluetooth HCI daemon*****
>
> *hcid[1710]: Could not become the primary owner of org.bluez.*****
>
> *hcid[1710]: Unable to get on D-Bus*****
>
> * *****
>
> Then I ran passkey-agent (an utility to generate the password
> commandline),it is also giving the error related to d-bus****
>
> * *****
>
> *root@(none):~# passkey-agent default 1000*****
>
> *Can't register passkey agent*****
>
> *The name org.bluez was not provided by any .service files*****
>
> * *****
>
> * *****
>
> *Please help me and provide me some solution.I am in very much need to do
> this.*****
>
> * *****
>
> Thanks & Regards****
>
> Sandeep Gopisetty****
>  ------------------------------
>
> *From:* Krzysztof Konopko [mailto:krzysztof.konopko at gmail.com]
> *Sent:* Wednesday, April 10, 2013 1:15 PM
> *To:* Sandeep Gopisetty
> *Subject:* Re: DBus-Problem****
>
>  ****
>
> Hi Sandeep,****
>
>  ****
>
> On your system, could you check the following:****
>
> id messagebus****
>
>  ****
>
> And if there's no `id' utility on your system:****
>
> grep messagebus /etc/{passwd,group}****
>
>  ****
>
> Kris****
>
>  ****
>
> 2013/4/10 sandeep <sandeep.gopisetty at igate.com>****
>
> Hi,
> My name is sandeep,currently i am working in adding bluetooth support in
> ARM board.I inserted the drivers:rfcomm,btusb,bnep,bluetooth.
> I cross compiled bluez-utils and all the other required utilitie.
> when i am starting hcid it is giving unable to get on DBus
> root@(none):/data/bluetooth/dbus/bin# hcid -n
> hcid[605]: Bluetooth HCI daemon
> hcid[605]: Unable to get on D-Bus
>
> So i came to know that i have to launch dbus.I am using dbus-1.6.8 version
> Following are the outputs of varioys commands
> dbus-launch
> DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-
> rNfAdnokq0,guid=db0383402b883abe589c9e26000005f7
> DBUS_SESSION_BUS_PID=611
> root@(none):/data/bluetooth/dbus/bin# dbus-uuidgen
> 9a4bd04bd3d7991a146d51f3000005fd
>
> dbus-daemon --config-file=/data/bluetooth/dbus/etc/dbus-1/system.conf
>
> Failed to start message bus: Could not get UID and GID for
> username "messagebus"
>
>
> Then i created UID and GID for messagebus
>  groupadd -g 101 messagebus
>  useradd -u 101 messagebus
>
> Even then also i am getting the same error
> dbus-daemon --config-file=/data/bluetooth/dbus/etc/dbus-1/system.conf
>
> Failed to start message bus: Could not get UID and GID for
> username "messagebus"
>
>
> Please help me what to do,i need help.Now i am in full trouble.
>
> Please Please help me and give me suggestions as early as possible.
>
> Thanks in advance
>
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus****
>
>  ****
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Information contained and transmitted by this e-mail is confidential and
> proprietary to iGATE and its affiliates and is intended for use only by the
> recipient. If you are not the intended recipient, you are hereby notified
> that any dissemination, distribution, copying or use of this e-mail is
> strictly prohibited and you are requested to delete this e-mail immediately
> and notify the originator or mailadmin at igate.com. iGATE does not enter
> into any agreement with any party by e-mail. Any views expressed by an
> individual do not necessarily reflect the view of iGATE. iGATE is not
> responsible for the consequences of any actions taken on the basis of
> information provided, through this email. The contents of an attachment to
> this e-mail may contain software viruses, which could damage your own
> computer system. While iGATE has taken every reasonable precaution to
> minimise this risk, we cannot accept liability for any damage which you
> sustain as a result of software viruses. You should carry out your own
> virus checks before opening an attachment. To know more about iGATE please
> visit www.igate.com.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ****
>
> ** **
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Information contained and transmitted by this e-mail is confidential and
> proprietary to iGATE and its affiliates and is intended for use only by the
> recipient. If you are not the intended recipient, you are hereby notified
> that any dissemination, distribution, copying or use of this e-mail is
> strictly prohibited and you are requested to delete this e-mail immediately
> and notify the originator or mailadmin at igate.com. iGATE does not enter
> into any agreement with any party by e-mail. Any views expressed by an
> individual do not necessarily reflect the view of iGATE. iGATE is not
> responsible for the consequences of any actions taken on the basis of
> information provided, through this email. The contents of an attachment to
> this e-mail may contain software viruses, which could damage your own
> computer system. While iGATE has taken every reasonable precaution to
> minimise this risk, we cannot accept liability for any damage which you
> sustain as a result of software viruses. You should carry out your own
> virus checks before opening an attachment. To know more about iGATE please
> visit www.igate.com.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20130410/718a8a09/attachment-0001.html>