Bug#832713: closed by Martin Pitt (Bug#832893: fixed in systemd 231-2)

2016-08-15 Thread Rick Thomas
On Aug 14, 2016, at 11:13 PM, Michael Biebl wrote: > Rick, if you comment out MemoryDenyWriteExecute=yes in your service > files in /lib/systemd/system, is the problem gone? Yeah, that seems to make the problem go away. Rick

Bug#832713: closed by Martin Pitt (Bug#832893: fixed in systemd 231-2)

2016-08-14 Thread Michael Biebl
Am 15.08.2016 um 08:07 schrieb Michael Biebl: > Control: found -1 231-2 > > Am 15.08.2016 um 00:17 schrieb Rick Thomas: >> Sorry, it’s not fixed in 231-2… Please see attached boot log. > > Yeah, the revert was incomplete. > The service files in systemd use > MemoryDenyWriteExecute=yes > which is

Processed: Re: Bug#832713: closed by Martin Pitt (Bug#832893: fixed in systemd 231-2)

2016-08-14 Thread Debian Bug Tracking System
Processing control commands: > found -1 231-2 Bug #832713 {Done: Martin Pitt } [systemd] systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start Bug #832893 {Done: Martin Pitt } [systemd] Failed at step SECCOMP spawning systemd-networkd Marked as found in versions

Bug#832713: closed by Martin Pitt (Bug#832893: fixed in systemd 231-2)

2016-08-14 Thread Michael Biebl
Control: found -1 231-2 Am 15.08.2016 um 00:17 schrieb Rick Thomas: > Sorry, it’s not fixed in 231-2… Please see attached boot log. Yeah, the revert was incomplete. The service files in systemd use MemoryDenyWriteExecute=yes which is implemented using seccomp. So we need to revert 40652ca4791fc3

Bug#832713: closed by Martin Pitt (Bug#832893: fixed in systemd 231-2)

2016-08-14 Thread Rick Thomas
Sorry, it’s not fixed in 231-2… Please see attached boot log. Rick screenlog.xz Description: Binary data