I ask because I've tried them all (tyoed one finger at a time) MULTIPLE times now.
Were you having Bitlocker issues on a previous thread? Maybe I'm remembering wrong. "Another user" must be you? Could this be bitlocker trying to reassert itself? Is there a way of getting out of this like a cancel or ignore button.
1 Like
Using Brave A.I. search via Mojeek gives (Zorin 18 is a fork of Ubuntu 24.04):
" This issue on Ubuntu 24.04 is typically caused by GNOME Keyring failing to unlock automatically during login, or a keyboard layout mismatch preventing the correct passphrase from being entered during the initial boot phase.
1. GNOME Keyring Auto-Unlock Failure
In Ubuntu 24.04, a known bug prevents the login keyring from unlocking automatically if it was created under a different user context or if the session fails to pass the password to the keyring daemon.
- Manual Unlock: Open the Passwords and Keys application (seahorse), right-click the Login keyring, and select Change Password . Re-enter your current login password to ensure the keyring is synced with your user account.
- Check for Missing Keyring: If the Login keyring is missing entirely, create a new one named Login and set the unlock password to match your user login password.
2. Keyboard Layout Mismatch at Boot
If the error occurs during the initial boot prompt (before the desktop loads), the system may be using a different keyboard layout than the one used to create the encryption passphrase.
- Temporary Fix: At the boot prompt, press Esc to access the GRUB menu, edit the kernel line, and append
lang=en_US keymap=enbefore thequietoption. - Permanent Fix: Edit
/etc/default/gruband addGRUB_CMDLINE_LINUX="lang=en_US keymap=en"to theGRUB_CMDLINE_LINUX_DEFAULTline, then runsudo update-grub.
3. Thunderbolt Device Authorization (NVMe Drives)
If the encrypted drive is an NVMe SSD connected via Thunderbolt on newer Intel architectures (Alder Lake/Meteor Lake), the drive may not appear until manually authorized, causing the system to hang waiting for the password source.
- Create a script at
/etc/initramfs-tools/scripts/init-top/authorize-thunderboltto authorize the device during boot. - Ensure
MODULES=mostis set in/etc/initramfs-tools/initramfs.conf. - Run
sudo update-initramfs -uto apply changes.
4. LUKS Header or Passphrase Issues
If the above steps fail, the LUKS header may be corrupted, or the passphrase may be incorrect due to hidden characters or layout differences.
- Verify Passphrase: Ensure no caps lock is active and test the password in a text editor.
- Check Header Integrity: Use
sudo cryptsetup luksDump /dev/sdX(replace with your device) to verify the header is readable. If the header is corrupted, you may need to restore it from a backup. - BitLocker Conflict: If the drive was previously used in Windows, it may be BitLocker encrypted . Use
sudo dislocker -r -V /dev/sdX -u yourPassword -- /media/bitlockerto unlock it.
AI-generated answer. Please verify critical facts."
Does anything here just work?
I'm not sure these apply as it insists I enter a PW to lock the drive.
Anither thing that's odd is that there is no other user.
Never had a bitlocker issue. Had an issue with an encryoted header, but that's been a little while ago now
Wonder if it is an issue with keyboard selection. If special characters used in creating password and had a different language at boot time, this can cause issues. # is Shift+ 3 in en_US @ is Shift+2
It looks like the Device has an Encryption. Could You install GParted with sudo apt install gparted and then open it and check if on this Drive is a little Key Symbol? Maybe make a Screenshot and post it here.
No special characters
No special characters, but thanks for the suggestion.
