Bug#1077271: systemd broken after 256.4-2 upgrade

[Richard B]

Thank you for pointing that out, Luca.  I couldn't uncover anything that 
was blocking namespaces, and decided to pursue a hard shutdown and 
system restore.  The restore wasn't needed, though, since my system 
booted normally after being powered back on.  I don't experience any of 
the systemd issues that I ran into at the start of this report and can't 
seem to recreate them, so this issue can likely be closed.

If it helps anyone else, searching for the protocol error line returned 
many results about services being denied by apparmor and conflicts 
created by unusual mount points for /tmp.  My system had /tmp mounted in 
a standard way, and no apparmor denials were logged at any point of the 
day.  I'm not sure what caused my problem, but others who run into this 
may save some time by checking apparmor and their configurations for /tmp

Thanks again.

Richard.


On 7/27/24 13:26, Luca Boccassi wrote:
> Control: severity -1 minor
> Control: tags -1 unreproducible moreinfo
>
> On Sat, 27 Jul 2024 18:16:36 +0000 Richard B <rb-misc at posteo.net> wrote:
>> Jul 27 11:41:44 fw13 systemd[1]: Failed to fork off sandboxing environment for executing generators: Protocol error
>> Jul 27 11:41:45 fw13 systemd[1]: Freezing execution.
> Something on your system is blocking namespaces, you will need to
> figure out what it is and why
>