Re: [systemd-devel] Using systemd --user to manage graphical sessions?

On Thu, May 12, 2016 at 1:28 AM, Luke Shumaker wrote: > > The only problem I have with this setup is that dunst (my desktop > notification daemon) isn't happy running multiple instances on > different displays. I think it's because it isn't happy sharing the > dbus, but I

Re: [systemd-devel] Using systemd --user to manage graphical sessions?

On Wed, 11 May 2016 12:13:45 -0400, Martin Pitt wrote: > Or is someone actually using systemd --user for graphical sessions > already and found a trick that I missed? I am! For several months now (and before that, I was still using systemd --user for graphical stuff, but not

Re: [systemd-devel] Using systemd --user to manage graphical sessions?

Hello Mantas, thanks for your reply! Mantas Mikulėnas [2016-05-11 19:54 +0300]: > AFAIK, the general idea of --user is that there's at most one graphical > session (per user) at a time, so things like $DISPLAY naturally become per > user. Right, I understand that. But that doesn't mean that

Re: [systemd-devel] Using systemd --user to manage graphical sessions?

On Wed, May 11, 2016 at 7:13 PM, Martin Pitt wrote: > Hello all, > > I've been experimenting with systemd --user as a possible replacement > for bringing up graphical user sessions. We currently bring up most of > that using upstart jobs (simple auto-restart on crashes,

[systemd-devel] Using systemd --user to manage graphical sessions?

Hello all, I've been experimenting with systemd --user as a possible replacement for bringing up graphical user sessions. We currently bring up most of that using upstart jobs (simple auto-restart on crashes, rate limiting, per-job logging, fine-grained startup condition control). There is one