flathub / flathub/com.google.Chrome
KWallet Communication (KDE)
- Dominant language
- Shell
- Stars
- 67
- Forks
- 39
- Avg merge
- 6h 48m
- Merged PRs (30d)
- 7
Description
Running in KDE, Chrome is unable to communicate with the KWallet keyring.
> [2:2:0101/023234.222060:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd5 (isEnabled)
Starting chrome with `--talk-name=org.kde.\*` or with session bus access works to solve this problem.
Without this, chrome does not store credentials in the DE keyring. (Maybe it uses an internal one)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the kwallet_dbus.cc(100) error and compare Chrome's KDE behavior with the --talk-name=org.kde.* workaround described here. Determine which Flatpak permission or integration entry point controls access to kwalletd5; done means Chrome can store credentials in KDE's keyring without requiring extra launch flags.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100