Bug#583973: problem between evince and dbus

[Josselin Mouette]

Le mercredi 27 avril 2011 à 20:52 +0400, Oleg Broytman a écrit : 
> DBUS is up and running:
> 
> $ ps aux | grep -Fi dbus
> 103       2718  0.0  0.0   2700   940 ?        Ss   Apr26   0:00 /usr/bin/dbus-daemon --system
> phd       4935  0.0  0.0   3288   476 tty2     S    Apr26   0:00 dbus-launch --autolaunch 3982994b745560194fce2e0046653e6e
> --binary-syntax --close-stderr
> phd       4936  0.0  0.0   2660   688 ?        Ss   Apr26   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

It was not launched correctly. This dbus instance was autolaunched, and
not launched through the session manager. There is obviously something
wrong with your configuration.

> Sourcing the file and exporting variables before launching evince
> does help:
> 
> $ . .dbus/session-bus/3982994b745560194fce2e0046653e6e-0
> $ export DBUS_SESSION_BUS_ADDRESS
> $ export DBUS_SESSION_BUS_PID
> $ export DBUS_SESSION_BUS_WINDOWID

Those variables should be setup by the session startup scripts.

All in all, not a bug in evince.

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'
  `-