Bug#897654: libpam-systemd: "Failed to create session: No such process"

On Fri, May 04, 2018 at 18:28:36 +0200, Michael Biebl wrote: > Use a drop-in config as described in the Arch wiki: > > For user sessions to work correctly, an exception needs to be added for > systemd-logind: > > /etc/systemd/system/systemd-logind.service.d/hidepid.conf containing > > [Service]

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Am 04.05.2018 um 18:24 schrieb Michael Gold: > On Fri, May 04, 2018 at 18:02:09 +0200, Michael Biebl wrote: >> I guess you have two options here: >> Either drop gid=4 from your mount flags or you add >> SupplementaryGroups=adm to systemd-logind.service > > I haven't figured out how to override

Bug#897654: libpam-systemd: "Failed to create session: No such process"

On Fri, May 04, 2018 at 18:02:09 +0200, Michael Biebl wrote: > I guess you have two options here: > Either drop gid=4 from your mount flags or you add > SupplementaryGroups=adm to systemd-logind.service I haven't figured out how to override that .service file locally yet, but I'm trying to add

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Control: forcemerge 892585 -1 Am 04.05.2018 um 17:02 schrieb Michael Biebl: > Am 03.05.2018 um 23:56 schrieb Michael Gold: >> On Thu, May 03, 2018 at 23:42:34 +0200, Michael Biebl wrote: >>> Am 03.05.2018 um 23:12 schrieb Michael Gold: Is this problem already tracked? >>> I'd say this is a

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Am 03.05.2018 um 23:56 schrieb Michael Gold: > On Thu, May 03, 2018 at 23:42:34 +0200, Michael Biebl wrote: >> Am 03.05.2018 um 23:12 schrieb Michael Gold: >>> Is this problem already tracked? >> I'd say this is a duplicate of #892585 > > Agreed. I think there should be a wishlist item

Bug#897654: libpam-systemd: "Failed to create session: No such process"

On Thu, May 03, 2018 at 23:25:05 +0200, Michael Biebl wrote: > Well, logind is running as root, but the the service file is locked down > considerably: > > CapabilityBoundingSet=CAP_SYS_ADMIN CAP_MAC_ADMIN CAP_AUDIT_CONTROL > CAP_CHOWN CAP_KILL CAP_DAC_REA > MemoryDenyWriteExecute=yes >

Bug#897654: libpam-systemd: "Failed to create session: No such process"

On Thu, May 03, 2018 at 23:42:34 +0200, Michael Biebl wrote: > Am 03.05.2018 um 23:12 schrieb Michael Gold: > > Is this problem already tracked? > I'd say this is a duplicate of #892585 Agreed. I think there should be a wishlist item requesting that the failure be more obvious. Shall I file

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Am 03.05.2018 um 23:12 schrieb Michael Gold: > retitle 897654 libpam-systemd: hidepid causes "Failed to create session: No > such process" > thanks > > On Thu, May 03, 2018 at 22:53:34 +0200, Michael Biebl wrote: >> On Thu, 3 May 2018 16:31:53 -0400 Michael Gold wrote: >>>

Bug#897654: libpam-systemd: "Failed to create session: No such process"

retitle 897654 libpam-systemd: hidepid causes "Failed to create session: No such process" thanks On Thu, May 03, 2018 at 22:53:34 +0200, Michael Biebl wrote: > On Thu, 3 May 2018 16:31:53 -0400 Michael Gold wrote: > > Apr 09 11:37:30 golbez lightdm[14767]:

Bug#897654: libpam-systemd: "Failed to create session: No such process"

On Thu, 3 May 2018 16:31:53 -0400 Michael Gold wrote: > Package: libpam-systemd > Version: 238-4 > Severity: important > > At some point in the past, I was able to shut down my system as a > non-root user: > dbus-send --system --print-reply --dest=org.freedesktop.login1 >

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Package: libpam-systemd Version: 238-4 Severity: important At some point in the past, I was able to shut down my system as a non-root user: dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 "org.freedesktop.login1.Manager.PowerOff" boolean:true But