When I try to enter my password it doesnt work. Please help
First, welcome to the KDE Discuss Forum.
You should always invoke the KWallet setup after setting up a new user –
- System Settings → Personalization → KDE Wallet –
Assuming that, a default Wallet named “kdewallet” has been created, press the button located bottom left – “Launch Wallet Manager”.
Once the Wallet Manager has started, press the button located top right – “Change Password…”
For the Wallet to be automatically opened when you login, the Wallet’s password has to be the same as your login password.
Full documentation is here – <KWallet Handbook>
- It seems that, the KWallet documentation hasn’t yet been updated for KDE Plasma 6 but, I suspect that nothing much has changed from the KDE Plasma 5 behaviour …
And in addition, not sure if the documentation mentions it because I stepped in that trap once, that “kdewallet” has to use “classic blowfish encryption” with “GPG encryption, for better security” auto login will not work.
If you have recently changed your password (at the command line or any other tool than the KDE User setting itself) you can try your old password. If not, i would guess you are out of luck, you have to delete that wallet (and its contends) and create it new from scratch. Following Franken14679 description.
It’s not in the KDE documentation – it’s here – <ArchWiki - KDE Wallet>
1 Like
Problem Overview
In KDE environments on Linux, Google Chrome attempts to use KDE’s KWallet for password storage by default. Even if you remove KWallet and all its dependencies, Chrome may still attempt to initialize KWallet, leading to errors in the logs or prompting unexpected interactions if KWallet is reinstalled.
Why This Happens
Chrome’s integration with KDE frameworks is hard-coded to check for KWallet availability as part of its password management system. Specifically, Chrome uses a component of the KDE libraries (libsecret or kwallet) to handle secure storage when running on KDE or other desktop environments compatible with KDE libraries.
In Linux, applications often have .desktop files stored in /usr/share/applications/. These files control how applications are launched in the graphical environment. Specifically, the .desktop file for Google Chrome is typically located at:
/usr/share/applications/google-chrome.desktop
The key line in this file is the Exec line, which defines the exact command used to start Chrome. Normally, it might look like this:
Exec=/usr/bin/google-chrome-stable %U
To prevent Chrome from using KWallet, you can add --password-store=basic to the Exec command, making it look like this:
Exec=/usr/bin/google-chrome-stable --password-store=basic %U
This flag tells Chrome to use a simple local password store, bypassing KWallet.
Automation Script
Here’s a Bash script to automate this change by adding --password-store=basic to every Exec line in Chrome’s .desktop file:
#!/bin/bash
Path to Chrome’s .desktop file
CHROME_DESKTOP_FILE=“/usr/share/applications/google-chrome.desktop”
Check if the file exists
if [[ -f “$CHROME_DESKTOP_FILE” ]]; then
echo “Modifying all ‘Exec’ lines in $CHROME_DESKTOP_FILE to disable KWallet…”
Create a backup of the original file
sudo cp “$CHROME_DESKTOP_FILE” “$CHROME_DESKTOP_FILE.bak”
Modify all lines starting with ‘Exec=’ to add --password-store=basic
sudo sed -i ‘/^Exec=/ s|$| --password-store=basic|’ “$CHROME_DESKTOP_FILE”
echo “Modification complete! Google Chrome is now configured to avoid using KWallet.”
else
echo “File $CHROME_DESKTOP_FILE not found. Make sure Google Chrome is installed.”
fi