Created attachment 181142 [details] Command line output of Chrome & Discord showing kwallet issue SUMMARY Google Chrome & Discord are taking up to 60 seconds to load after today's updates (10 May 2025). I think I have tracked it down to KWallet, which I have disabled and has been disabled for some time. This issue just started today. STEPS TO REPRODUCE 1. Start Chrome or Discord OBSERVED RESULT Takes up to 60 seconds to load for either application. EXPECTED RESULT Should start up immediately. SOFTWARE/OS VERSIONS KDE Neon 6.3 (10 May 2025 Updates) ADDITIONAL INFORMATION Attaching output seen when opening either Chrome or Discord from the command line.
I can confirm my issue is 100% kwallet related. I just enabled kwallet, created a new wallet & just used the blowfish setup w/ no passwords (I think that was the old school way to stop it from bothering me with Chrome back in the day). Chrome & Discord started up immediately.
Due to lack of communication with KDE Wallet, network connections with secrets (e.g., vpn connections) cannot be activated too.
I confirm, I have same issue with Chrome. Output from terminal: [2787:2787:0511/201348.597448:ERROR:dbus/object_proxy.cc:590] 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. [2787:2787:0511/201348.597482:ERROR:components/os_crypt/sync/kwallet_dbus.cc:117] Error contacting kwalletd6 (isEnabled) [2787:2787:0511/201348.597981:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files [2787:2787:0511/201348.597992:ERROR:components/os_crypt/sync/kwallet_dbus.cc:86] Error contacting klauncher to start kwalletd6 Killed
I can reproduce this problem on CachyOS after the May 10/11th 2025 update of various KDE packages with Google Chrome (official) and RobRich's Chromium AVX2 build. A workaround which was mentioned to me on the CachyOS Discord is to add a new user and to leave Kwallet as enabled. I normally disable Kwallet. If I disable Kwallet for the new user, the app starts instantly but the front page would not load and need to open a new tab to proceed. However, this trick doesn't seem to work with my old user account. The app is still slow to start up even after enabling Kwallet. I see these entries in journalctl: Mai 11 19:49:04 n5z690 kwin_wayland[181823]: QProcess: Destroyed while process ("/usr/lib/kwin_killer_helper") is still running. Mai 11 19:49:06 n5z690 google-chrome-stable[182674]: [182669:182669:0511/194906.685425:ERROR:dbus/object_proxy.cc:590] 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 > Mai 11 19:49:06 n5z690 google-chrome-stable[182674]: [182669:182669:0511/194906.685454:ERROR:components/os_crypt/sync/kwallet_dbus.cc:412] Error contacting kwalletd6 (close) Mai 11 19:49:06 n5z690 kwin_wayland[181823]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Mai 11 19:49:06 n5z690 systemd[181768]: Started app-com.google.Chrome-182669.scope. Mai 11 19:49:06 n5z690 google-chrome-stable[182674]: [182669:182669:0511/194906.777525:ERROR:content/browser/network_service_instance_impl.cc:586] Network service crashed, restarting service. Mai 11 19:49:06 n5z690 google-chrome-stable[182674]: [182669:182669:0511/194906.784312:ERROR:extensions/browser/service_worker/service_worker_task_queue.cc:197] DidStartWorkerFail edibdbjcniadpccecjdfdjjppcpchdlm: 3 Mai 11 19:49:06 n5z690 ksecretd[182626]: kf.i18n: 0 instead of 1 arguments to message "<html><head/><body><..." supplied before conversion Mai 11 19:49:06 n5z690 ksecretd[182626]: Application "xdg-desktop-portal" using kwallet without parent window! Mai 11 19:49:09 n5z690 google-chrome-stable[182674]: Created TensorFlow Lite XNNPACK delegate for CPU. Mai 11 19:49:10 n5z690 google-chrome-stable[182674]: [182669:182734:0511/194910.033978:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT Mai 11 19:49:10 n5z690 ksecretd[182626]: QWizard::field: No such field 'key' Mai 11 19:49:10 n5z690 ksecretd[182626]: Application "xdg-desktop-portal" using kwallet without parent window! Mai 11 19:49:22 n5z690 google-chrome-stable[182674]: [182669:182737:0511/194922.218291:ERROR:content/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed Mai 11 19:49:22 n5z690 systemd[181768]: app-com.google.Chrome-182669.scope: Consumed 1.345s CPU time, 187.7M memory peak. Mai 11 19:49:22 n5z690 systemd[181768]: app-google\x2dchrome@498d9bfb79c4437c9132e610c535d2c4.service: Consumed 1.439s CPU time, 278.3M memory peak. Mai 11 19:49:24 n5z690 systemd[181768]: Started Google Chrome - Web-Browser. Mai 11 19:49:24 n5z690 systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth). Mai 11 19:49:49 n5z690 google-chrome-stable[183255]: [183250:183250:0511/194949.506062:ERROR:dbus/object_proxy.cc:590] 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 > Mai 11 19:49:49 n5z690 google-chrome-stable[183255]: [183250:183250:0511/194949.506477:ERROR:components/os_crypt/sync/kwallet_dbus.cc:117] Error contacting kwalletd6 (isEnabled) Mai 11 19:49:49 n5z690 google-chrome-stable[183255]: [183250:183250:0511/194949.506897:ERROR:dbus/object_proxy.cc:590] 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 Mai 11 19:49:49 n5z690 google-chrome-stable[183255]: [183250:183250:0511/194949.506912:ERROR:components/os_crypt/sync/kwallet_dbus.cc:86] Error contacting klauncher to start kwalletd6 Mai 11 19:50:13 n5z690 plasmashell[182063]: kf.windowsystem: static void KX11Extras::forceActiveWindow(WId, long int) may only be used on X11 Mai 11 19:50:14 n5z690 google-chrome-stable[183255]: [183250:183250:0511/195014.532242:ERROR:dbus/object_proxy.cc:590] 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 > Mai 11 19:50:14 n5z690 google-chrome-stable[183255]: [183250:183250:0511/195014.532268:ERROR:components/os_crypt/sync/kwallet_dbus.cc:412] Error contacting kwalletd6 (close) Mai 11 19:50:14 n5z690 kwin_wayland[181823]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Mai 11 19:50:14 n5z690 systemd[181768]: Started app-com.google.Chrome-183250.scope. Mai 11 19:50:14 n5z690 google-chrome-stable[183255]: [183250:183250:0511/195014.621555:ERROR:content/browser/network_service_instance_impl.cc:586] Network service crashed, restarting service. Mai 11 19:50:14 n5z690 google-chrome-stable[183255]: [183250:183250:0511/195014.630333:ERROR:extensions/browser/service_worker/service_worker_task_queue.cc:197] DidStartWorkerFail edibdbjcniadpccecjdfdjjppcpchdlm: 3 Mai 11 19:50:19 n5z690 google-chrome-stable[183255]: Created TensorFlow Lite XNNPACK delegate for CPU. Mai 11 19:50:19 n5z690 google-chrome-stable[183255]: [183250:183277:0511/195019.875689:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT Mai 11 19:50:44 n5z690 chrome[183250]: [183250:183274:0511/195044.550300:INFO:chrome/browser/extensions/extension_garbage_collector.cc:184] Garbage collection for extensions on file thread is complete. Mai 11 19:50:45 n5z690 google-chrome-stable[183255]: [183250:183277:0511/195045.644687:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT Mai 11 19:51:32 n5z690 google-chrome-stable[183255]: [183250:183277:0511/195132.346621:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT Mai 11 19:52:58 n5z690 google-chrome-stable[183255]: [183250:183277:0511/195258.552543:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT Mai 11 19:54:55 n5z690 google-chrome-stable[183255]: [183303:183303:0511/195455.762247:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 1 times! Mai 11 19:55:03 n5z690 google-chrome-stable[183255]: [183250:183250:0511/195503.920681:ERROR:mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:725] Message 1 rejected by interface blink.mojom.WidgetHost Mai 11 19:55:07 n5z690 google-chrome-stable[183255]: [183303:183303:0511/195507.922827:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 2 times! Mai 11 19:55:13 n5z690 google-chrome-stable[183255]: [183303:183303:0511/195513.312124:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 3 times!
I can't confirm with Chromium on Arch KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 If Chromium/Chromium-based browsers need kwallet to work and someone disables kwallet, why should it be a KDE problem.
(In reply to bugsie from comment #5) > If Chromium/Chromium-based browsers need kwallet to work and someone > disables kwallet, why should it be a KDE problem. Why should these browsers need kwallet to work? They did not need it to work before the KF 6.14.0 update. And there are many people that don't want to use it as they prefer ease-of-use. By the way, the mentioned workaround now seems to work with my old user profile, but I had to chose a method and enter a password. Just enabling Kwallet and ignoring it isn't enough.
Same problem with Chromium, Vivaldi browser and Discord on my Arch Linux after update to frameworks 6.14. Vivaldi is literally unusable, it gets stuck in its splash screen forever. kwallet is permanently disabled on my system, and enabling it does not solve the problem here. Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Graphics Platform: Wayland
Please have a look at this thread on the Arch Linux forums: https://bbs.archlinux.org/viewtopic.php?id=305540 Same issue on Arch Linux after a full system update today. Chromium didn't start after updating kwallet to 6.14.0, despite kwallet being disabled in the KCM. Launching Chromium with the `--password-store=basic` launch option however worked. Enabling kwallet and rebooting also worked, though restarting Plasma alone without a reboot didn't (which I guess was probably related to kwallet DBus changes and not restarting the `dbus.service` too, but I'm not sure). Disabling kwallet again after the reboot also worked, meaning Chromium launched just fine, but it had messed with the profile data, because Chromium had switched to kwallet after enabling it. For some reason, the `--password-store=basic` launch argument resolved that, despite kwallet being disabled again. A bit annoying, but I can live with that... > Why should these browsers need kwallet to work? As shown in the linked thread, Chromium always queries the kwallet DBus interfaces in order to check whether kwallet is enabled. If it's not, or if the user has set `--password-store=basic`, then it uses the "basic" password store implementation ("password store" affects all sensitive user data, like cookies, etc.). - https://github.com/chromium/chromium/blob/136.0.7103.92/components/os_crypt/sync/key_storage_kwallet.cc#L58-L71 - https://github.com/chromium/chromium/blob/136.0.7103.92/components/os_crypt/sync/kwallet_dbus.cc#L109 So my guess is that updating kwallet to 6.14.0 requires a reboot (or `dbus.service` restart), otherwise its initial query gets stuck and times out after the default timeout value it uses (which may be quite long). Btw, my kwallet KCM froze and crashed the system settings before rebooting. I couldn't generate a log from this, unfortunately.
> Disabling kwallet again after the reboot also worked, meaning Chromium launched just fine I spoke too soon. Disabling kwallet breaks all kinds of Chromium-based applications, like Electron or NW.js. I didn't check this... > Btw, my kwallet KCM froze and crashed the system settings before rebooting Re-enabling it and then opening the KCM makes it crash. So there's definitely a big issue here.
On my Arch, chromium and chromium-based apps always take several seconds to open if the kwallet is disabled in its KCM. And apparently enabling/disabling the kwallet in its KCM only takes full effect after re-login or reboot. Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Graphics Platform: Wayland On an another OS called neon unstable, that runs master branch of KDE software, I have the same results. Also, on it the profile of Vivaldi browser got corrupted due to the problem with kwallet.
I did a quick test of downgrading kwallet to v6.13 (was already in my cache anyway) that seems to resolve my issues of slow launching chromium applications. Just an FYI. Here's the journal when opening Brave-Browser with downgraded kwallet v6.13: [wtaylor@wtaylor-arch] ~ ❯ journalctl -f | grep wallet May 12 11:12:26 wtaylor-arch systemd[754]: Created slice Slice /app/dbus-:1.1-org.kde.kwalletd6. May 12 11:12:26 wtaylor-arch systemd[754]: Started dbus-:1.1-org.kde.kwalletd6@0.service. May 12 11:12:27 wtaylor-arch brave[1760]: [1760:1760:0512/111227.043406:ERROR:dbus/object_proxy.cc:590] Failed to call method:kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Remote peer disconnected May 12 11:12:27 wtaylor-arch brave[1760]: [1760:1760:0512/111227.043422:ERROR:components/os_crypt/sync/kwallet_dbus.cc:117] Error contacting kwalletd6 (isEnabled) May 12 11:12:27 wtaylor-arch brave[1760]: [1760:1760:0512/111227.043468:ERROR:components/os_crypt/sync/kwallet_dbus.cc:86] Error contacting klauncher to start kwalletd6 May 12 11:12:27 wtaylor-arch systemd[754]: Started dbus-:1.1-org.kde.kwalletd6@1.service. May 12 11:12:27 wtaylor-arch brave[1760]: [1760:1760:0512/111227.157603:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Remote peer disconnected May 12 11:12:27 wtaylor-arch brave[1760]: [1760:1760:0512/111227.157612:ERROR:components/os_crypt/sync/kwallet_dbus.cc:412] Error contacting kwalletd6 (close) May 12 11:12:33 wtaylor-arch systemd[754]: Started dbus-:1.1-org.kde.kwalletd6@2.service. May 12 11:12:33 wtaylor-arch systemd[754]: Started dbus-:1.1-org.kde.kwalletd6@3.service. Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.6-arch1-1 (64-bit) Graphics Platform: Wayland
Wes Taylor: > I did a quick test of downgrading kwallet to v6.13 (was already in my cache anyway) that seems to resolve my issues of slow launching chromium applications. Just an FYI. Thanks for the info.
Had the same issue, apps very slow to load with kdewallet disabled. Problem started with neon plasma 6.3.5 updates on 2025-05-10. After some updates yesterday situation is a bit different: Applications load normally with kde wallet enabled. When kde wallet is disabled (in system settings), applications starts, but cannot use network. Applications affected: google-chrome (deb), ungoogled chromium (flatpak), spotify, signal-desktop (probably all electron based apps). Please visit this link for more details: https://discuss.kde.org/t/problems-after-upgrading-neon-to-plasma-6-3-5/34042
(In reply to bugsie from comment #5) > If Chromium/Chromium-based browsers need kwallet to work and someone > disables kwallet, why should it be a KDE problem. Kwallet is part of KDE. Applications don't need any wallet to work, they ask a system if there is such service, and use it if it is available. Option in system settings to disable kwallet shouldn't affect ANY application.
Nice job breaking Chrome / Chromium based items. https://discuss.cachyos.org/t/chromium-browsers-takes-longer-to-open-outside-microsoft-edge-and-google-chrome/8867/4
(In reply to bugsie from comment #5) > I can't confirm with Chromium on Arch KDE Plasma Version: 6.3.5 > KDE Frameworks Version: 6.14.0 > Qt Version: 6.9.0 > > If Chromium/Chromium-based browsers need kwallet to work and someone > disables kwallet, why should it be a KDE problem. You are kidding , right? The fact that KWallet is still hooked into the browser when it's disabled is very problematic. When KWallet is disabled it should no longer have ANYTHING to do with the browsers, Discord, etc.....
I'm trying to reproduce but sofar haven't been able to. Here chromium can write/read fine from the item "Chromium keys/Chromium safe storage" which appears the only entry that gets saved, i guess being the encryption key of its own secret storage. reading various comments, i don't have exactly clear whether this happens when kwallet is actually enabled or disabled.
If i disable kwallet from the kcm, i get chromium without any saved passwords, but doesn't hang up on startup
People who have this problem, please post your kwalletrc while the problem is occurring. > The fact that KWallet is still hooked into the browser when it's disabled is very problematic. It's the other way around: the browser is asking KWallet if it's available. But after the update, it seems KWallet fails to respond when it's disabled.
Github issue for signal: https://github.com/signalapp/Signal-Desktop/issues/7327 Github issue for Brave browser: https://github.com/brave/brave-browser/issues/45983
> It's the other way around: the browser is asking KWallet if it's available. But after the update, it seems KWallet fails to respond when it's disabled. Exactly this. I have posted the relevant Chromium code parts in my previous comment, where it checks `isEnabled` on the dbus first (after detecting KDE Plasma as my DE). https://bugs.kde.org/show_bug.cgi?id=504014#c8 I have since rolled back my entire system to earlier BTRFS snapshots (both / and /home), because I don't want to deal with this major breakage that affects multiple applications. However, on KWallet 6.13.0, when it's disabled (right now on my system), there's nothing on my dbus session bus. The Chromium logs also show this. Chromium attempts to check on the session bus whether KWallet is enabled, as it has detected Plasma as my DE and thus does this by default, but it can't find the dbus interface and then switches to the "basic" password store, which is what I want (without having to force the `--password-store=basic` launch option). Here's the respective log ``` [124261:124261:0514/113826.513583:VERBOSE1:components/os_crypt/sync/key_storage_util_linux.cc:46] Password storage detected desktop environment: KDE6 [124261:124261:0514/113826.513592:VERBOSE1:components/os_crypt/sync/key_storage_linux.cc:116] Selected backend for OSCrypt: KWALLET6 [124323:124323:0514/113826.569782:WARNING:sandbox/policy/linux/sandbox_linux.cc:415] InitializeSandbox() called with multiple threads in process gpu-process. [124323:124323:0514/113826.570302:VERBOSE1:components/viz/service/main/viz_main_impl.cc:85] VizNullHypothesis is disabled (not a warning) [124261:124261:0514/113826.628698:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Remote peer disconnected [124261:124261:0514/113826.628715:ERROR:components/os_crypt/sync/kwallet_dbus.cc:117] Error contacting kwalletd6 (isEnabled) [124261:124261:0514/113826.628803:ERROR:dbus/object_proxy.cc:590] 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 [124261:124261:0514/113826.628809:ERROR:components/os_crypt/sync/kwallet_dbus.cc:86] Error contacting klauncher to start kwalletd6 [124261:124261:0514/113826.628812:WARNING:components/os_crypt/sync/key_storage_linux.cc:189] OSCrypt tried KWallet but couldn't initialise. [124261:124261:0514/113826.744174:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Remote peer disconnected [124261:124261:0514/113826.744199:ERROR:components/os_crypt/sync/kwallet_dbus.cc:412] Error contacting kwalletd6 (close) ``` > reading various comments, i don't have exactly clear whether this happens when kwallet is actually enabled or disabled. To repeat what happened after updating to 6.14.0 without enabling KWallet: Chromium simply hang. It didn't show its window and didn't respond to SIGTERM. This indicates that the dbus calls for checking KWallet hung. After enabling KWallet 6.14.0 and rebooting, Chromium worked, but re-visiting the KWallet KCM before the reboot made it crash (together with the system settings application). Enabling also caused corruption in Chromium, as the previous profile data was based on the "basic" password-store (affecting all kinds of stored sensitive data). Disabling 6.14.0 again made Chromium once again hang. And the KCM also crashed before rebooting. Enabling and disabling always required a system reboot to take effect. ---- Current kwalletrc on 6.13.0: ``` $ cat ~/.config/kwalletrc [Wallet] Close When Idle=false Close on Screensaver=false Default Wallet=kdewallet Enabled=false Idle Timeout=10 Launch Manager=false Leave Manager Open=false Leave Open=true Prompt on Open=false Use One Wallet=true ```
(In reply to michaelk83 from comment #19) > People who have this problem, please post your kwalletrc while the problem > is occurring. $ cat ~/.config/kwalletrc [Wallet] Close When Idle=false Close on Screensaver=false Default Wallet=kdewallet Enabled=false First Use=false Idle Timeout=10 Launch Manager=false Leave Manager Open=false Leave Open=true Prompt on Open=false Use One Wallet=true [org.freedesktop.secrets] apiEnabled=true
Ok, thanks for your input. It looks like the problem is in the master switch, `[Wallet] Enabled=false`. There were some changes in how it's handled as part of the refactor for 6.14 (along with some other configuration changes - that's why I asked for the kwalletrc). And I guess it broke the response behavior.
After installing the libqca-qt6-plugins package on my KDE neon system, KWallet started working again, just like it did before the 2025-05-10 updates.
See bug 504082 - kwallet is crashing. Happened to me. Confirm same problem on openSUSE Tumbleweed after latest snapshot. This has resulted in my being logged out of every browser account that uses the wallet. systemctl status --user plasma-kwallet-pam.service × plasma-kwallet-pam.service - Unlock kwallet from pam credentials Loaded: loaded (/usr/lib/systemd/user/plasma-kwallet-pam.service; static) Active: failed (Result: exit-code) since Wed 2025-05-14 13:55:34 PDT; 8min ago Duration: 8ms Invocation: 02b666d3bb0b4d28ae99d8ff3104f099 Main PID: 3118 (code=exited, status=1/FAILURE) CPU: 8ms May 14 13:55:34 localhost.localdomain systemd[2870]: Started Unlock kwallet from pam credentials. May 14 13:55:34 localhost.localdomain pam_kwallet_init[3122]: 2025/05/14 13:55:34 socat[3122] W address is opened in read-write mode but only supports read-only May 14 13:55:34 localhost.localdomain pam_kwallet_init[3122]: 2025/05/14 13:55:34 socat[3122] E connect(, AF=1 "/run/user/1000/kwallet5.socket", 32): Connection refused May 14 13:55:34 localhost.localdomain systemd[2870]: plasma-kwallet-pam.service: Main process exited, code=exited, status=1/FAILURE May 14 13:55:34 localhost.localdomain systemd[2870]: plasma-kwallet-pam.service: Failed with result 'exit-code'. Kwalletrc: [Wallet] First Use=false
I'm not able to reproduce this on Plasma 6.3.5 or git-master on Solus, nor on Neon Testing I tested this by: - Disabling KWallet through System Settings (without rebooting) - Launching Discord, DeGoogled Chromium, Vivaldi, Chrome Applications launched normally. ❯ rg Enabled ~/.config/kwalletrc 5:Enabled=false 15:apiEnabled=true Operating System: Solus 4.7 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.8.3 Kernel Version: 6.14.6-319.current (64-bit)
(In reply to Richard Steven Hack from comment #25) > See bug 504082 - kwallet is crashing. Happened to me. This is something different; please open a new bug report about it. And in that bug report, make sure to include a backtrace of the crash. Thanks!
(In reply to Efe Ciftci from comment #24) > After installing the libqca-qt6-plugins package on my KDE neon system, > KWallet started working again, just like it did before the 2025-05-10 > updates. Rich Johnson, does this fix the issue for you too?
(In reply to Nate Graham from comment #28) > (In reply to Efe Ciftci from comment #24) > > After installing the libqca-qt6-plugins package on my KDE neon system, > > KWallet started working again, just like it did before the 2025-05-10 > > updates. > Rich Johnson, does this fix the issue for you too? I was just about to come here to say it doesn't fix my issue as it is/was already installed when I experienced the issue.
(In reply to TraceyC from comment #26) > I'm not able to reproduce this on Plasma 6.3.5 or git-master on Solus, nor > on Neon Testing > I tested this by: > > - Disabling KWallet through System Settings (without rebooting) > - Launching Discord, DeGoogled Chromium, Vivaldi, Chrome How about after a reboot? That is when it all started for me was after I rebooted. Even if I were to enable kwallet right now, it would still be broken for me until I rebooted.
(In reply to Efe Ciftci from comment #24) > After installing the libqca-qt6-plugins package on my KDE neon system, > KWallet started working again, just like it did before the 2025-05-10 > updates. Have added this as a runtime dependency for kf6-kwallet and snapshot to user is now running - https://invent.kde.org/neon/kf6/kf6-kwallet/-/commit/5ce2e2ee6a22181c7d36f74f17c2f68e40402ef2
I can not confirm that installing libqca-qt6-plugins helps(even after reboot) - Slack still can start only with enabled KWallet.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kwallet/-/merge_requests/117
Git commit c9a9252d34a63bb02a3756bf5e58441a42ad5928 by Marco Martin. Committed on 15/05/2025 at 15:10. Pushed by mart into branch 'master'. Don't make clients hang if kwallet is disabled When KWallet/KSecretd is disabled, return with error from main, this makes the caller of the Dbus-activated service not stay hanged and timeout M +1 -1 src/runtime/ksecretd/main.cpp M +1 -1 src/runtime/kwalletd/main.cpp https://invent.kde.org/frameworks/kwallet/-/commit/c9a9252d34a63bb02a3756bf5e58441a42ad5928
I can confirm that the issue has been resolved. Thanks for the fix, Marco! I've forked the current version of Arch's kwallet PKGBUILD with c9a9252d34a63bb02a3756bf5e58441a42ad5928 being applied to v6.14.0, updated the system, built the PKGBUILD, installed the package and tested the changes. Chromium and anything based on it now properly falls back to the basic password store as it's supposed to, since I have kwallet disabled.
*** Bug 504271 has been marked as a duplicate of this bug. ***
*** Bug 504300 has been marked as a duplicate of this bug. ***
Is this bug also the reason why Remmina (a remote desktop app that I use) keeps asking me for password now input every time I login or am I facing a different issue? Because specifically when I downgrade kwallet-pam-6.3.5-2-x86_64.pkg.tar.zst to kwallet-pam-6.3.5-1-x86_64.pkg.tar.zst on Arch, my issue stops occurring. I also downgraded kwallet itself, and kwalletmanager, but it's really kwallet-pam which seems to make the difference.
(In reply to Eduard from comment #38) kwallet-pam is BUG 502808.
(In reply to michaelk83 from comment #39) > (In reply to Eduard from comment #38) > kwallet-pam is BUG 502808. Thanks!
Git commit bbdf7fd289ba569f878e9000e39941a49b02793a by Nicolas Fella, on behalf of Marco Martin. Committed on 16/05/2025 at 10:47. Pushed by nicolasfella into branch 'Frameworks/6.14'. Don't make clients hang if kwallet is disabled When KWallet/KSecretd is disabled, return with error from main, this makes the caller of the Dbus-activated service not stay hanged and timeout (cherry picked from commit c9a9252d34a63bb02a3756bf5e58441a42ad5928) M +1 -1 src/runtime/ksecretd/main.cpp M +1 -1 src/runtime/kwalletd/main.cpp https://invent.kde.org/frameworks/kwallet/-/commit/bbdf7fd289ba569f878e9000e39941a49b02793a
SUSE patch already there: https://build.opensuse.org/projects/KDE:Frameworks/packages/kf6-kwallet/files/0001-Don-t-make-clients-hang-if-kwallet-is-disabled.patch?expand=1 Hope it will be accepted fast.
Yep, these packages for SUSE fix the issue: https://build.opensuse.org/projects/KDE:Frameworks/packages/kf6-kwallet/repositories/openSUSE_Tumbleweed/binaries
*** Bug 504336 has been marked as a duplicate of this bug. ***
*** Bug 504334 has been marked as a duplicate of this bug. ***
On ubuntu/neon kf6-kwallet (6.14.0-0zneon+24.04+noble+release+build33) finally fixes this. Now, aplications work normally with wallet disabled. Although, it was not "inexpensive" fix - after updating and disabling kwallet, signal-desktop reported corrupted data and i had to re-link my device :/
Created attachment 181457 [details] screenshot of Vivaldi when kwallet is disabled I installed kwallet 6.14.1-1 on Arch Linux a few hours ago. If I disable kwallet in its KCM, Chromium opens without any delay, but it does not load any url until reboot. And after reboot with kwallet disabled, Vivaldi browser does not open as expected with my current profile; I get the window seen in the attached screenshot instead. Operating System: Arch Linux KDE Plasma Version: 6.3.90 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Graphics Platform: Wayland
(In reply to Patrick Silva from comment #47) > I installed kwallet 6.14.1-1 on Arch Linux a few hours ago. If I disable > kwallet in its KCM, Chromium opens without any delay, but it does not load > any url until reboot. And after reboot with kwallet disabled, Vivaldi > browser does not open as expected with my current profile; I get the window > seen in the attached screenshot instead. This is unlikely an issue with kwallet. You can't switch back-and-forth between different password stores in Chromium-based applications, meaning you can't disable and enable kwallet without "breaking" the data of your browser's user-data-dir. Once kwallet has been enabled, Chromium will use it and encrypt sensitive user data (not just passwords), and it will also translate old data from the unencrypted "basic" password store that was used when kwallet was disabled. However, when disabling kwallet again after it had been enabled, Chromium won't be able to read sensitive user data anymore, as it has been encrypted, resulting in a broken profile. Either keep kwallet enabled or create a new user-data-dir. - https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux/password_storage.md - https://wiki.archlinux.org/title/Chromium#Force_a_password_store - https://wiki.archlinux.org/title/Chromium#Launch_a_new_browser_instance This back-and-forth was the reason why I reverted to older BTRFS system+home snapshots until this issue got resolved, because it had messed with my Chromium browser/application profiles while I was figuring out the cause of the issue.
(In reply to Patrick Silva from comment #47) > Created attachment 181457 [details] > I installed kwallet 6.14.1-1 on Arch Linux a few hours ago. If I disable > kwallet in its KCM, Chromium opens without any delay, but it does not load > any url until reboot. I had a similar issue with Chromium for some reason a while ago - it opened a blank page on every URL - fixed by pressing F5 (reloading the page). Then the issue went away. So it was not related to kwallet.
(In reply to bastimeyer123 from comment #48) > (In reply to Patrick Silva from comment #47) > > I installed kwallet 6.14.1-1 on Arch Linux a few hours ago. If I disable > > kwallet in its KCM, Chromium opens without any delay, but it does not load > > any url until reboot. And after reboot with kwallet disabled, Vivaldi > > browser does not open as expected with my current profile; I get the window > > seen in the attached screenshot instead. > > This is unlikely an issue with kwallet. > > You can't switch back-and-forth between different password stores in > Chromium-based applications, meaning you can't disable and enable kwallet > without "breaking" the data of your browser's user-data-dir. Once kwallet > has been enabled, Chromium will use it and encrypt sensitive user data (not > just passwords), and it will also translate old data from the unencrypted > "basic" password store that was used when kwallet was disabled. However, > when disabling kwallet again after it had been enabled, Chromium won't be > able to read sensitive user data anymore, as it has been encrypted, > resulting in a broken profile. Either keep kwallet enabled or create a new > user-data-dir. > > - > https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux/ > password_storage.md > - https://wiki.archlinux.org/title/Chromium#Force_a_password_store > - https://wiki.archlinux.org/title/Chromium#Launch_a_new_browser_instance > > This back-and-forth was the reason why I reverted to older BTRFS system+home > snapshots until this issue got resolved, because it had messed with my > Chromium browser/application profiles while I was figuring out the cause of > the issue. Thanks for your informative comment. (In reply to Aleksey Kontsevich from comment #49) > (In reply to Patrick Silva from comment #47) > > Created attachment 181457 [details] > > I installed kwallet 6.14.1-1 on Arch Linux a few hours ago. If I disable > > kwallet in its KCM, Chromium opens without any delay, but it does not load > > any url until reboot. > > I had a similar issue with Chromium for some reason a while ago - it opened > a blank page on every URL - fixed by pressing F5 (reloading the page). Then > the issue went away. So it was not related to kwallet. Even creating a new tab and entering a url does not work. Unfortunately I need to keep kwallet enabled or use the browsers with a new profile.