dbus, epiphany, rekonq

Da Rock freebsd-questions at herveybayaustralia.com.au
Wed Mar 21 14:33:44 UTC 2012

On 03/21/12 19:29, Anton Shterenlikht wrote:
> On Wed, Mar 21, 2012 at 04:12:50AM +0100, Bernt Hansson wrote:
>> 2012-03-19 13:21, Anton Shterenlikht skrev:
>>> 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?
>>> I understand dbus is a required part of
>>> a modern browser, it is no longer an option, right?
>>> Many thanks
>> You do have this in /etc/rc.conf
>> dbus_enable="YES"
> I didn't think it was necessary, as firefox3
> launches dbus-daemon on startup. But I'll give
> it a go.
> Thanks
This got me: you need dbus_enable in the rc.conf  (for global, this I 
have observed for a long time), but you apparently need it _per session_ 
as well.

dbus and hal work together at the system level to facilitate device 
addition and removal notification; dbus at the session level provides 
notification between the apps and the system notifications (redundant 
given FreeBSDs already in place notification systems).

This how the file managers add new devices and filesystems to the 
"place" listings. To do this you need to have a dbus session running per 
user, and a few more convoluted processes to ensure each app uses it.

So you use the addition to the xsession script posted, console-kit 
(possibly), and dbus-launch for every app. Fun... <groan>

As to whether all this applies in your particular case... but 
essentially this how it is used. HIH

More information about the freebsd-questions mailing list