Skip to content

Instantly share code, notes, and snippets.

@w3dg
Created September 13, 2025 08:47
Show Gist options
  • Select an option

  • Save w3dg/943c08ab93d37ade08428dd5f78c9bf3 to your computer and use it in GitHub Desktop.

Select an option

Save w3dg/943c08ab93d37ade08428dd5f78c9bf3 to your computer and use it in GitHub Desktop.
next steps for keyring after password reset on local root shell

root – Drop to root shell prompt

# remount as rw

mount -o remount,rw /

# change password for the user
passwd your_username

# sync to fs and reboot into new system
sync
reboot
# Update your system and initramfs, so future boots are smoother:

sudo apt update && sudo apt upgrade -y
sudo update-initramfs -u -k all


# Make GRUB easier to access next time by editing /etc/default/grub:

sudo nano /etc/default/grub

# Change these lines (or add if missing):

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=5

# Then apply changes:
sudo update-grub

Thanks for that! I have another issue now which i think is for the passwd change. I had chrome installed, and currently when i start chrome i am asked for a keyring password which was supposedly my old passwd. How can i like reset google chrome for this

Yes — that’s expected. Here’s why:

Chrome stores saved passwords, cookies, and tokens in the GNOME Keyring (even on Xubuntu, it uses gnome-keyring-daemon).

That keyring is encrypted with the password you had at the time you first logged in.

When you changed your system login password from recovery, the keyring password didn’t automatically update. So Chrome now asks for the old one, which you no longer know.


Options to fix this

  1. Reset the keyring (start fresh, Chrome loses stored passwords/sessions)

If you don’t care about saved Chrome passwords/sessions:

rm ~/.local/share/keyrings/*

Next time you open Chrome, it will ask to create a new keyring. You can just set it to the same as your current login password.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment