[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 michaelk83 changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=504656 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #50 from Patrick Silva --- (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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #49 from Aleksey Kontsevich --- (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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #48 from bastimeyer...@gmail.com --- (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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #47 from Patrick Silva --- Created attachment 181457 --> https://bugs.kde.org/attachment.cgi?id=181457&action=edit 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 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #46 from nicols --- 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 :/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #45 from michaelk83 --- *** Bug 504334 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Antonio Rojas changed: What|Removed |Added CC||muhdhatt...@gmail.com --- Comment #44 from Antonio Rojas --- *** Bug 504336 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #43 from Aleksey Kontsevich --- Yep, these packages for SUSE fix the issue: https://build.opensuse.org/projects/KDE:Frameworks/packages/kf6-kwallet/repositories/openSUSE_Tumbleweed/binaries -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #42 from Aleksey Kontsevich --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Nicolas Fella changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram |eworks/kwallet/-/commit/c9a |eworks/kwallet/-/commit/bbd |9252d34a63bb02a3756bf5e5844 |f7fd289ba569f878e9000e39941 |1a42ad5928 |a49b02793a --- Comment #41 from Nicolas Fella --- 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-1src/runtime/ksecretd/main.cpp M +1-1src/runtime/kwalletd/main.cpp https://invent.kde.org/frameworks/kwallet/-/commit/bbdf7fd289ba569f878e9000e39941a49b02793a -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Eduard changed: What|Removed |Added CC||jongedu...@hotmail.com --- Comment #38 from Eduard --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #40 from Eduard --- (In reply to michaelk83 from comment #39) > (In reply to Eduard from comment #38) > kwallet-pam is BUG 502808. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #39 from michaelk83 --- (In reply to Eduard from comment #38) kwallet-pam is BUG 502808. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Antonio Rojas changed: What|Removed |Added CC||akontsev...@gmail.com --- Comment #37 from Antonio Rojas --- *** Bug 504300 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Nate Graham changed: What|Removed |Added CC||q1253328...@163.com --- Comment #36 from Nate Graham --- *** Bug 504271 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #35 from bastimeyer...@gmail.com --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Nate Graham changed: What|Removed |Added Version Fixed In||6.15 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Marco Martin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kwallet/-/commit/c9a ||9252d34a63bb02a3756bf5e5844 ||1a42ad5928 --- Comment #34 from Marco Martin --- 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-1src/runtime/ksecretd/main.cpp M +1-1src/runtime/kwalletd/main.cpp https://invent.kde.org/frameworks/kwallet/-/commit/c9a9252d34a63bb02a3756bf5e58441a42ad5928 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 villene...@arcor.de changed: What|Removed |Added CC||villene...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #33 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kwallet/-/merge_requests/117 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Andrej changed: What|Removed |Added CC||urvance...@gmail.com --- Comment #32 from Andrej --- I can not confirm that installing libqca-qt6-plugins helps(even after reboot) - Slack still can start only with enabled KWallet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Carlos De Maine changed: What|Removed |Added CC||carlosd@gmail.com --- Comment #31 from Carlos De Maine --- (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 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #30 from Rich Johnson --- (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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #28 from Nate Graham --- (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? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #29 from Rich Johnson --- (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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #27 from Nate Graham --- (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! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #26 from TraceyC --- 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) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Richard Steven Hack changed: What|Removed |Added CC||richardstevenh...@gmail.com --- Comment #25 from Richard Steven Hack --- 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 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #24 from Efe Ciftci --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Nate Graham changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #23 from michaelk83 --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #22 from Patrick Silva --- (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 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #21 from bastimeyer...@gmail.com --- > 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 ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #20 from Rik Mills --- 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 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #19 from michaelk83 --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 --- Comment #18 from Marco Martin --- If i disable kwallet from the kcm, i get chromium without any saved passwords, but doesn't hang up on startup -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #17 from Marco Martin --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 m.k...@irregular.at changed: What|Removed |Added CC||m.k...@irregular.at -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 michaelk83 changed: What|Removed |Added CC||mk.mat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 Nate Graham changed: What|Removed |Added Keywords||regression CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 John Kizer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458085 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 504014] Chromium-based applications take around 60 seconds to start if KWallet is disabled
https://bugs.kde.org/show_bug.cgi?id=504014 John Kizer changed: What|Removed |Added CC||john.ki...@proton.me, ||kdelibs-b...@kde.org Summary|Chrome & Discord Slow To|Chromium-based applications |Load due to kwallet failure |take around 60 seconds to |to load |start if KWallet is ||disabled Version|unspecified |6.14.0 Product|kwalletmanager |frameworks-kwallet Component|general |general -- You are receiving this mail because: You are watching all bug changes.
