Thread | Brutkey

@mntmn@mastodon.social

a) journalctl -b | grep keyring may reveal the app (check exe=). sudo lsof -n | grep keyring might also help. Both not 100% reliable (maybe someone else has an idea)

b) Could also be a broken keyring. I see it when auto-unlock fails and e.g. Nextcloud asks for auth. seahorse („Passwords and Keys“) shows same behavior / unlock not possible; I fix it by resetting via seahors (or deleting ~/.local/share/keyrings/). Never debugged it in detail.

Alexa Devreux-Swift
@alexadeswift@lgbtqia.space

@bitshift@chaos.social @mntmn@mastodon.social I had an issue like this with a broken keyring. I removed and created a new keyring and all has been good since.

bitshift
@bitshift@chaos.social

@alexadeswift@lgbtqia.space @mntmn@mastodon.social

Yes, delete/reset was the only way. But it happened ~four or five times within the last three years. I was not able to detect a reason. No other corruption issues with other files, hardware errors, or such. So I think there is some kind of race condition during updating the keyring or something like that.

Alexa Devreux-Swift
@alexadeswift@lgbtqia.space

@bitshift@chaos.social @mntmn@mastodon.social it is very strange to be sure. I had this on a new clean install, and I was also using my correct password!