I have site down and eventually together with paride was able to create a bit of a timeline and a fix.
I have - at first - wondered as I could reproduce it in Jammy, but not in Impish
I had qemu 1:6.0+dfsg-2expubuntu1 in both, why would they behave different.
And then I found that my Impish system was running an outdated kernel.
Rebooting into the newer one revealed that 5.11.0-20 -> 5.13.0-20 has brought the incompatibility.
I have site down and eventually together with paride was able to create a bit of a timeline and a fix.
I have - at first - wondered as I could reproduce it in Jammy, but not in Impish 2expubuntu1 in both, why would they behave different.
I had qemu 1:6.0+dfsg-
And then I found that my Impish system was running an outdated kernel.
Rebooting into the newer one revealed that 5.11.0-20 -> 5.13.0-20 has brought the incompatibility.
Gladly the already identified fix (comment #6) applies fine and build in a PPA already. /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 4700
https:/
With that I was able to get things working again.
On the way we also found an even simpler testcase.
And finally I also hit the "/bin/sh: 0: cannot open a: No such file" issue, I can confirm that it seems to be the same and fixed by the same.
I'm now preparing an SRU template and merge requests for reviewing this fix.