dbus - ARM target - ERROR: Couldn't connect to session bus

[Trilok Soni]

Hi Thiago,

On Feb 16, 2008 1:38 PM, Thiago Macieira <thiago at kde.org> wrote:
> Colin Walters wrote:
> >I've always found DBUS_VERBOSE logging to not be very useful; it's
> >more designed for someone hacking on DBus itself rather than someone
> >trying to use it.
> >
> >Can you try using "strace -s1000 dbus-daemon ..." to get the actual
> >data it's sending?
>
> strace -s2048 -e read,writev
>
> D-Bus always reads in chunks of 2048 bytes and it uses writev to send.
> With that, you're eliminating the rest of the clutter.
>
> You may want to add "accept,close" if you're trying to debug connection
> problems.

Thanks for the reply. Here is the output of strace for dbus-daemon
running my "trilok" login.

#strace -s2048 -e read,writev,accept,close dbus-daemon --fork
--session --print-pid 0 --print-address 0
read(3, "\177ELF\1\1\1a\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\\%\0\0004\0\0\0x,\3\0\2\0\0\0004\0
\0\3\0(\0\"\0\37\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0d\260\1\0d\260\1\0\5\0\0\0\0\200\0\0\1\0\0\0d\260\1\0d0\2\0d0\2\0\370\32
close(3)                                = 0
read(3, "\177ELF\1\1\1a\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\210k\1\0004\0\0\0\24\255\20\0\2\0\0\0004\0
\0\7\0(\0?\0>\0\6\0\0\0004\0\0\0004\0\0\0004\0\0\0\340\0\0\0\340\0\0\0\5\0\0\0\4\0\0\0\3\0\0\0\4\21\20\0\4\21\20\2
close(3)                                = 0
read(3, "<!-- This configuration file controls the
per-user-login-session message bus.\n     Add a session-local.conf and
edit that rather than changing this \n     file directly.
-->\n\n<!DOCTYPE busconfig PUBL7
close(3)                                = 0
read(4, "b)\205\261%\310\202g\26\25\3\234", 12) = 12
close(4)                                = 0
unix:path=/tmp/session_bus_socket,guid=622985b125c882671615030000014b14
1083
Process 1082 detached

I feel that above strace output on my ARM board looks quite short from
the one generated on my Ubuntu Feisty Fawn desktop.

-- 
--Trilok Soni