Strange problem of dbus in my arm system

[João Ramos]

Trilok Soni escreveu:
> Hi
>
> On Mon, Mar 17, 2008 at 11:22 PM, João Ramos <joao.ramos at inov.pt> wrote:
>   
>> Hi,
>>
>>  I'm new to this mailing list, as I have come across an issue that was already reported in this mailing list. The following message is the original request.
>>  I'm trying to compile DBus and Bluez for an EP9315 ARM920t processor, and I'm having the same problem. I've enabled verbose mode on Dbus and all I see, after a dump of messages, is that DBus segfaults when hcid process is launched...
>>  Has anyone figured out this problem?
>>
>>
>>  Original message:
>>
>>
>>  Hello.I have compiled dbus for arm in scratchbox.But when I ran command dbus-daemon --system,error appeared
>>  [root@(none) /]# dbus--daemon --system
>>  [root@(none) /]# dbus-monitor --system
>>  Failed to open connection to system message bus: Did not receive a reply. Possib
>>  le causes include: the remote application did not send a reply, the message bus
>>  security policy blocked the reply, the reply timeout expired, or the network con
>>  nection was broken
>>  I added messagebus user manually in /etc/passwd and /etc/group.
>>  In /etc/group,I added these
>>  messagebus:*:502:root
>>  haldaemon:x:68:
>>  avahi:x:70:
>>  In /etc/group,I added these
>>  messagebus:*:501:502:messagebus:/:/sbin/nologin
>>  haldaemon:x:68:68:HAL daemon:/:/sbin/nologin
>>  avahi:x:70:70:Avahi daemon:/:/sbin/nologin
>>  I copied dbus-cleanup-sockets, dbus-monitor dbus-daemon, dbus-send dbus-launch, and dbus-uuidgen
>>  to /usr/bin and copied libdbus-1.so ,libdbus-1.so.3  and libdbus-1.so.3.2.0 in /usr/lib in my target file
>>  system.Because I use scram file system and files can be read only in flash,I created a link to /var/bdus-1 in /etc and
>>  var was mount point in form of ramfs therefore only it could be changed in my file system.
>>  I want to embed bluez in arm which uses dbus.After I ran dbus-daemon --system ,I ran hcid -n and error message appeared as
>>  well.
>>  hcid[481]: Bluetooth HCI daemon
>>  hcid[481]: Can't connect to system message bus: Did not receive a reply. Possibl
>>  e causes include: the remote application did not send a reply, the message bus s
>>  ecurity policy blocked the reply, the reply timeout expired, or the network conn
>>  ection was broken.
>>  hcid[481]: Unable to get on D-Bus
>>  Can I anyonet help me to figure out the problem? I will be very grateful for your help.
>>
>>     
>
> Could you please disable the optimization while compiling dbus
> library, make it -O0?
>
> It worked for me on ARM9 based TI DaVinci board.
>
>   
Thank you, I had already seen that solution in another forum, and I have 
just finished testing it. It works!
Thanks anyway.

João