https://bugs.kde.org/show_bug.cgi?id=498695

--- Comment #4 from scooter_icky...@simplelogin.com ---
(In reply to Nicolas Fella from comment #3)
> What seems to happen is that Chrome makes a DBus call to KWallet to open the
> wallet, see
> https://source.chromium.org/chromium/chromium/src/+/main:components/os_crypt/
> sync/kwallet_dbus.cc;l=165
> 
> The default timeout for a DBus call is 25 seconds, and Chrome uses the
> default timeout value. After that the Chrome window starts appearing. As far
> as I can tell the actual page loading still doesn't happen until I enter the
> wallet password and unlock the wallet, and after that the page with password
> loads fine.
> 
> The defaults 25 seconds being to short for the wallet unlock is a known
> thing, which is why when KDE applications use KWallet they increase the
> timeout, see
> https://invent.kde.org/frameworks/kwallet/-/blob/master/src/api/KWallet/
> kwallet.cpp#L260
> 
> However since Chrome does not use the KWallet C++ API but talks to it
> directly via DBus that doesn't apply to Chrome.
> 
> So no, the timeout is not an artificial, non-configurable delay implemented
> by KWallet, but rather the result of how the Chrome code is written. That
> means that any fix for this must happen in Chrome

Thank you. I wonder what happens with gnome-keyring? I've seen it wait wait
much more than a minute. 

Should this thread be closed?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to