dbus, epiphany, rekonq

Polytropon freebsd at edvax.de
Mon Mar 19 12:44:25 UTC 2012

On Mon, 19 Mar 2012 12:21:29 +0000, Anton Shterenlikht wrote:
> I can't lauch www/epiphany or www/rekonq
> on ia64 -current, due to some dbus issue:
> TZAV> ps ax|grep dbus
>  1435  -  Is       0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sess
>  1434  2- I        0:00.01 dbus-launch --autolaunch=fb0372ea595109904f5a068e00000180 --binary-synta
> 41284  5  RL+      0:00.00 grep dbus
> TZAV> epiphany
> ** (epiphany:41285): WARNING **: Unable to connect to session bus: Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory
> TZAV> rekonq 
> unnamed app(41291): KUniqueApplication: Cannot find the D-Bus session server:  "Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory" 
> unnamed app(41290): KUniqueApplication: Pipe closed unexpectedly. 
> TZAV> ps ax | grep dbus
>  1435  -  Is       0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sess
>  1434  2- I        0:00.01 dbus-launch --autolaunch=fb0372ea595109904f5a068e00000180 --binary-synta
> 41294  5  RL+      0:00.00 grep dbus
> What am I doing wrong?

Have you checked the presence of the /tmp/dbus-dyUjnhLBwE socket?

> I understand dbus is a required part of
> a modern browser, it is no longer an option, right?

What?! I don't think that this is an acceptable opinion. :-)

Both browsers you mentioned are part of KDE or Gnome.
THOSE heavily rely on DBUS, that's right, and due to
the transition of dependencies, _their_ web browsers
also do.

For example, I'm not running DBUS here, but I run modern
web browsers. I just don't run _those_ two. :-)

So did you properly build your KDE and Gnome components
with DBUS enabled, and all of their configurable dependencies
also with DBUS enabled? It _may_ be that the use of DBUS
is not among the default building options for one of the
nested dependencies, and that one might be _the one_ that
now shoots your foot. :-)

Your ps listing indicates that you are running DBUS, so
that shouldn't be the problem. Missing DBUS support in one
of the required components _could_ be.

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

More information about the freebsd-questions mailing list