No, that's completely unrelated. This here is firmwares not having enough storage space. It's not a bug in shim. Potentially it can be worked around by avoiding the mirroring of MokListX to MokListXRT, since the information is mostly pointless to mirror.
No, that's completely unrelated. This here is firmwares not having enough storage space. It's not a bug in shim. Potentially it can be worked around by avoiding the mirroring of MokListX to MokListXRT, since the information is mostly pointless to mirror.