Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start
Felipe Sateler
fsateler at debian.org
Mon Aug 29 13:48:24 BST 2016
Control: tags -1 moreinfo
Control: found -1 231-5
On 28 August 2016 at 17:46, Pete Batard <pete at akeo.ie> wrote:
> On 2016.08.28 15:37, Felipe Sateler wrote:
>>
>> Could you try 231-5 from unstable?
>
>
> Oops, I mean 231-5 broke it. I'm seeing the issue back in 231-5 and not
> 231-4 as I mentioned earlier.
>
> 231-4 seemed to be okay, and it's only when I upgraded to 231-5 that the
> problem reappeared.
Hmm. Strange. I cannot reproduce on a vm with seccomp disabled. Could
you please attach a verbose log?
--
Saludos,
Felipe Sateler
More information about the Pkg-systemd-maintainers
mailing list