From: MikeE@ster.invalid   
      
   Az wrote:   
   > I tend to get overly paranoid when things change like starts happening   
   > that was not there before, the last upgrade or app install, etc.   
   >   
   > Have you ran any rootkit virus checks? I have at time found a few programs   
   > identified that were not present on install. Once removed all was well,   
   > afaik, Just a thought.   
      
   I was 'paranoid' - suspicious at first, but when I searched and found   
   discussions of the problem, I became somewhat reassured, but I still   
   didn't want to cooperate with the 'process'.   
      
   The 'system' is 'disabled' in that one cannot proceed further w/o   
   cooperating w/ the authentication request; it isn't as if one could just   
   'decline' to open chromium, it is more like one can't decline to   
   authenticate to login.  Nothing works, incl ctrl-alt-del.  One can   
   either authenticate to login and boot chromium or do a hard shutdown.   
      
   Ridiculous.   
      
   It is apparently all about the idea chromium has 'in its head' that the   
   login needs to be done and it hasn't been, so 'this is as far as you go,   
   pal'.  And the *reason* the login hasn't been done, according to   
   chromium, is because the keyring hasn't been opened, which may be true.   
      
   There is a chromium - keyring - login combo 'requirement' because   
   chromium wants to be able to use its keyring, even if it has been   
   configured to not provide user/pass.   
      
   --   
   Mike Easter   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)