Mailspring encountered errors syncing this account - Suspect Keyring issue

Help
1

Today after launch mailspring all accounts (gmail, yandex, others) appear marked “red” in manage screen due to sync/auth fail.
Mailstpring worked properly until yesterday, I haven’t changed anything in its config, nor on my system.

  • mailspring version: 1.15.1-cb02bf10
  • system: Slackware64 GNU/Linux 15.0
  • graphic environment: X11 + dwm
  • launch command by bash script:

mailspring --password-store="gnome-libsecret"

On the red warning “Several of your accounts are having issues” I chose I “manage”. All accounts are marked red. Tried to re-connect but after a gmail account re-login to trust mailspring, an error pops up:

Mailspring could not store your password securely. For more information, visit https://communityt.getmailspring.com/t/password-managment-error/199

Here I read:

Other Desktop Environments

When using a desktop enviroment that is not Gnome or KDE based such as LXDE, ensure that you followed the steps for the Gnome Desktop Environment. Then, try running Mailspring from the terminal while forcing Mailspring to encrypt your passwords using the gnome-libsecret backend:

mailspring --password-store="gnome-libsecret"

I encountered this issues times ago, and I solved as explained, by adding --password-store="gnome-libsecret".
But now I’m using gnome-libsecret for keyring yet… I just tried to reboot my system, but with no luck…

Any suggest?
Thanks in advance

2

An update:
today after system boot, Mailspring works properly.

I don’t know why the hell it failed to sync yesterday… Any ideas would be appreciated.

3

V.1.15.1 and that stupid password error is there again and again.
I am on Arch CachyOS and have followed all the instructions related to
mailspring --password-store="gnome-libsecret" %U

including the exec line in the config file

The idea of updating does not work since there is no update in arch for this app.

Should I go to the AUR and recompile it ??? I really need help here from the developer,maybe?

thanks for any advice even if it does not resolve the issue … :people_hugging:

4

On Linux, Mailspring requires a secret service (GNOME Keyring or KWallet) to store account passwords securely. The “could not store your password securely” error means Mailspring can’t talk to that service.

A few things to try:

  1. Make sure a secret service daemon is running. On GNOME, run gnome-keyring-daemon --start in a terminal. On KDE, ensure KWallet is active.

  2. Launch Mailspring with the correct flag. If you’re using GNOME Keyring, start Mailspring with:

    mailspring --password-store="gnome-libsecret"

    If you’re using KWallet:

    mailspring --password-store="kwallet5"

    You can add this flag to your desktop launcher or .desktop file to make it permanent.

  3. Reboot — sometimes the keyring daemon isn’t fully started on login, and a reboot resolves it (as one user in this thread found).

  4. On some distros, gnome-keyring needs to be configured to auto-start with the session. Check your distro’s documentation for “unlock GNOME Keyring on login.”

If none of these work, please share your distro and desktop environment and I’ll dig deeper.