From: MikeE@ster.invalid   
      
   Paul wrote:   
   > Is that an issue with your graphics subsystem ?   
      
   Not that I know of; I read some stuff about the error string, but it   
   wasn't useful to me.  Right now chromium opens OK from the menu.   
      
   Or the command:   
   $ /usr/bin/chromium   
   or just chromium   
      
   Currently I have deleted the sections of seahorse that relate to   
   chromium/chrome and chromium is configured to not offer to save user/pass.   
      
   However, I'm not confident that condition will survive/persist after   
   rebooting.  I have a feeling that seahorse will be re-populated w/   
   chrome/chromium functions.   
      
   --   
   Mike Easter   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)