Error with password storage

[Fumesover]

What operating system are you using?

Archlinux x86_64

What version of Mailspring are you using?

1.0.12-cf081332

Bug?

Do you have any third-party plugins installed? If so, which ones?

Nop

Is the issue related to a specific email provider (Gmail, Exchange, etc.)?

Nop

Is the issue reproducible with a particular attachment, message, signature, etc?

Hi,
When I'm trying to login to mailspring with a typical user, I can't get it to store my password
The app is giving me the folowing error :

Mailspring could not store your password securely. Make sure you have libsecret installed and a keyring is present. For more information, visit http://support.getmailspring.com/hc/en-us/articles/115001875571

But if I run it with sudo mailspring it works direcly without any error

I don't know if the error is from me or not but you may update you'r support website

Amazing app, good luck guys !

[bengotow]

Thanks for reporting this! I'll incorporate this change when we update that page in the KB.

[spcmd]

I'm getting the same error on Arch Linux (mailspring 1.1.3.27dcee2-1)

core/libsecret 0.18.5+14+g9980655-1 [installed]
extra/gnome-keyring 1:3.27.2-1 (gnome) [installed]
extra/libgnome-keyring 3.12.0-2 [installed]

I don't want to use it with sudo.

Update/Edit: I found a solution on the Arch Wiki. I'm not using a DM (using only a WM: bspwm), so I tried the xinitrc method (the i3 method exactly):

https://wiki.archlinux.org/index.php/GNOME/Keyring#xinitrc_method

This is the important part to put in the .xinitrc:

dbus-update-activation-environment --systemd DISPLAY
eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)
export SSH_AUTH_SOCK

After that the gnome-keyring asked for the password (it didn't accept my user password, only root's password.. Edit/Fix: The problem caused by using mailspring with sudo for the first time, so the gnome-keyring asked/remembered for the root's password. To fix I have to delete the keyring files in ~/.local/share/keyrings and after a logout-login the gnome-keyring asked for the new password for my user.)

[pba247]

This is a bit of a hack for linux users, but works (I'm using KDE Neon):

1. Install evolution (just temporarily). It will force you to setup the keyring.
2. Uninstall evolution.
3. Install Mailspring with no issue.

[BlueManCZ]

I solved this error by installing gnome-keyring package to system, which is also package defaultly installed with evolution, as @pba247 says. So thank you.

With apt: sudo apt install gnome-keyring

[michaelhofer]

As @BlueManCZ suggests, installing gnome-keyring does fix the issue.

It would be great if the rpm packages would include this as a dependency.

[brunofin]

I had the same problem on Kubuntu, and as @BlueManCZ suggests, installing gnome-keyring does fix the issue.

[denis-kisel]

Incredible, thanks BlueManCZ its work for lubuntu18.04(64)

[jasgagne]

@BlueManCZ Thanks a lot man! This helped me on Manjaro KDE!

[minyaen]

@BlueManCZ Thanks a lot man! This helped me on Manjaro KDE!

This worked for me as well (Manjaro KDE)

[meowsus]

I'm surprised that installing gnome-keyring didn't work for me. After receiving the following error:

Mailspring could not store your password securely. Make sure you have `libsecret` installed and a keyring is present.  For more information, visit http://support.getmailspring.com/hc/en-us/articles/115001875571

I attempted to install libsecret and gnome-keyring

$ sudo apt install libsecret-1-0 libsecret-1-dev gnome-keyring
Reading package lists... Done
Building dependency tree       
Reading state information... Done
gnome-keyring is already the newest version (3.31.91-1ubuntu1).
libsecret-1-0 is already the newest version (0.18.8-1).
libsecret-1-dev is already the newest version (0.18.8-1).
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.

But I still receive the error. I'm on Ubuntu 19.04 running Mailspring v1.6.3:

$ lsb_release -a
LSB Version:	core-10.2019031300ubuntu1-noarch:printing-10.2019031300ubuntu1-noarch:security-10.2019031300ubuntu1-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 19.04
Release:	19.04
Codename:	disco

$ mailspring -v
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
1.6.3-134a0e55

Checking the KB article linked in the error message prompts me to email support, which is what I'm doing presently.

EDIT

This was happening on a clean install when trying to log in for the first time with my existing Mailspring credentials. After hitting the Quit button supplied by the error dialog and restarting the application I was able to get in just fine.

@bengotow you may want to update that KB article to support this usecase until a fix is made.

[exapsy]

Very happy that Gnome-Keyring worked. But why? Does anyone have any idea? The message says that there just isn't a lib-secret, even though there is. So what's the issue here?

[itselijahciali]

If you're on Windows, I've found that running as administrator fixes this issue.

[romill93]

I tried running as administrator as suggested by @itselijahciali, but it did not work.
I use Mailspring on Win10 Pro 10.0.19042 Build 19042, Mailspring v. 1.8.0-8983dca2
As stated here a lot of accounts on windows might cause the issue, but I got
Mailspring could not store your password securely. For more information visit http://support.getmailspring.com/hc/en-us/articles/115001875571 which redirects me to https://foundry376.zendesk.com/hc/en-us/articles/115001875571 for adding my second account. And of course, after I click on Quit Mailspring is quitted as well.
What are the keyring requirements on Windows. Do I need to install something additionally that I am not aware of?

Would really appreciate some support - if I should provide any additional info please shout out

[CodeMouse92]

We are in the process of migrating issues (and Zendesk articles too, actually) to Discourse, which can better facilitate discussion and discovery, and so GitHub Issues can focus on issues that are confirmed and slated for resolution in the near term. Learn more about the changes here.

@romill93 The best way to get an answer to your question would be to post a new Topic on the Help section of our Discourse.