Comment 116 for bug 1689825

Thanks for the feedback Stephen. This thread has become very long and it's hard to extract the relevant information, so just to make sure that I fully understand the issue:

 - can you confirm that chrom{e,ium} takes a long time to open (in the original description it was 2 minutes, is this the same for you)?

 - if so, do you eventually see a popup prompting for your password to unlock the keyring?

 - after closing it and opening again, I take it it's not blocked on the keyring, assuming you previously unlocked it?

 - can you launch chromium from a terminal with the following command, and share the output:

      chromium-browser --enable-logging=stderr

Thanks in advance!