Hi, I also have the same problem (Mailspring 1.12.0 on Ubuntu 20.04.3) I can solve it following this procedure: https://foundry376.zendesk.com/hc/en-us/articles/115002012491
So in practice I remove the /.config/Mailspring from the snap directory and reconnect all the accounts.
However, when I close and reopen Mailspring the problem occurs again, which is quite annoying.
Hi, same problem for me.
uname -a
Linux REDACTED 6.5.7-060507-generic #202310102154 SMP PREEMPT_DYNAMIC Tue Oct 10 22:00:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linuxlsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
snap list | grep mailspring
mailspring 1.12.0 526 latest/stable foundry376** -
Note that reverting to the previous version fixes the problem for me:
sudo snap revert mailspring --revision 523
mailspring reverted to 1.11.0
Can you please check the output of
snap connections mailspring
password-manager-service of being activated?mailspring --password-store="gnome-libsecret"
Refresh command failed for me but sudo snap refresh mailspring --revision=523 worked fine and resolved all issues
Hi,
Thank you for your reply.
The output of the command is the following:
Interface Plug Slot Notes
avahi-observe mailspring:avahi-observe :avahi-observe -
browser-support mailspring:browser-support :browser-support -
content[gnome-42-2204] mailspring:gnome-42-2204 gnome-42-2204:gnome-42-2204 -
content[gtk-3-themes] mailspring:gtk-3-themes gtk-common-themes:gtk-3-themes -
content[icon-themes] mailspring:icon-themes gtk-common-themes:icon-themes -
content[sound-themes] mailspring:sound-themes gtk-common-themes:sound-themes -
cups-control mailspring:cups-control :cups-control -
desktop mailspring:desktop :desktop -
desktop-legacy mailspring:desktop-legacy :desktop-legacy -
gsettings mailspring:gsettings :gsettings -
home mailspring:home :home -
mount-observe mailspring:mount-observe - -
network mailspring:network :network -
network-bind mailspring:network-bind :network-bind -
network-observe mailspring:network-observe :network-observe -
opengl mailspring:opengl :opengl -
password-manager-service mailspring:password-manager-service :password-manager-service -
pulseaudio mailspring:pulseaudio :pulseaudio -
removable-media mailspring:removable-media :removable-media -
screen-inhibit-control mailspring:screen-inhibit-control :screen-inhibit-control -
unity7 mailspring:unity7 :unity7 -
wayland mailspring:wayland :wayland -
x11 mailspring:x11 :x11 -
So yes, it seems that the password manager is activated.
I exit from mailspring and re-enter it but now it says that all the accounts are not synchronized (both with mailspring and mailspring --password-store="gnome-libsecret").
After this, I reverted back to 1.11 as suggested by @jerjako and now everything works fine.
PS: I just realized that the tray icon on top bar does not show up for version 1.12 while this problem is not present in the 1.11 version.
Maybe you can try the preview of the 1.13 version after the update to 1.12: [SNAP] Update to gnome extension and core22 by soumyaDghosh · Pull Request #2464 · Foundry376/Mailspring · GitHub
If this does not help, I will need to do some more debugging. Unfortunately, I won’t be able to achieve anything here before the weekend. So please keep tight until then. I will definitely let you know if I have more information/ideas on what to do.
I am running the 1.12 version on Zorin. I’m not an experienced linux user so trying to muddle my way through. I have tried to sudo snap connect… command, the password manager appears to be running but doesn’t work with the gnome-secret command. I’m not sure which package I installed, it was a long time ago. Nor do I know where to find the snap folder (if that’s how I installed it). I’d love help getting back access to my email accounts!
-sorry I see that you are a bit stuck with this, I’ll continue to monitor this thread 
Same issues. I’m using Windows. I fear I’ve lost all the emails I had before, which I still need to track. Very disappointed in how hard it is to get help.
Can confirm that it may work once but never on restart.
Also once the setup happens once, I don’t see anything stored in the host secret service, so I feel something is wrong there too.
In difference to the previous behaviour, you won’t see any stored credentials in the keyring. The keyring is only used to encrypt the mail passwords before they are stored in the config.json file in the Mailspring settings directory.
I hope that I will be able to reproduce the issue by trying the upgrade path via snap on Zorin OS, so that I can then deliver a solution.
Hello, I love mailspring, it is a shame it is having these issues.
I just wanted to drop by and let you know it isn’t working for me either, having the same error as explained in this thread.
OS: Arch linux
DE: None, just DWM
Installed by Pacman
I installed gnome-keyring, since I already had libsecret, and launched the application using the commands suggested but no errors in the terminal appeared nor any changes in the way the application behaves.
Reverting back to 1.11 is working for me too.
I hope we can get to the bottom of this and continue using this great email client.
Regards
I do see password-manager-service enabled under snap connections mailspring, but running with --password-store="gnome-libsecret" does not fix the issue. When I run with that flag, I do get some errors it looks like
❯ mailspring --password-store="gnome-libsecret"
Gtk-Message: 07:59:03.433: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
Gtk-Message: 07:59:03.433: Failed to load module "appmenu-gtk-module"
(mailspring:530636): Gtk-WARNING **: 07:59:03.467: GTK+ module /snap/mailspring/526/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Gtk-Message: 07:59:03.467: Failed to load module "canberra-gtk-module"
(mailspring:530636): Gtk-WARNING **: 07:59:03.468: GTK+ module /snap/mailspring/526/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Gtk-Message: 07:59:03.468: Failed to load module "canberra-gtk-module"
Running database migrations
App load time: 151ms
{"error":null}
libva error: vaGetDriverNames() failed with unknown libva error
[530636:1117/075903.649599:ERROR:browser_main_loop.cc(267)] GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Error: Could not call remote method 'decryptString'. Check that the method signature is correct. Underlying error: Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.Underlying stack: Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.
at /snap/mailspring/526/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/main/server.js:465:71
at IpcMainImpl.<anonymous> (/snap/mailspring/526/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/main/server.js:323:27)
at IpcMainImpl.emit (node:events:390:28)
at IpcMainImpl.emit (node:domain:475:12)
at EventEmitter.<anonymous> (node:electron/js2c/browser_init:161:10935)
at EventEmitter.emit (node:events:390:28)
at EventEmitter.emit (node:domain:475:12)
at /snap/mailspring/526/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/main/server.js:468:25
at IpcMainImpl.<anonymous> (/snap/mailspring/526/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/main/server.js:323:27)
at IpcMainImpl.emit (node:events:390:28)
at IpcMainImpl.emit (node:domain:475:12)
at EventEmitter.<anonymous> (node:electron/js2c/browser_init:161:10935)
at EventEmitter.emit (node:events:390:28)
at EventEmitter.emit (node:domain:475:12) {
message: "Recovered Error: Could not call remote method 'decryptString'. Check that the method signature is correct. Underlying error: Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.Underlying stack: Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.\n" +
' at /snap/mailspring/526/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/main/server.js:465:71\n' +
' at IpcMainImpl.<anonymous> (/snap/mailspring/526/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/main/server.js:323:27)\n' +
' at IpcMainImpl.emit (node:events:390:28)\n' +
' at IpcMainImpl.emit (node:domain:475:12)\n' +
' at EventEmitter.<anonymous> (node:electron/js2c/browser_init:161:10935)\n' +
' at EventEmitter.emit (node:events:390:28)\n' +
' at EventEmitter.emit (node:domain:475:12)\n'
} { pluginIds: [] }
(node:530636) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
(Use `mailspring --trace-deprecation ...` to show where the warning was created)
Raven: 429 - undefined
❯ mailspring --version
1.12.0-390a301d
❯ uname -a
Linux pop-os 6.5.6-76060506-generic #202310061235~1697396945~22.04~9283e32 SMP PREEMPT_DYNAMIC Sun O x86_64 x86_64 x86_64 GNU/Linux
I’m also experiencing this, but I noticed something unfortunate with the provided snap workaround. When I do sudo snap refresh mailspring --revision=523 it works great, but then snap goes ahead and auto-updates the package again a few hours later. Does anyone have any recommendations about what I can do about this?
edit: I think I found the solution, I seem to be able to do this: sudo snap refresh --hold=forever mailspring which tells me General refreshes of "mailspring" held indefinitely so hopefully this will stop the auto-updates.
I managed to reproduce the error in a virtual machine running Pop OK. I still can’t get my head around why on a first start of Mailspring, the snap application can connect to the host keyring for encryption but not on further restarts. I will start debugging this issue and hope to come up with a solution that works quickly.
@ipkpjersi @jwoertink @3v1n0 @sdanckert1 @lostinafro @XZillA @jerjako @DawoodMorris
Did anyone of you try to completely uninstall Mailspring (deleting all its configuration), rebooting the machine and then installing Mailspring version 1.12 via snap freshly? I don’t understand why, but this seems to have resolved the issue for me on my test system.
sudo snap remove mailspring
sudo snap install mailspring
This all still looks quite random to me, so any further information (especially if it works sometimes and othertimes not) are really helpful.
I also have no issues with the .deb version of Mailspring, so if you need a workaround while we are trying to resolve the issue in the snap, that might be something. You can try copying over your config.json file from the snap to your .deb installation to keep your account setup.
cp ~/snap/Mailspring/common/config.json ~/.config/Mailspring/config.json
As for me, downloading and installing the .deb file fixes the problem.
I did this and so far all is good.
I had the same problem as other users with version 1.12.0. My OS is Ubuntu 22.04 and I installed the app with snap. So as you suggested, I removed the version with snap but installed the version with the .deb package and it’s working.
I have the feeling that there is some kind of strange race condition in the setup. I was repeatedly able to open mailspring correctly with some instances where I could not open it at all on Zorin OS which looks similar to the issues on Pop OS, getting the error
Error: Could not call remote method 'decryptString'. Check that the method signature is correct. Underlying error: Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.Underlying stack: Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.
I tried fixing this using the suggestion as of [SNAP] Update to gnome extension and core22 by soumyaDghosh · Pull Request #2464 · Foundry376/Mailspring · GitHub but this did not produce any positive effects.
Hey folks, thanks for reporting this - I’ve been looking into the Electron internals and I’m hoping we can get this fixed very soon. One interesting note is that the error most folks are seeing in this thread:
Error: Could not call remote method 'decryptString'. Check that the method signature is correct.
Is actually not one of the errors that is generated by the Electron safeStorage APIs (found here)
https://github.com/electron/electron/blob/2c03b8fd6be5029dce0a78849860e5f57a3b3026/shell/browser/api/electron_api_safe_storage.cc#L84
I think that you’re correct @Phylu and this is some sort of race condition of electron-remote error, and may not be related to the key storage setup on Linux.
Hey folks,
We’ve released Mailspring 1.13.0, which addresses issues with the snap build of 1.12.0. I was able to reproduce the issues reported above, where the snap was able to write your passwords but not read them after a restart, causing it to succeed on the first run and then get into an invalid + broken state after quitting + restarting.
I fixed it by copying snapcraft.yaml configuration from the chromium snap, which I observed was reading / writing from the keychain successfully. They were building libsecret into the snap explicitly, which did the trick for us as well.
If you snap refresh mailspring, you’ll get the new revision which addresses these issues. If your Mailspring install is broken, you’ll launch into a bit of a mess and I’m really sorry for the hassle. You’ll need to:
Go to Preferences > Subscription and sign in to your Mailspring identity again to enable read receipts, send later, etc. (If you were signed in previously).
Go to Preferences > Accounts and click “Reconnect” or “Re-authorize” for each account that is shown in red or having connection difficulty.
Thankfully, with this upgrade Mailspring is running on Electron 22 and the new safeStorage APIs, which gives us a clear path forward and makes it much easier to incorporate upstream security patches and updates. I appreciate everyone’s patience and I’m sorry this has been a rocky update.