This really shouldn’t matter since they said they’ve deleted the config folder a few times. But I guess it might be worth a try.
Only other thing I can think of is to test a new temporary desktop user to see if that works. If it does, then copy the config folder from that user to the current user and maybe things will work.
As per my first/opening post the only difference in the app image is the Shell version I have is 28.3.0
Also, I have this app for over an year. Just today decided to stop working.
From the link I posted I read about this issue happening with MS Win10 users… Bitwarden closed it on their bug report site (https://github.com/bitwarden/clients/issues/8651)
To confirm: I meant add a login user for your desktop/laptop, not for Bitwarden.
You can do it through the terminal or through the system settings for your DE/WM.
Also works fine here, …alternative use a Bitwarden Browser Plugin.
You can detach that and use it like the GUI version, as long as the native one is broken.
@Limen , It seems you may have exactly the same issue I got: look in the “app.log” file, in the bitwarden config directory. If each time the app try to sync you have this line :
[error] Unable to fetch ServerConfig: Failed to decode access token: JWT must have 3 parts
Then THIS is the official answer from Bitwarden (I received it yesterday after contacting their helpdesk):
The short version is that Bitwarden recently introduced changes in how data was stored in an operating system’s secure storage system, which varies by operating system. In certain Linux configurations, there is a bug that can lead to the behavior you are seeing. This is being actively worked on by the team at Bitwarden, and I suspect this will be addressed soon in a future update. For more information, you can follow the progress being made here in our GitHub: https://github.com/bitwarden/clients/pull/8776
In the meantime, I recommend using an alternative, such as the Bitwarden browser extension or the Bitwarden Web App (https://vault.bitwarden.com/). Apologies for any inconvenience.
I am actually accessing the vault through the web browser, until they resolve the bug.
I have this issue now. No issues in my previous EOS KDE install. But in EOS Cinnamon, I have the exact same issue as the OP. Hopefully this will be addressed by a Bitwarden update soon. Using browser extension for the time being.