Comment # 50 on bug 950569 from Neil Rickert

Responding to Marcus c#48

This bug really is fixed, though with some residual problems.

Take a look at the output from the command:
     ls -lL /usr/lib64/efi/shim.efi
If that shows a file date of Dec 14 (give or take a day), then you have the
fixed shim on your system.  As a further check, you could try:
     md5sum /usr/lib64/efi/shim.efi
I get a checksum of "22462d4a946d9233ef6115dfcb31320b" on that file.

If you get the same checksum, then you have the fixed shim.efi.  I just
retested within the last 30 minutes, on the machine where I originally found
(and reported) this bug.

But they made a mistake (see c#47).  They failed to install that new shim after
the update.

If you have the fixed shim, then (as root) you can either run:

     shim-install

or

     cp /usr/lib64/efi/shim.efi /boot/efi/EFI/opensuse/.

Either of those should fix your boot problem (assuming that you have the fixed
shim.efi on your system).

There's another bug that affects booting Windows, but does not affect booting
opensuse.  That's bug 954126 and we have not yet received an update to fix that
bug (though they do have a fix that is being prepared to send out).  Hopefully,
they will run "shim-install" with that update.