If gnome keyring is not unlocked, browser can't go online
Reported by
lg.pente...@gmail.com,
Jul 11
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Example URL: all Steps to reproduce the problem: 1. Open Chrome or Chromium in a Gnome-compatible desktop 2. A pop-up appears, asking to unlock the login keyring 3. Press 'cancel' (the pop-up might appear several times; keep pressing 'cancel') 4. No site is reachable 5. Launching from terminal shows error messages related to being unable to unlock the login keyring, and no further error 6. Launching the browser with --password-store=basic works: the browser can go online What is the expected behavior? The browser should be able to go online even when the keyring is unlocked. Use case: I might not want to unlock all my passwords if I know I'm not going to visit any website where I need them. What went wrong? It appears like preventing the browser from accessing the login keyring breaks its network capabilities. Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: Kali Flash Version:
,
Jul 12
I think this is a known problem (restricted bug 762758). AFAIK, the gnome keyring backend is being replaced with something much more robust which should hopefully solve the problem. See issue 571003. |
||
►
Sign in to add a comment |
||
Comment 1 by krajshree@chromium.org
, Jul 12