[frameworks-kwallet] [Bug 522307] kwalletd6 spins in infinite ReadAlias("default") D-Bus loop after screen unlock from suspend, causing constant ksecretd CPU usage

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

Tomasz C. <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #14 from Tomasz C. <[email protected]> ---
Same ReadAlias("default") loop here, paired with secret_item_create_sync(), and
I found a trigger that may be worth ruling out: a concurrently running
gnome-keyring-daemon owning the org.freedesktop.secrets D-Bus name.

gnome-keyring returns a Prompt object path from Unlock but never registers the
object on the bus, so kwalletd6's libsecret client waits forever for Completed
and spins. Removing gnome-keyring -- ksecretd then takes over the name --
stopped the loop and the accompanying memory growth, and it has not returned.

Full write-up with the D-Bus evidence and what did not help is in bug 522615;
I won't duplicate it here.

Quick check whether this applies to you:

    dbus-send --session --print-reply --dest=org.freedesktop.DBus \
      /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID \
      string:org.freedesktop.secrets

If the returned PID belongs to gnome-keyring-daemon rather than ksecretd, that
comment likely applies here too.

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