From: vallor@cultnix.org
On Sat, 17 May 2025 16:26:51 -0700, Mike Easter wrote
in :
> Mike Easter wrote:
>>
>> 'All of a sudden' (as they say when something changes) starting
>> chromium would 'take over' the system/screen with an alert
>> 'authentication required' + 'the login keyring did not get unlocked
>> when you logged into your computer' which 'of course' is based on the
>> fact that I did not login to the computer.
>
> Another data point:
> Live LM. Uninstall seahorse. Install chromium. Try to launch chromium.
> Different alert:
>
> Choose password for new keyring. An application wants to create a new
> keyring called 'default keyring'. Choose the password you want to use
> for it.
>
> Chromium is badly designed to require there being a keyring in order to
> run at all.
>
> And, even worse, if you don't WANT to make a new keyring for it, you
> cannot 'escape' the authentication demand. The system is frozen unless
> you comply with doing what it requests.
>
> It gets crazier and crazier.
I don't have chromium, but I just did a "man google-chrome" and found:
--password-store=
Set the password store to use. The default is to
automatically detect based on the desktop envi‐
ronment. basic selects the built in, unencrypted
password store. gnome selects Gnome keyring.
kwallet selects (KDE) KWallet. (Note that KWal‐
let may not work reliably outside KDE.)
So maybe try "chromium --password-store=basic"?
--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
OS: Linux 6.14.6 Release: Mint 22.1 Mem: 258G
"Do vegetarians eat animal crackers?"
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
