You are not logged in.
I don't know the best place(s) to report this, but it was exceedingly difficult just to register at bugs.archlinux.org using the very popular (especially since lastpass changed their $$ policy) Bitwarden.
1. Go find the Flyspray confirmation code in your Spam Folder (my gmail account which almost never makes mistakes re: spam). If there is a way I should have reported this to Flyspray, I could not find it.
2. Discover through trial and error that Bitwarden's default generated password of 14 characters doesn't work on bugs.archlinux.org and there is no real explanation
2.a. Google and find a thread from 2012 that describes how bugs.archlinux.org doesn't like longer passwords (even though it only states the password must be at least 5 chars)
3. Save the password when Bitwarden asks
4. Go to attempt to login at bugs.archlinux.org, only to find that Bitwarden has saved the confirmation code as the username (Bitwarden problem or bugs.archlinux.org not playing nicely with Bitwarden?)
5. Hit Lost Password. Feel grateful that the password recovery didn't go to spam this time.
6. Login, and ignore the fact that you are actually finally logged in, even though the login/password fields remain.
Offline
My password is longer than 14 characters...
Offline
3. Save the password when Bitwarden asks
4. Go to attempt to login at bugs.archlinux.org, only to find that Bitwarden has saved the confirmation code as the username (Bitwarden problem or bugs.archlinux.org not playing nicely with Bitwarden?)
Atleast 2 other password managers exhibit similar behaviour on multiple websites.
I've made it a habit to NOT save upon confirmation and manually verify what is stored after verifying login works.
Last edited by Lone_Wolf (2021-04-26 11:45:47)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline