Skip to content
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

Open
technodrome opened this issue Dec 23, 2020 · 14 comments
Open

Manjaro Linux: Libsecret not recognized #43

technodrome opened this issue Dec 23, 2020 · 14 comments
Labels
bug Something isn't working

Comments

@technodrome
Copy link

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:

  1. Install AUR package
  2. Run
  3. See error

Expected behavior
Working state.

Screenshots
image

Setup: (please complete the following information):

  • OS: Manjaro Linux
  • OS Version 5.4.80-2-MANJARO Roadmap/devlog and general discussion #1 SMP PREEMPT Sat Nov 28 09:58:18 UTC 2020 x86_64 GNU/Linux
  • Mailspring Version: ex: 1.7.8_libre1
  • libsecret installed: 0.20.4-1
@technodrome technodrome added the bug Something isn't working label Dec 23, 2020
@technodrome technodrome changed the title Manjaro LInux: Libsecret not recognized Manjaro Linux: Libsecret not recognized Dec 23, 2020
@exprez135
Copy link
Collaborator

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.

@technodrome
Copy link
Author

technodrome commented Dec 25, 2020

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?

@exprez135
Copy link
Collaborator

I agree completely! Just wanted to be sure that was the issue.
There's at least one issue upstream about this as well (Foundry376#713). I will try to look into this soon.

@technodrome
Copy link
Author

Thank you. It is indeed a sloppy implementation on their side. I'll give this gladly a go as soon as this is fixed.

@exprez135
Copy link
Collaborator

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!

@lannet2000
Copy link

lannet2000 commented Jan 5, 2021

On Manjaro KDE I fixed it installing gnome-keyring and it work good :)

@JoshuaCrewe
Copy link

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.

@wcasanova
Copy link

@JoshuaCrewe
Copy link

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?

@sandboiii
Copy link

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.

@JoshuaCrewe
Copy link

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 .xinitrc route. The additional dbus-update-activation-environment --systemd DISPLAY appeared to be required for me.

@flazz01
Copy link

flazz01 commented Aug 17, 2021

Im facing the same issue. And still cant find a fix.

@JoshuaCrewe
Copy link

@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.

@ashooner
Copy link

@JoshuaCrewe This issue also occurs when using Mailspring 1.9.2-1 (not Libre) on Manjaro.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants