From: MikeE@ster.invalid   
      
   Paul wrote:   
   > On Sat, 5/17/2025 7:58 PM, Mike Easter wrote:   
   >> vallor wrote:   
   >>>   
   >>> 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"?   
   >>>   
   >> I understand the programming assumptions, even 'tho' they are (slightly)   
   mistaken.  The assumption is that every linux user is going to have a   
   user/pass at login and 'therefore' there is a default keyring; and further,   
   even IF there isn't a default    
   keyring, there *SHOULD* be so as to enable chromium's user/pass functions (if   
   enabled).   
   >>   
   >> But the fact is that it IS possible to have a linux install which does NOT   
   require a user/pass at login; well, there is an 'arbitrary' user corresponding   
   to the name given at installation.   
   >>   
   >> And, it isn't even unusual that a user would decide to NOT have chromium   
    populate user/pass automatically.   
   >>   
   >> The chromium assumptions represent 'shortsightedness' on the part of the   
   chromium dev/s.  That is a bug, not a feature :-)   
   >>   
   >   
   > On Mint, it's available as a deb   
   >   
   >     sudo apt install chromium   
   >   
   > bullwinkle@FRAZZLE:~$ cat /etc/lsb-release   
   > DISTRIB_ID=LinuxMint   
   > DISTRIB_RELEASE=22.1   
   > DISTRIB_CODENAME=xia   
   > DISTRIB_DESCRIPTION="Linux Mint 22.1 Xia"   
   > bullwinkle@FRAZZLE:~$ sudo apt install chromium   
   >   
   > $ sudo synaptic   
   > [sudo] password for bullwinkle:   
   > bullwinkle@FRAZZLE:~$ which chromium   
   > /usr/bin/chromium   
   > bullwinkle@FRAZZLE:~$ /usr/bin/chromium   
   > [2729:2729:0517/215307.618919:ERROR:chromium-136.0.7103.92/com   
   onents/dbus/xdg/request.cc:169]   
   >   Request ended (non-user cancelled).   
   >   
   > bullwinkle@FRAZZLE:~$ whoami   
   > bullwinkle   
   > bullwinkle@FRAZZLE:~$ /usr/bin/chromium  --password-store=basic   
   > bullwinkle@FRAZZLE:~$   
   >   
   > With the setting of "basic", it no longer attempts to open the keyring.   
   > As far as I know, I think this means a password would be stored in   
   > a plain text file somewhere.   
   >   
   I'm not being successful w/ changing its ongoing behavior to   
   password-store=basic.  It is possible to write that into its bash script?   
      
   The /usr/bin/chromium is a bash script.   
      
   $ /usr/bin/chromium  --password-store=basic   
      
   For me the command throws a string of same errors on my system and   
   chromium opens.   
      
   [minigbm:drv_helpers.c(364)] DRM_IOCTL_MODE_CREATE_DUMB failed (26, 13)   
      
   (same x26 times)   
      
   --   
   Mike Easter   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)