On Mon, Jul 02, 2018 at 01:19:55PM +0200, Antoine Jacoutot wrote:
> On Mon, Jul 02, 2018 at 09:06:50AM +0100, Stuart Henderson wrote:
> > On 2018/06/28 08:47, Sebastien Marie wrote:
> > >
> > > I think last patch on firefox workarounded efficiently fork+exec
> > > problem (setting DBUS_SESSION_BUS_ADDRESS if not present). so no wrapper
> > > script should be needed.
> > >
> > > So reenabling autolaunch on dbus port is possible and should not impact
> > > firefox.
> > >
> > > On the other side, it only hides the underline problem of dbus session.
> > > If I correctly understood have dbus-launch works, When a program starts
> > > it at program level (opposite to Xsession level), the session is only
> > > "local" to the program: only this particular program will speak with
> > > this dbus daemon. And it could result on starting a dbus session per
> > > program that could need it. I have already seen several dbus deamon
> > > running because starting several firefox -no-remote.
> >
> > Even if we're going to make changes in Xsession I think we should
> > reenable autolaunch in dbus for now as there is too much hard-to-debug
> > breakage.
>
> OK, I'll re-enable it for the time being then.
>
> --
> Antoine
>
I suspect this is also behind 'emacsclient -a "" -c' not doing what I
expected recently. i.e. starting up an emacs daemon if one is not
already running.
.... Ken
No comments:
Post a Comment