https://bugs.kde.org/show_bug.cgi?id=520471
Bug ID: 520471
Summary: If you open KWallet kcm and for whatever reason
kwallet doesn't reply over DBus, systemsettings gets
stuck forever
Classification: Applications
Product: systemsettings
Version First 6.6.5
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_kwalletconfig5
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 192506
--> https://bugs.kde.org/attachment.cgi?id=192506&action=edit
Backtrace
DESCRIPTION
Stumbled on this while debugging another issue on a fresh Arch install. Turns
out that KWallet kcm is forced to wait KWallet to respond over DBus as if it
was a guarantee to happen, which in my case it's not, and that's how I got
systemsettings to completely froze. [Attached backtrace]
STEPS TO REPRODUCE
1. Make it so kwallet doesn't respond over DBus (in my case it's provoked by
another issue yet to find)
2. Open the KWallet kcm
OBSERVED RESULT
systemsettings ANRs
EXPECTED RESULT
Should detach the KWallet KCM loading process (waiting a DBus reply) as another
process/thread so it is not hardly tied to systemsettings' execution flow.
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window): Arch Linux
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
ADDITIONAL INFORMATION
The original issue I was trying to debug is that KWallet doesn't respond over
DBus to Chromium either:
[75045:75045:0521/070046.221417:ERROR:dbus/object_proxy.cc:572] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
[75045:75045:0521/070046.221451:ERROR:components/os_crypt/sync/kwallet_dbus.cc:113]
Error contacting kwalletd6 (isEnabled)
[75045:75045:0521/070046.221820:ERROR:dbus/object_proxy.cc:572] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name is not
activatable
[75045:75045:0521/070046.221847:ERROR:components/os_crypt/sync/kwallet_dbus.cc:82]
Error contacting klauncher to start kwalletd6
[75045:75045:0521/070111.246348:ERROR:dbus/object_proxy.cc:572] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
[75045:75045:0521/070111.246421:ERROR:components/os_crypt/sync/kwallet_dbus.cc:408]
Error contacting kwalletd6 (close)
So I went to the KCM to try doing something on that side and discovered this
another issue.
--
You are receiving this mail because:
You are watching all bug changes.
