@mntmn@mastodon.social
why can't this show me which application? because this recently pops up on my empty gnome desktop after login, so i'd really like to know :D
why can't this show me which application? because this recently pops up on my empty gnome desktop after login, so i'd really like to know :D
@mntmn@mastodon.social Maybe you are being hacked ?
@mntmn@mastodon.social
Same in MacOS.
And yet we wonder why phishing works.
@mntmn@mastodon.social @kevin@mastodon.km6g.us
I mean just configure auditd to log all the processes and then parse the logs. Maybe use strace. Easy peasy!/s
@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.
@mntmn@mastodon.social This kind of thing has been going on in Linux UIs for ages and it is just the most bonkers, infuriating thing. We spend all this time telling people to be extra careful to avoid sharing passwords and phishing anything and then build and apparently tolerate dialogs that say "put in your password" with no useful information why or any way to validate any claims or anything.
I mean, what are we even doing here?
@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.
@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.
@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.
@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.
@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.
@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!
@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.
@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!
@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!
@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!