Kwallet blocks Bitwarden's login page

,

Hello,

Sometimes when I launch the appimage version of BitWarden, a window will pop-up saying something like this:

“An application wants to unlock the default keyring, but it is locked”

It is asking for a password. I reckon it’s from Neochat that asked the same thing, but I’ve uninstalled that matrix client a while ago.

The problem is a catch-22: I can’t get the password without login onto the password manager. I can’t click in any other window or KDE widget or panel. I can only interact with the window.

Since I can’t unlock it, I have to click “cancel” at least twice, of which it will disappear and allow me to interact with the desktop. However, BitWarden will not go to the login page and instead give a infinite loading screen.

I’ve tried restarting the application, but it remains the same. Reinstalling it doesn’t do anything.

The only workarounds is to log out and log back in or restart the PC, both are very inconvenient and sometimes I have to do several times.

I already have Kwallet disabled before I even installed Bitwarden and Neochat. As the following image shows:

I uninstalled it and the KDE settings page, but the problem still persists. Reinstalling doesn’t do anything either.

It’s odd that this happen here, but never did at my OpenSUSE Tumbleweed install.

Is there a way to remove this pop-up? Is there also a way to reset the password that I set on Neochat? Maybe that«s what it’s asking for.

From Proposed Common Issues to Ask Fedora

Have you tried installing the bitwarden browser extension. That way you can open your browser, open bitwarden and get the password.

I use the rpm version of the bitwarden desktop client and also use kwallet. I haven’t experienced the same issue.

I use the browser extension a lot.

That way you can open your browser, open bitwarden and get the password.

Yeah if I have the password on my clipboard, that might work. But if I don’t, I’m simply screwed.

Again, I can’t interact with any other window when that one pops in, not even the browser.

I use the rpm version of the bitwarden desktop client and also use kwallet. I haven’t experienced the same issue.

I might have to start using it. I’m starting to have a felling that AppImages just have problems depending on the distro. For example, PCSX2 AppImage version can’t auto update on Tumbleweed due to the certificates being in a different place or something.

That’s odd. I’m using kdewallet, and when I get the pop-ups I can open other applications. Of course, if something needs a password, it won’t work, but Firefox opens just fine and I can sign into the bitwarden extension with no issues.

As you can see, I launched spectacle to take a screen shot.

Here’s a video showcasing my issue: 7.8 MB file on MEGA

@gbcox , do you think a reinstall can possibly fix this? Or should I wait and upgrade to Fedora 40 when that comes out tomorrow? Maybe upgrading fixes the issue.

I would wait to see if the upgrade fixes this, but chances are that won’t work if it is something in a configuration file somewhere. I’d hate to advise you to reinstall, but sometimes that is faster than going on a treasure hunt trying to uncover the root cause. I did try the appimage, and it behaves for me the same way the rpm behaves.

I also noticed that if my wallet is locked, bitwarden will wait to finish the login until I unlock the wallet - but when that happens, only bitwarden is waiting - other applications work as expected.

Also, from the first photo you attached, kde wallet isn’t activated (it isn’t checked). You might decide to activate it and tie it to your login password. That way when you login, kwallet will automatically unlock. Just a thought.