-
Notifications
You must be signed in to change notification settings - Fork 14
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
Manjaro Linux: Libsecret not recognized #43
Comments
Hmm, thanks for the report! I'll see if I can boot up my Manjaro computer later today, but I don't think I've run into this issue. Do you have gnome-keyring installed? It is marked as an optional dependency, but it's possible that it's currently required by the Linux package. |
Thanks for your reply. My Manjaro uses kdewallet (as I have KDE installed) to manage keys AFAIK. Installing yet another key manager just to have one app working isn't very user friendly in my book. Shouldn't this be abstracted so that it doesn't require any specific key manager? |
I agree completely! Just wanted to be sure that was the issue. |
Thank you. It is indeed a sloppy implementation on their side. I'll give this gladly a go as soon as this is fixed. |
Okay I've done a lot more reading on this. I'm not sure where to go from here. I have every desire to get this working without requiring gnome-keyring, but I don't know if this project would have the bandwidth to do so. KDE never finished replacing KWallet with a Secret Service API-compatible solution, which leaves us without any secure options. As far as I can see, node-keytar --> libsecret --> a keyring is the standard for secrets management in node now. If KDE ever finishes KSecretService, then everything will work properly. I personally don't have the expertise to write something which will interact with the KWallet dbus as a fallback. If anyone knows of a library like Python's keyring which supports macOS Keychain, the Secret Service API, Windows Credential Locker, and KWallet, let me know! |
On Manjaro KDE I fixed it installing gnome-keyring and it work good :) |
I have gnome-keyring installed and I still get this error. It was working previously on this system but I needed to reinstall the app. Also on Arch linux and installed via the AUR. |
you can also use KeePassXC |
I tried installing KeePassXC but that didn't solve the problem either. I am happy to install gnome-keyring if that is what is required but at the moment I have that installed along with libsecret and I still get an error saying they need to be installed. Any ideas what is going on? |
I also had problem with libsecret. Installing gnome-keyring is not enough. You need to make sure that keyring-daemon is running. Please read the wiki for this matter. I used the PAM method and Mailspring is now working good for me. |
I found in the end doing what is found Foundry376#511 (comment) was enough to get it working for me. I was going down the |
Im facing the same issue. And still cant find a fix. |
@flazz01 are you aware that the original project which this is forked from is now fully open source and doesn't require an ID to use? It might be worth trying that one out to see if you still have the same issue or not. |
@JoshuaCrewe This issue also occurs when using Mailspring 1.9.2-1 (not Libre) on Manjaro. |
Describe the bug
Fresh install from AUR. Upon first launch, an error message appears. User can only quit the app. See error in screenshot.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Working state.
Screenshots
Setup: (please complete the following information):
The text was updated successfully, but these errors were encountered: