Comment # 5 on bug 1092000 from Kukuh Syafaat

* The opensuse-secureboot original one when error happened was

Boot0015* opensuse-secureboot   
HD(1,GPT,b4729dfe-7dfe-439e-867c-715f77a69a1f,0x800,0x31801)/File(\EFI\opensuse\shim.efi)

* Then i tried to make another boot with opensuse-alt

Boot0016* openSUSE-alt   
HD(1,GPT,b4729dfe-7dfe-439e-867c-715f77a69a1f,0x800,0x31801)/File(\EFI\opensuse\grubx64.efi)

* The rest of all below was created because i tried to reinstall tumbleweed,
leap 15.0 beta and leap 42.3 with formatted whole disk and created new
partition

Boot0017* opensuse-secureboot   
HD(1,GPT,87b755f6-2333-4805-b15c-da561cc06948,0x800,0x32000)/File(\EFI\opensuse\shim.efi)
Boot0018* opensuse-secureboot   
HD(1,GPT,9ae5bbd1-b55f-40d5-a536-d67efbd3ca14,0x800,0xfa000)/File(\EFI\opensuse\shim.efi)
Boot0019* opensuse-secureboot   
HD(1,GPT,17230b2b-7144-484e-888d-00f397062559,0x800,0xfa000)/File(\EFI\opensuse\shim.efi)
Boot001A* opensuse-secureboot   
HD(1,GPT,17230b2b-7144-484e-888d-00f397062559,0x800,0xfa000)/File(\EFI\opensuse\shim.efi)

> For shim 0.9, fallback.efi will try to load the "restored" boot entry first. But shim 14 changes the behavior and resets the system directly. It should be fine since the boot entry is created, and the firmware should follow it to load shim.efi.

I believe it's a shim problem with spesific hardware, for this case, ThinkPad
X1 carbon 2015. But i can't reproduce this error again because i still use my
computer for dailiy use.