Hey folks—thanks for checking out Mailspring! The Linux version actually hasn't been released yet ( where did you find a download link? I hope I didn't leave it turned on...)

It should be ready in the next few days—I had to change the way the C++ mailsync codebase is compiled to link against linux dependencies in a more portable way. Stay tuned!

from mailspring.

It looks like install script does not download and extract sync binary. You can download it manually from:
https://mailspring-builds.s3.amazonaws.com/client/01295136/linux/mailsync.tar.gz
and extract its content to /usr/share/mailspring/resources/app.asar.unpacked

from mailspring.

I found the news + link here: http://www.omgubuntu.co.uk/2017/10/mailspring-nylas-fork-released

from mailspring.

Ahh haha excellent - thanks for letting me know! Guess there are pros and cons to descriptive error messages ;-)

from mailspring.

Hey folks the lsb_release error should be fixed in 1.0.3 and I've improved the error message to mention the .tar.gz file if you get an ENOENT. (f780877). Will close this when the next version ships.

from mailspring.

It may come from installation errors:

Setting up mailspring (1.0.0) ...
Usage: lsb_release [options]

lsb_release: error: no such option: -u
Usage: lsb_release [options]

lsb_release: error: no such option: -u
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-1) ...

from mailspring.

Same on elementaryOS Loki (Ubuntu 16.04)
Is there ANY distribution in which it works?

from mailspring.

Same on KDE Neon (Ubuntu 16.04)

Proper verbose output would be nice (the log file is quite scarce)

from mailspring.

I am also getting the same issue on Windows 10.

from mailspring.

Yep, exactly the same here. If you need more details let me know. Can provide anything needed.

from mailspring.

Same for me on Ubuntu 17.10. And i also have lsb_release error.

from mailspring.

It does not seem to be linked to the lsb_release error. I added the -u option to /usr/bin/lsb_release (doing the same thing that -a), purged Mailspring and reinstalled it without the error. But still does not work.

from mailspring.

Same error here.

from mailspring.

This also happens with ubuntu 14.04

from mailspring.

Same happens on Fedora 26, installation goes without errors.

from mailspring.

Same error here.

from mailspring.

+1

from mailspring.

Same here on Ubuntu 17.04 (Gnome)

from mailspring.

Tried the dev mode (-d) but results are the same.

Logs does not give any information on the error :

{"host":"xxxxxx","timestamp":"2017-10-04T15:20:45.859Z","payload":"App load time: 376ms\n"}
/tmp/Nylas-Mail-15145.log (END)

from mailspring.

I get the same error message

from mailspring.

Ubuntu 16.04 gnome - same issue.

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

from mailspring.

@bengotow i detailed how i found the download link in the comments of issue #11

from mailspring.

@bengotow Here, the 1.0.1 deb version is working perfectly in my Ubuntu 16.04. Can I inform it to the OmgUbuntu author?

from mailspring.

@bengotow weird, 1.0.0 deb version it's working fine for me on Ubuntu 14.04.

from mailspring.

with @cobisimo's comment I was able to get v1.0 to run on my machine. I have no upgraded to the v1.0.1 deb package. I am able to sign in to my gmail account. (But i'm unable to connect any of my Exchange accounts.)

from mailspring.

When installing from scratch, the error seems to happen because the app/mailsync.tar.gz file is downloaded during postinstall, but not unpacked. Extracting the archive solves the spawn ENOENT issue.

from mailspring.

Ahh thanks @cynddl — we should definitely catch the error and display a better message if it's an ENOENT and you just need to unpack the mailsync archive!

from mailspring.

facing the same issue, looked into the ./scripts/postinstall.js and reconstructed the URL manually and cURLed it with:

curl -vv -sSLo ./app/mailsync.tar.gz "https://mailspring-builds.s3.amazonaws.com/client/1.2.1-7e7447b6/linux/mailsync.tar.gz"

it came back with a 403 forbidden which i suppose is the reason the npm i command fails :/ the link which @cobisimo provided also returns an AccessDenied from s3

from mailspring.