On 30/01/15 08:30, Simon McVittie wrote:
So that the people who are happy with the complexities of the current
arrangement can remain happy, here is how I intend it to work:
* ./configure --disable-user-bus: you get a login-session-centric world
* ./configure --enable-user-bus: you get a user-se
On 03/02/15 10:16, Stef Bon wrote:
> I've never understood why the session bus is started through dbus-launch.
If we move from a per-login-session to a per-user-session bus, then it
won't be; dbus-launch will become solely for the people who run twm
under xdm or something, but who still want to ru
2015-01-30 9:30 GMT+01:00 Simon McVittie :
> In principle, a PAM module or something could ensure that we have a
> dbus-daemon per login session, even tty/ssh/cron login sessions
> (which all go through PAM). In practice, nobody has ever cared enough to
> implement this, so we're left with D-Bus au
Hi
On Fri, Jan 30, 2015 at 9:30 AM, Simon McVittie
wrote:
> [For those who are there, I'll be at the system hackfest today and at
> FOSDEM this weekend, so if you are interested in these topics, please
> talk to me about them; I'll try to summarize discussion to these lists.
> For those not there
On Mon, 02.02.15 10:22, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote:
> > plus the obvious ones set by *dm, such as DISPLAY, or by PAM. Similarly,
> > a user's ~/.xsession can set arbitrary variables - mine sets CCACHE_DIR,
> > EDITOR, MPD_HOST and XDG_CONFIG_DIRS, among others.
> >
> >
On Sat, 31.01.15 09:43, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
> Losing DBUS_SESSION_BUS_ADDRESS was part of the point of this
> thread.
BTW: DBUS_SESSION_BUS_ADDRESS we currently set on kdbus systems from
pam_systemd. That way we can be sure it is set for all the user's
sessions.
On Fri, 30.01.15 22:53, Elias Probst (m...@eliasprobst.eu) wrote:
> On 01/30/2015 09:30 AM, Simon McVittie wrote:
> > Remaining issue: environment variables
> > ==
> >
> > […]
> > As a short-term solution, I'm tempted to write that tool, but make it
> > only up
On Fri, 30.01.15 09:30, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
> user-session
>
>
> I don't think there is a standard term for this so I'm making one up.
> The XDG_RUNTIME_DIR specification says that there is at most one
> XDG_RUNTIME_DIR per uid per machine, that it
On 02/02/15 10:22, Dimitri John Ledkov wrote:
> I would like to experiment with a user-bus, potentially in a transient
> manner to have 3 buses: system, user, session busses.
I still think it's a bad idea to have both a user bus and a session bus.
Having things "on the wrong bus" is definitely an
On 30 January 2015 at 08:30, Simon McVittie
wrote:
> Remaining issue: environment variables
> ==
>
> Sadly, not all the issues have been resolved yet. The biggest is
> environment variables: on existing systems there is an expectation
> that environment variable
On 30/01/15 09:30, Simon McVittie wrote:
> user-session
>
>
> I don't think there is a standard term for this so I'm making one up.
Notes from the hackfest: A few people called these "super-sessions" when
we discussed them. I preferred user-session tbh, but if people want to
standard
On 30/01/15 22:53, Elias Probst wrote:
> IMHO, env variables are something we should get rid of in the long term.
> It might be fine for now to provide some legacy-compatibility mechanisms
> (like your not-yet-written tool), but to me environment variables are
> something straight out of the dark a
On 01/30/2015 09:30 AM, Simon McVittie wrote:
> Remaining issue: environment variables
> ==
>
> […]
> As a short-term solution, I'm tempted to write that tool, but make it
> only upload a whitelisted set of variables automatically, and say "if
> you install dbus
[For those who are there, I'll be at the system hackfest today and at
FOSDEM this weekend, so if you are interested in these topics, please
talk to me about them; I'll try to summarize discussion to these lists.
For those not there, I'll try to keep up with responses via email and
raise any interes
14 matches
Mail list logo
