On Wednesday 28 August 2013 at 16:07:23, Mantas wrote:
Partial reply:
On Wed, Aug 28, 2013 at 10:15 AM, Ivan Shapovalov intelfx...@gmail.com
wrote:
With v206, that stopped working. It seems that `systemd --user` now must
be
launched
1) with PAMName=systemd-shared
[…]
3) with
On Sat, Sep 7, 2013 at 8:12 PM, Ivan Shapovalov intelfx...@gmail.com wrote:
On Wednesday 28 August 2013 at 16:07:23, Mantas wrote:
Partial reply:
On Wed, Aug 28, 2013 at 10:15 AM, Ivan Shapovalov intelfx...@gmail.com
wrote:
With v206, that stopped working. It seems that `systemd --user` now
Hello!
With systemd v204 and earlier, I used `systemd --user` to manage my complete
session, including X server (via xorg-launch-helper) and all related things.
I used a slightly modified user-session@.service unit to start the
`systemd --user` instance in its own session to get PolicyKit
Partial reply:
On Wed, Aug 28, 2013 at 10:15 AM, Ivan Shapovalov intelfx...@gmail.com wrote:
With v206, that stopped working. It seems that `systemd --user` now must be
launched
1) with PAMName=systemd-shared
[…]
3) with /etc/pam.d/systemd-shared symlinked to system-login or whatever
