Skip to content

Commit de1ed4d

Browse files
authored
Another Flatpak/KDE5 wallet workaround (#7606)
1 parent cc732ce commit de1ed4d

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

docs/editor/settings-sync.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -195,6 +195,11 @@ It's possible that your wallet (aka keyring) is closed. If you open [KWalletMana
195195

196196
If you are using KDE5 or higher and are having trouble connecting to `kwallet5` (like users of the unofficial VS Code Flatpak in [issue #189672](https://github.com/microsoft/vscode/issues/189672)), you can try [configuring the keyring](#other-linux-desktop-environments) to `gnome-libsecret` as this will use the [Secret Service API](https://www.gnu.org/software/emacs/manual/html_node/auth/Secret-Service-API.html) to communicate with any valid keyring. `kwallet5` implements the Secret Service API and can be accessed using this method.
197197

198+
If you're still experiencing trouble connecting to `kwallet5`, some users have reported that granting the specific D-Bus service permissions proved a viable fix:
199+
```sh
200+
flatpak override --user --talk-name=org.kde.kwalletd5 --talk-name=org.freedesktop.secrets com.visualstudio.code
201+
```
202+
198203
#### Other Linux desktop environments
199204

200205
First off, if your desktop environment wasn't detected, you can [open an issue on VS Code](https://github.com/microsoft/vscode/issues/new/choose) with the verbose logs from above. This is important for us to support additional desktop configurations.

0 commit comments

Comments
 (0)