Yes, that’s where it started.
Did anyone who can reproduce it file a bug yet ?
Discussing the issue and finding workaround (or write tutorials to help users) might be all fine but that will not solve the cause of the issue nor will it bring it to the attention of developers who can potentially fix it …
So if someone here can reproduce it, it would be nice to open a bug, attach logs etc so the system can be fixed in way the issue does not occur anymore …
@ogra the problem is that maybe it’s not a bug at all. As I said a couple of messages ago, it’s just triggered before anything related to Ubuntu has anything to do with the computer. Once Subiquity stars running, the disk is already blocked by Bitlocker.
Well, a bug doesn’t necessarily mean there is a flaw in the code
It could mean fixes to documentation or showing a pop-up like “If you changed the boot order in your UEFI Windows might now require a bitlocker key to boot it again”, filing it to make developers or documenters aware is the first step to take though, else it will not be looked at (perhaps there is something you can do in code to prevent the whole thing, who knows…)
This new piece in the documentation talks at the end about the issues that we discussed in this thread:
Just a +1 at this point.
However, I have not been able to recover my ThinkPad at this point. I can mount the OS drive with the recovery tools (using the recovery key).
But booting hangs, I’m just getting a blank blue screen (not the BSOD).
I suspect it’s asking for the recovery key, but there isn’t any text. My other guess is that it’s hung up trying to access the TPM.
Well… just typed the recovery key in the blind on the blue screen, no dashes with enter at the end. And it booted.
This topic was automatically closed after 30 days. New replies are no longer allowed.