From: MikeE@ster.invalid   
      
   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 :-)   
      
   --   
   Mike Easter   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)