[SOLVED] dbus: EOF in dbus-launch reading address from bus daemon

Mr. Bougo · 2009-07-18 09:28:01

Hello! I installed dbus from the extra repository, but it doesn't seem to work correctly...

dbus-monitor outputs this:
Failed to open connection to session message bus: dbus-launch failed to autolaunch D-Bus session: EOF in dbus-launch reading address from bus daemon

ps aux | grep dbus shows the daemon is correctly launched:
dbus 5336 0.0 0.0 2140 824 ? Ss 11:18 0:00 /usr/bin/dbus-daemon --system

My DAEMONS array is set this way:
DAEMONS=(syslog-ng network netfs crond @sshd alsa hal g15daemon)

I did some googling, but it didn't really help... I have no idea how to fix this. Does any of you know?

Thanks in advance for your help

EDIT: it seems dbus-monitor --system sees the daemon! But I have no idea what that means...
I actually need dbus for a python plugin for xchat, to control audacious2. Maybe I should try to adapt that script.

EDIT2: Oh, so it seems I should start the "session daemon" as well, that's what I need...

EDIT3: dbus-daemon --session segfaults

EDIT4: nevermind, that's not how it's supposed to be launched anyway... I see there's a /etc/X11/xinit/xinitrc.d/30-dbus file that is supposed to take care of all this... Is the execution of this logged anywhere? grepping dbus in /var/log shows a lot of messages like this:
Jul 18 11:44:30 arch kernel: dbus-daemon[23490]: segfault at 6fdf85e0 ip b7e5c2cc sp bfc86d10 error 4 in libGL.so.185.18.14[b7e35000+80000]
in messages.log and kernel.log...

Last edited by Mr. Bougo (2009-07-19 08:32:09)

bernarcher · 2009-07-18 10:24:55

You should have hal started as soon as possible. This would provide a running dbus interface for any following task, thus

DAEMONS=(syslog-ng hal network netfs crond @sshd alsa g15daemon)

And make sure to not background hal. It must fully initialize otherwise other demons might fail.

Mr. Bougo · 2009-07-18 13:59:32

Moving hal right after syslong-ng didn't solve my issue... Thank you for the tip, though

bernarcher · 2009-07-18 15:22:47

As dbus appears correctly launched some other daemon could be the cause. Did you try to successively disable one by one and check if the problem goes away?

All your daemons run ok here except g15daemon which I don't know much of. Maybe this is the culprit.

Last edited by bernarcher (2009-07-18 15:23:27)

Mr. Bougo · 2009-07-19 08:11:01

That doesn't seem to work either...

But dbus does not seem to be correctly launched, actually... What appears in the process list is /usr/bin/dbus-daemon --system, I believe what I need is another instance of it, with --session instead of --system...
And I guess /etc/X11/xinit/xinitrc.d/30-dbus is supposed to take care of launching that, but somehow fails.

Last edited by Mr. Bougo (2009-07-19 08:11:10)

Mr. Bougo · 2009-07-19 08:35:09

I think I solved the problem!

I copied the contents of the 30-dbus script from xinitrc.d in my ~/.xinitrc, and changed this line:
eval `$dbuslaunch --sh-syntax --exit-with-session`
to this:
eval `$dbuslaunch --sh-syntax`

Apparently, the dbus daemon then keeps running: the process list shows this:
/usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
and dbus-monitor doesn't report any error.

Maybe it's related to the fact that I use wmii, not a heavyweight DE which would possibly take care of that dbus thing?

Last edited by Mr. Bougo (2009-07-19 08:36:03)

Arch Linux

#1 2009-07-18 09:28:01

[SOLVED] dbus: EOF in dbus-launch reading address from bus daemon

#2 2009-07-18 10:24:55

Re: [SOLVED] dbus: EOF in dbus-launch reading address from bus daemon

#3 2009-07-18 13:59:32

Re: [SOLVED] dbus: EOF in dbus-launch reading address from bus daemon

#4 2009-07-18 15:22:47

Re: [SOLVED] dbus: EOF in dbus-launch reading address from bus daemon

#5 2009-07-19 08:11:01

Re: [SOLVED] dbus: EOF in dbus-launch reading address from bus daemon

#6 2009-07-19 08:35:09

Re: [SOLVED] dbus: EOF in dbus-launch reading address from bus daemon

Board footer