> Chromium … it wants a password to initiate, which I understand but refuse to comply with.
That sounds like the the keyring issue that pops up if you have your user account auto-login on machine start. If you don't let Chromium store passwords⁰¹ this can be safely disabled: see https://archive.is/G6pPH#ID15 ²
I ran into the issue when setting up a simple temporary public kiosk a short while back.
--------
[0] I don't, I prefer to keep my internet facing UAs and my credential stores a bit more separated than that. It also removes some friction from moving between browsers, when one annoys me enough to (re)try another.
[1] If you do let Chromium store passwords, then you can still do this, but not safely as per the warnings in that article.
That sounds like the the keyring issue that pops up if you have your user account auto-login on machine start. If you don't let Chromium store passwords⁰¹ this can be safely disabled: see https://archive.is/G6pPH#ID15 ²
I ran into the issue when setting up a simple temporary public kiosk a short while back.
--------
[0] I don't, I prefer to keep my internet facing UAs and my credential stores a bit more separated than that. It also removes some friction from moving between browsers, when one annoys me enough to (re)try another.
[1] If you do let Chromium store passwords, then you can still do this, but not safely as per the warnings in that article.
[2] Or https://easylinuxtipsproject.blogspot.com/p/tips-1.html#ID15 for the original, if you enjoy consent dialogues or want to be commercially internet stalked