-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wire can’t access your system's safe storage. #7890
Comments
Have this issue as well on Arch Linux (6.9.1-arch1-2 kernel version) |
Yes, I'm sure that it isn't just me, but rather a fundamental failure to check for dependencies, and maybe alternatives to some common methods for handling keys and such. |
I have the same issue on Ubuntu 24.04 |
Well, mine just did something different. It auto-started but this time shows me as logged in already. I selected Conversation>Start, and then it came up that I had to log in after all. It is set to auto-start every day. Nothing in my system has changed since yesterday. There is definitely inconsistent behavior in the program. |
Same using the flatpak. |
Well, this is interesting. I just followed the instructions found at https://github.com/wireapp/wire-desktop/wiki/How-to-install-Wire-for-Desktop-on-Linux on my new Debian 12. The Wire Desktop installed correctly and I was able to log in without a problem. It is interesting because I had just removed GNOME Keyring and rebooted using KeePassXC with the SecretService before installing Wire. Hmm, I wonder........ |
Wire version: Version 3.35.3348
Wire for web version:
Operating system: Debian 11 Bullseye, Xfce 4.16
Which antivirus software do you have installed:
What steps will reproduce the problem?
What is the expected result?
...
What is the actual result?
...Wire can’t access your system's safe storage.
Please provide any additional information below. Attach a screenshot if possible.
This issue appears to be a problem with the internal encryption key storage in the OS. If that is so, then Wire does not automatically utilize the existing system. Since that mechanism of security keys can be handle in any of various manners, then why is it not standardized as other programs address it? If a particular system needs to be installed and configured a particular way, then it appears that Wire is not as utilitarian as needed.
...
The text was updated successfully, but these errors were encountered: