Can't get past GRUB after latest update (nvm it fixed itself)

[ihavenoideawhatimdoing]

I have Tumbleweed dual-booted with Win11. I noticed in the release notes for the last snapshot that something got fixed regarding encryption on a drive with other partitions, but idk if that’s relevant.

What’s happening is I input the encryption key at boot and it just sits there blinking.

Anyways…how do I get into my system now that Opensuse has locked me out of it??

Update1: I pressed Enter and got this error:

Update2: Okay restarted again, tried again, and it’s working. I suppose I simply mistyped the key, but normally that just returns “invalid key/password”

[arvidjaar]

@ihavenoideawhatimdoing

I suppose I simply mistyped the key

No, no key data means it really attempted to unlock LUKS partition without any passphrase. So, it looks like your input was simply lost and only the second ENTER was accepted resulting in the empty line. Whether it is GRUB or hardware issue is hard to say.

[ihavenoideawhatimdoing]

How peculiar

[arvidjaar]

You may consider (openSUSE) bug report. Normally, grub should retry up to 3 times (by default) if unlocking fails due to incorrect passphrase:

          if (ret != GRUB_ERR_ACCESS_DENIED || tries == 1)
            goto error;

But if it gets empty input, it fails with the different error:

 if (cargs->key_data == NULL || cargs->key_len == 0)
    return grub_error (GRUB_ERR_BAD_ARGUMENT, "no key data");

But what it really should do in this case is retrying input. User may have pressed ENTER by accident, it happens. It is just another typo.