Mailspring: Error 134 (SIGABRT) when connecting a Gmail account

Created on 8 Feb 2018  ·  20Comments  ·  Source: Foundry376/Mailspring

This bug is still here - https://github.com/Foundry376/Mailspring/issues/368, and it's the real block right now.

Yesterday when you released 1.1.3 my Mailspring stucks in a state "Sending message... Checking mailbox...". Few restarts get the same behavior, and I've decided to clear ~/.config/Mailspring and start from scratches.

And I got the same error when trying to login to my Gmail.
screenshot from 2018-02-08 15-01-06

Using IMAP to get access to my emails is not an option because there are no Gmail labels which are crucial for me.

So, I feel so unhappy because the new release blocked my work with no option to revert.

Most helpful comment

Same issue+1 on Mailspring 1.6.1 and ArchLinux

All 20 comments

Hey! Thanks for reporting this. I'll see if I can get to the bottom of this. Error 134 is SIGABRT, which means something pretty far down in the IMAP/SMTP library is crashing and I haven't been able to find another account this occurs with yet.

@bengotow Is this any chance to add gmail account with this bug? maybe some kind of backdoor? I'm really stuck right now :((

many thanks in advance!

Hey @DmitryLoki just wanted to let you know I spent most of this evening and yesterday working on this, and it'll be fixed in tomorrow's release. It turns out it was an issue with the sync worker being unable to open it's log file, of all things. Stay tuned—

wow! supercool!!!! thanks a lot!

PS
In case of thinking about starting donation program (additionally to pro subscription) - I'm down :)

@bengotow Nooooo =(((
1.1.4, still there
image

:(

Hm.. It seems that this bug is relevant only for Ubuntu 16.10. I've tried live-USB with Ubuntu 17.10 and it works fine. It's also fine with macOS.

So, I've solved this just logged in macOS and then just copy the whole Mailspring user's folder to my Ubuntu 16.10 and it works.

Still the same error with gmail account: An unexpected mailsync error occurred (134)
I'm using:

Mailspring-1.2.1
Linux Ubuntu 17.10

Still facing the same problem "An unexpected mailsync error occurred (134)" when connecting to Gmail.
My environment: Fedora 27, mailspring-1.2.1-7e7447b6

Hi, I have the same error on Ubuntu 16.04.
Anybody solved it?

Same here, Linux Mint 19.1 and Mailspring 1.5.6

The same issue arose for me as well, on Mailspring 1.6.1 and Ubuntu 18.10, about one week ago.

Same issue+1 on Mailspring 1.6.1 and ArchLinux

Still got the same issue on version 1.7.2-4522b259 and Kubuntu 19.10.

Same issue+1 on Mailspring 1.7.4 and deepin 15.11

got same error on fedora 32
MainSpring 1.7.6
error: mailsync:134

Same error
Mailspring 1.7.6
MacOS 10.13.6

Same error on Arch Linux
Mailspring 1.7.8

Hello, Same Error On ParrotOS
I try to Connect Gmail with Proxy , But it returns Error

# uname -a
Linux parrot 5.8.0-2parrot1-amd64 #1 SMP Debian 5.8.10-2parrot1 (2020-10-05) x86_64 GNU/Linux

mailSpring 1.7.8-13635bcf

2020-10-10_08-56

такая же херня
mailspring -v
1.7.8-13635bcf
LMDE (Linux x 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64 GNU/Linux)
Сначала норм работало, потом перестало, как пофиксить то? другие ящики работают только с гуглом проблема

Was this page helpful?
0 / 5 - 0 ratings