Re: dbus-run-session output.

Thiago Macieira <[email protected]>
Newsgroups gmane.comp.freedesktop.dbus
Message-ID <4635343.Lma2oXxL4I@tjmaciei-mobl1>
Em segunda-feira, 10 de abril de 2017, às 04:37:18 PDT, Simon McVittie 
escreveu:
> > $ echo $DBUS_SESSION_BUS_ADDRESS
> > unix:path=/run/user/1000/bus
> > $ emacs
> > Activating service name='org.gnome.GConf'
> > Successfully activated service 'org.gnome.GConf'
> 
> So the issue here seems to be that the emacs launcher is second-guessing
> how dbus-launch works:
> https://build.opensuse.org/package/view_file/openSUSE:Factory/emacs/emacs.sh
> ?expand=1 and preferring to use dbus-run-session if both dbus-launch and
> dbus-run-session are available.

My guess is that it does that after getting screen-inherited invalid 
DBUS_SESSION_BUS_ADDRESS variables.

> > It seems the problem is that the session bus launched by whatever the
> > distro uses did not fill in ~/.dbus/session-bus/$MACHINEID-0.
> 
> Correct, the systemd user unit does not fill in ~/.dbus/session-bus.
> 
> I would really prefer not to keep that mechanism forever - we have already
> been asked to stop putting this "autolaunch crap" in the home directory
> <https://bugs.freedesktop.org/show_bug.cgi?id=35887>. I had hoped that
> the user-session service (which is already opt-in, so openSUSE's dbus
> maintainer should hopefully have evaluated its impact before opting in)
> was an opportunity to draw a line and get away from those historical
> oddities.

The file is the only way to get session bus information from regular scripts. I 
use them myself in an NM-launched script that changes the proxy information 
when connecting to different networks.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

_______________________________________________
dbus mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dbus
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.