Addendum: the error in the system log is:
[175109.432995] systemd[15887]: systemd-logind.service: Failed at step
SECCOMP spawning /lib/systemd/systemd-logind: File exists
cheers, Phil
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@
On Feb 2 2017, Michael Biebl wrote:
Am 02.02.2017 um 11:46 schrieb Phil Armstrong:
Package: systemd
Version: 232-15
Severity: normal
A recent update to systemd enabled SECCOMP, after which any service using
RestrictAddressFamilies, MemoryDenyWriteExecute or RestrictRealtime fails
to start
On Feb 2 2017, Michael Biebl wrote:
I guess it would be worthwile testing 232-1 from snapshot.d.o [1]
Downgrading systemd, udev, libudev1 & libsystemd0 to 232-1 doesn't help:
[190930.425521] systemd[2789]: systemd-udevd.service: Failed at step
ADDRESS_FAMILIES spawning /lib/systemd/systemd-
On 02/02/17 16:04, Phil Armstrong wrote:
On Feb 2 2017, Michael Biebl wrote:
I guess it would be worthwile testing 232-1 from snapshot.d.o [1]
Downgrading systemd, udev, libudev1 & libsystemd0 to 232-1 doesn't help:
[190930.425521] systemd[2789]: systemd-udevd.service: Faile
On 02/02/17 21:50, Michael Biebl wrote:
Am 02.02.2017 um 20:58 schrieb Phil Armstrong:
On 02/02/17 16:04, Phil Armstrong wrote:
On Feb 2 2017, Michael Biebl wrote:
I guess it would be worthwile testing 232-1 from snapshot.d.o [1]
Downgrading systemd, udev, libudev1 & libsystemd0 to 2
On 02/02/17 22:37, Phil Armstrong wrote:
On 02/02/17 21:50, Michael Biebl wrote:
Are you absolutely sure? We had another bug report who said that
downgrading systemd+udev to 232-1 did fix the problem on ppc(64).
This is a ppc32 system, so maybe that makes the difference? I’ll test
it
