Thanks for the helpful and quick responses, Robert and Thorsten! I can confirm that running "zypper dup" from a "transactional-update shell" worked for me on both machines. Looking at the upgrades performed this way, I did see the "scriptlet failed" message for the "shim" and "kernel-default" packages on the machine upgrading from the 20220628 snapshot. The "kernel-default" scriptlet message did reference an issue with enrolling new keys. The machine upgrading from the 20220613 snapshot oddly only had the "shim" "scriptlet failed" message. When I was searching for the errors before, I was only looking for the word "error". Now I know to look for the "scriptlet failed, exit status 255" messages as well (or instead). Also, it is interesting that running "zypper dup" in the "transactional-update shell" environment seemed to colorize the various responses differently in my terminal window than running either "transactional-update" or "transactional-update dup". Specifically, the "scriptlet failed" messages seemed to stand out more due to their light purple color. Thinking back, it seems like "transactional-update" and "transactional-update dup" are suppressing these colors (though, I may be remembering that wrong), so the "scriptlet failed" messages didn't seem to stand out as much in my terminal window. Thanks again for the help! Paul On Sat, Sep 3, 2022 at 8:22 AM Robert Kocher wrote:

Hy there,

I do have the same problem and in my case i can affirm that shim is the problem! And since a few weeks, the kernel is additionally not updating anymore. I was not able to find the root cause, but it seems that some certificates can not be loaded in the post scripts...

Am 03.09.22 um 14:03 schrieb Thorsten Kukuk:

...

On Fri, Sep 02, Paul Graham wrote:

...

Since the last system boot core libraries or services have been updated. Reboot is suggested to ensure that your system benefits from these updates. 2022-09-02 17:21:11 Application returned with exit status 107. ERROR: zypper up on /.snapshots/27/snapshot failed with exit code 107! Use '--interactive' for manual problem resolution.

Sounds like the bootloader/"shim" bug.

So the problem with shim seems to be known?! Is there any solution for it expected?

...

...

Looking through the information written to the console, the only thing that claims to be an error is the following:

There should be another error about the bootloader, too.

...

Any suggestions on how to resolve this issue?

transactional-update shell -> zypper dup

And ignore the zypper error code. At least my PIs did happily boot afterwards.

Sorry, saw on my system that it is now the kernel which is broken, see bsc#1203087 ...

Thorsten

Thanks, Robert