Package Details: mailspring 1.10.5-1

Git Clone URL: https://aur.archlinux.org/mailspring.git (read-only, click to copy)
Package Base: mailspring
Description: A beautiful, fast and maintained fork of Nylas Mail by one of the original authors.
Upstream URL: https://getmailspring.com/
Keywords: email mail multiple-accounts nylas
Licenses: custom: GPL3 and (C) 2016-2019 Foundry 376, LLC.
Submitter: jnylen
Maintainer: slondr (mandeepsan)
Last Packager: slondr
Votes: 199
Popularity: 1.44
First Submitted: 2017-10-06 10:00 (UTC)
Last Updated: 2022-08-10 23:28 (UTC)

Latest Comments

slondr commented on 2022-08-10 23:30 (UTC)

Package updated to version 1.10.5

slondr commented on 2022-08-10 00:06 (UTC)

Package updated to version 1.10.4

bitterhalt commented on 2022-07-12 13:05 (UTC) (edited on 2022-07-12 13:06 (UTC) by bitterhalt)

Seems to work but it also crashes in background and creating a thousands of lines the error code "core dumped" logs..

mandeepsan commented on 2022-04-19 06:09 (UTC)

Package has been updated to 1.10.3

mandeepsan commented on 2022-03-30 03:31 (UTC)

Package has been updated to 1.10.2

slondr commented on 2022-03-12 18:05 (UTC)

Package updated to version 1.10.1

slondr commented on 2022-03-06 16:01 (UTC)

I've added appmenu-gtk-module as an optional dependency. This package provides an alternative to libappindicator-gtk3 (which was already an optional dependency) to provide app menu/taskbar icon support for non-Gtk-based desktop environments.

If you already had a working app icon, no additional work is necessary on your system.

slondr commented on 2022-02-28 23:53 (UTC)

Package updated to version 1.10

akhil commented on 2022-02-26 12:08 (UTC)

temporary fix for i3 users i3-msg 'exec --no-startup-id mailspring --no-sandbox'

renan_bodom commented on 2022-02-20 02:55 (UTC)

Thanks you @tomrudnick!

SpidFightFR commented on 2022-02-18 18:54 (UTC)

Thanks for the tip, @tomrudnick, it seems to work. That should do the trick until the next update.

tomrudnick commented on 2022-02-18 12:51 (UTC)

Starting Mailspring with --no-sandbox should fix it temporarily.

SpidFightFR commented on 2022-02-18 11:28 (UTC)

Also crashing with the error code "core dumped".

reisbauer commented on 2022-02-17 07:37 (UTC) (edited on 2022-02-17 07:40 (UTC) by reisbauer)

Also crashing:

{"error":null}
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
Manual update check (updates.getmailspring.com/check/linux/x64/1.9.2-6e14dad1/anonymous/stable) returned 204
[4447:0217/083436.721191:FATAL:gpu_data_manager_impl_private.cc(1034)] The display compositor is frequently crashing. Goodbye.
Failed to get crash dump id.
Report Id: {"success":true}
Failed to get crash dump id.
Report Id: {"success":true}
[1]    4447 illegal hardware instruction (core dumped)  mailspring

Gusted commented on 2022-02-16 21:17 (UTC)

Also recently starting to get crashes:

[8733:0216/221526.932431:FATAL:gpu_data_manager_impl_private.cc(1034)] The display compositor is frequently crashing. Goodbye.
Failed to get crash dump id.
Report Id: {"success":true}
Failed to get crash dump id.
Report Id: {"success":true}
[1]    8733 illegal hardware instruction (core dumped)  mailspring

vinnivitz commented on 2022-02-11 16:43 (UTC)

Since some time the client is crashing quite often. I dont know if this is related to the use of multiple email addresses. When I start it from the terminal there are no error longs when it crashes. It seems like it just freezes at a certain point. I am using manjaro with kernel 5.16 and xfce 4.16. Does somebody else encounter this issue?

wcasanova commented on 2021-12-28 23:35 (UTC) (edited on 2021-12-28 23:41 (UTC) by wcasanova)

you must activate the libsecret service in keepassxc, by default it is turned off. I use it and it works with KeePassXC. https://avaldes.co/2020/01/28/secret-service-keepassxc.html

apart from activating libsecret, you must expose the db to at least one group, not just activate it.

gardotd426 commented on 2021-12-28 23:31 (UTC) (edited on 2021-12-28 23:32 (UTC) by gardotd426)

I had keepassxc open and the keyring unlocked (my Passwords.kdbx file) and the second I uninstalled gnome-keyring Mailspring would refuse to launch because of the lack of libsecret support (same error as if you have no keyring or libsecret installed).

Oh and this is with the Secret Services integration in Keepassxc enabled.

wcasanova commented on 2021-12-28 23:28 (UTC)

@gardotd426 yes it works, the only thing you must have keepassxc open and unlocked so that it can read and write in a dedicated folder for secrets

crabvk commented on 2021-12-23 19:55 (UTC)

Hi. Since you don't build package from source and only repack deb package, you should rename it to mailspring-bin.

Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. An exception to this is with Java. The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist.

https://wiki.archlinux.org/title/AUR_submission_guidelines

Thank you for the package.

SpidFightFR commented on 2021-12-20 10:07 (UTC)

Great (the best, imo) email client, i love the design and the AUR version works perfectly. Upvoted.

gardotd426 commented on 2021-12-19 07:54 (UTC)

@wcasanova none of those actually work, gnome-keyring is the only way to get Mailspring to actually work.

wcasanova commented on 2021-11-29 19:48 (UTC)

delete gnome-keyring, Provides org.freedesktop.secrets @rcintra https://rtfm.co.ua/en/what-is-linux-keyring-gnome-keyring-secret-service-and-d-bus/

https://www.cogitri.dev/posts/03-keepassxc-freedesktop-secret/#setting-up-within-keepassxc

drarig29 commented on 2021-11-23 00:31 (UTC)

I would suggest adding libunity as a dependency, to fix this badge issue on KDE: https://github.com/Foundry376/Mailspring/issues/1890#issuecomment-612424494

rcintra commented on 2021-11-10 04:09 (UTC) (edited on 2021-11-10 04:09 (UTC) by rcintra)

The application does not work if gnome-keyring is not installed, at least when skipping the step to use a Mailspring ID. You may consider making that dependency not optional.

slondr commented on 2021-11-08 19:50 (UTC)

This was discussed previously. If someone had a working source release, then yes this package should be renamed. Until then, doesn't make much sense to.

Hanabishi commented on 2021-11-08 19:34 (UTC)

@MithicSpirit, yeah, I've tried. But maybe someone will dive in it successfully.

MithicSpirit commented on 2021-11-08 18:10 (UTC)

@Hanabishi yeah I think I've also brought that up but the maintainer hasn't renamed the package yet :/

There isn't much of an issue with this currently because building Mailsync is a pain on Arch rn due to differing library versions and stuff.

Hanabishi commented on 2021-11-08 17:47 (UTC) (edited on 2021-11-08 17:52 (UTC) by Hanabishi)

Shouldn't this package be named -bin? Because source code for building the app is avaliable.
According to https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission

mandeepsan commented on 2021-09-29 10:07 (UTC)

The PKGBUILD is now fixed for coreutils 9.0-1 that was causing build to fail. I really appreciate Humandoodlebug to bring this bug into our attention.

Humandoodlebug commented on 2021-09-29 08:42 (UTC) (edited on 2021-09-29 08:53 (UTC) by Humandoodlebug)

I'm getting an error in the package() stage. Seems to be caused by the line chmod -R go-w "${pkgdir}"/usr, which tries to recursively change the permissions on the symlink usr/bin/mailspring. In my testing, this is fine when the symlink is directly specified in the command but returns error status when it is found through recursion. Permissions on symlinks aren't really a thing anyway, so perhaps it's best to split the line in two like this:

chmod go-w "${pkgdir}"/usr "${pkgdir}"/usr/bin
chmod -R go-w "${pkgdir}"/usr/share

EDIT: This appears to be a new change in behaviour of chmod between coreutils 8.32-1 and 9.0-1. This seems to have broken a few other packages too, e.g. spotify. Downgrading to 8.32-1 fixes it, but that's probably not a good long-term solution.

slondr commented on 2021-09-16 21:03 (UTC)

Package updated to version 1.9.2. I appreciate everyone's patience.

Sasuchi commented on 2021-09-09 12:05 (UTC)

Version 1.9.2 Instruction: Edit Buildfile and change this lines: pkgver=1.9.2 sha256sums_x86_64=('a3bc365c77791673d8b7d8fc2081b2e8e80ab5d78d6ffa99f848971849f43544')

After saving you can install/ update

que5779 commented on 2021-09-08 20:41 (UTC)

I switched to Manjaro from Ubuntu because of the snaps and bloat, but snaps have creeped into Manjaro the past few major Gnome updates. So I am now using the auto updating snap from https://snapcraft.io/mailspring. There are Arch and Manjaro instructions.

flavio92ux commented on 2021-09-08 18:30 (UTC) (edited on 2021-09-16 11:07 (UTC) by flavio92ux)

package out of date. I downloaded .deb package from official site and used debtap for converting .deb for arch linux package and worked.

rajkrys commented on 2021-09-08 13:55 (UTC)

I do agree, since couple of days my Mailspring is asking for update... would be nice to update this repo.

moonaru commented on 2021-09-08 06:09 (UTC)

Version 1.9.2 has been released. It would be good if there is an update.

aorth commented on 2021-08-14 14:54 (UTC)

@FabioLolix ouch! That's terrible. So... yeah... bin package it is for now.

FabioLolix commented on 2021-08-13 10:31 (UTC)

Building mailspring from source is a PITa, for various reasons; like it need to use GCC5.

aorth commented on 2021-08-13 10:27 (UTC) (edited on 2021-08-13 10:27 (UTC) by aorth)

I agree with @MithicSpirit that this should be renamed to mailspring-bin. The MailspringID is now option (you can skip it during setup). Someone should start packaging a source version so we can eventually get Mailspring in the [community] repos (eeek, that electron8 though!).

MithicSpirit commented on 2021-07-12 23:45 (UTC)

Shouldn't this be renamed to mailspring-bin, since mailsync is now also open source (and has been for a few months)?

slondr commented on 2021-04-28 16:31 (UTC)

Package updated to version 1.9.1. I appreciate everyone's patience.

samstator commented on 2021-04-27 15:07 (UTC) (edited on 2021-04-27 15:09 (UTC) by samstator)

14 days and counting from the 1.9 release. Even 1.9.1 is out. Should have been updated by now.

txtsd commented on 2021-04-27 07:47 (UTC)

@NishantN It's a solid release, not a beta. So this package should have updated to it by now.

@slondr If you'd like us to help maintain, please add us as maintainers. We'd be happy to help.

NishantN commented on 2021-04-26 13:22 (UTC)

Is this package being actively maintained? It's been 12 days since mailspring was updated. Or are you waiting for a more stable release before you update it here?

mdeboer commented on 2021-04-18 12:35 (UTC)

If you need a (co-)maintainer, I'd be happy to adopt this :)

si1enced0ne commented on 2021-04-17 17:16 (UTC)

To continue the train of updating the PKGBUILD file.

Line 8 pkgver= 1.9.1 line 19 sha256sums_x86_64=('99fa700d84691542c3f5387cb48e72a9be516166491daadb598a5f292dd0ea61')

testbird71 commented on 2021-04-14 14:48 (UTC)

For all you want not wait, change the Pkgbuild file

Line 8 pkgver= 1.9.0 line 19 sha256sums_x86_64=('212c0d151f0cdfbefe27b5a81bd3256e517caf9c914e00b1106b336428ea5bf9')

gardotd426 commented on 2021-03-27 11:31 (UTC) (edited on 2021-03-27 11:32 (UTC) by gardotd426)

I believe you might also need one of the keyring packages, like libgnome-keyring, just depending on which DE you're on.

Kalyan commented on 2021-03-27 06:51 (UTC)

I'm new to arch, and have this problem while running the application. Mailspring could not store your password securely. Make sure you have 'libsecret' installed and a keyring is present. When I'm trying to install the optional dependencies in the its throwing an error as well.

niraami commented on 2021-03-16 10:34 (UTC)

Can confirm, it seems that gtk3 1:3.24.27-4 fixed this issue.

d-air1 commented on 2021-03-15 17:00 (UTC)

Seems it was fixed in todays update.

knaick commented on 2021-03-14 22:28 (UTC)

The lines causing problems in the gtk3 package build

cvalcort commented on 2021-03-14 21:44 (UTC)

Installing gtk3-no_deadkeys_underline solved the problem:`sqlite3_db_mutex(db->db_handle) == __null' failed.

knaick commented on 2021-03-14 21:03 (UTC)

I just found the same issue and pinned pointed the same reason as @d-air1 and @croyleje.

Installing gtk3-no_deadkeys_underline-1:3.24.26-1 did the trick.

croyleje commented on 2021-03-14 17:20 (UTC)

I can confirm having the same issue downgrading to gtk3-1:3.24.27-2-x86_64.pkg.tar.zst resolved the issue but my question is how hard would it be to replicate the NixOS fix on arch. It appears Nix uses a type of dependencies file that allows you to pass arguments at build time what would be the way of doing this on arch I am willing to learn how to do it just don't know what to look for if anyone could point me in the correct direction it would greatly appreciated. I tried changing the PKGBUILD and adding the same argument but that doesn't seem to work.

d-air1 commented on 2021-03-14 15:08 (UTC) (edited on 2021-03-14 15:22 (UTC) by d-air1)

Seems that this app is crashing on startup. The only recent dependency that I see that got upgraded was gtk3.

Edit: I wanted to add that some people over at nixos seem to have fixed the issue. Here is a link to that discussion in the hopes that it might help you out as well: https://github.com/NixOS/nixpkgs/issues/106732

Edit 2: Mailspring-libre aur package is having the same issue. There is more discussion over there. Figured I drop that link just in case: https://aur.archlinux.org/packages/mailspring-libre/

adrianinsaval commented on 2021-02-24 02:38 (UTC)

package should be renamed to mailspring-bin

MithicSpirit commented on 2021-02-22 20:58 (UTC)

The source link in the .SRCINFO file appears to be out of date, as it still points to v1.7.8. The updated version can be obtained by running makepkg --printsrcinfo > .SRCINFO.

MithicSpirit commented on 2021-02-16 15:53 (UTC)

Also, the license can be changed to just "GPL3" I think.

neitsab commented on 2021-02-09 03:13 (UTC)

In the light of the open sourcing of the entire codebase, could you rename the package "mailspring-bin" so that another built-from-source package may be submitted to the AUR? It is indeed customary to label pre-built binary package as such to prevent confusion. Thanks!

FabioLolix commented on 2021-02-08 20:46 (UTC)

A welcoming news https://community.getmailspring.com/t/a-free-open-source-future-for-mailspring/484

wcasanova commented on 2021-01-20 12:22 (UTC) (edited on 2021-01-20 12:24 (UTC) by wcasanova)

@Archange https://community.getmailspring.com/t/mailspring-without-mailspring-id/64

Mailspring stores your mail credentials securely on your machine in the keychain / keyring, and does not send your email credentials to the cloud. All email sync is done on your computer.

https://github.com/Foundry376/Mailspring/blob/master/ROADMAP.md#why-is-mailsync-closed-source

sachmalh commented on 2021-01-20 12:14 (UTC)

basically change

pkgver=1.8.0

and

sha256sums_x86_64=('06dcd870737ceea1fbb371a206bb037e6bb2f6fdb176109e49286ef3e4fd4f71')

sachmalh commented on 2021-01-20 12:09 (UTC)

change your pkgbuild as follows

Maintainer: Eric S. Londres ericlondres@protonmail.com
Contributor: Joakim Nylén me@jnylen.nu
Contributor: Rashintha Maduneth rashinthamaduneth@gmail.com
Contributor: Dhananjay Balan mail@dbalan.in
Contributor: ahrs

pkgname=mailspring pkgver=1.8.0 pkgrel=1 pkgdesc="A beautiful, fast and maintained fork of Nylas Mail by one of the original authors." arch=('x86_64') license=('custom: GPL3 and (C) 2016-2019 Foundry 376, LLC.') url="https://getmailspring.com/" options=('!strip')

source=()

source_x86_64=("https://github.com/Foundry376/Mailspring/releases/download/${pkgver}/mailspring-${pkgver}-amd64.deb") sha256sums_x86_64=('06dcd870737ceea1fbb371a206bb037e6bb2f6fdb176109e49286ef3e4fd4f71')

depends=("libxss" "libtool" "c-ares" "ctemplate" "tidy" "libxkbfile" "libsecret" "gtk3" "nss" "libglvnd")

optdepends=('libappindicator-gtk3: for system tray support' "libgnome-keyring: keyrings" "gnome-keyring: keyrings" )

package() { cd ${srcdir}

tar -xvf data.tar.xz -C ${pkgdir} --exclude='./control'

chmod -R go-w "${pkgdir}"/usr

}

Archange commented on 2021-01-20 12:08 (UTC)

@burakcank

Mailspring has one of the best UI/UX designs out there imo, honestly I am not sure why this package is not more popular than it is right now.

Because it’s not open source (mailsync engine) and requires registration (though Mailspring Libre fork work around this).

wcasanova commented on 2021-01-20 12:00 (UTC) (edited on 2021-01-20 12:45 (UTC) by wcasanova)

no need to have gnome-keyring as dependency. just have org.freedesktop.secrets and use any program that provides it. to work with KeePassXC, you have to enable a group to integrate it, more info here. https://rtfm.co.ua/en/what-is-linux-keyring-gnome-keyring-secret-service-and-d-bus/

https://www.cogitri.dev/posts/03-keepassxc-freedesktop-secret/#setting-up-within-keepassxc @Archange

burakcank commented on 2021-01-20 11:49 (UTC)

A new version has come out, @slondr will probably be working on it soon.

Mailspring has one of the best UI/UX designs out there imo, honestly I am not sure why this package is not more popular than it is right now.

gardotd426 commented on 2020-10-15 23:24 (UTC)

I guess we'll just have to use one of the other AUR packages, or the package from the community repository.

Archange commented on 2020-10-15 23:19 (UTC)

Has anyone tried with e.g. KeePassXC instead of gnome-keyring? If so, the dependency should be org.freedesktop.secrets.

maxcahill commented on 2020-10-15 22:19 (UTC)

Chiming in that as another kde user, gnome-keyring was required to get mailspring running. It actually popped up a window saying it "could not store my password securely", and then closed, so it's not like there's some limited functionality that you can use without it.

It's clearly not an optional dependency - if there are non-gnome alternatives that it would happily work with, that's not made clear :)

As a sidenote, the popup hinted I might want to install libsecret as well - which was already installed. After installing gnome-keyring, it ran fine.

capoeira commented on 2020-08-21 11:26 (UTC)

in fact @gardotd426's argument doesn'tmake sense. neofetch has limited function without the optional dependency, mailspring has zero function without gnome-keyring.

grega commented on 2020-08-21 10:57 (UTC)

Sorry for the late response. @gardotd in my case failed to start on the fresh install of KDE plasma. Tracking down the issue, I have also came across the same issue as linked in the @capoeira comment.

Anyway, all issues were gone when I installed gnome-keyring package on my non-gnome desktop environment.

capoeira commented on 2020-08-11 09:41 (UTC)

@gardotd426 it might run, but it doesn't work: https://github.com/Foundry376/Mailspring/issues/713

gardotd426 commented on 2020-08-05 09:40 (UTC) (edited on 2020-08-05 09:42 (UTC) by gardotd426)

I just uninstalled gnome-keyring and libgnome-keyring and installed mailspring, and it runs (I'm not logged into gnome right now).

So yeah, it's not a mandatory dependency. I know it's weird but mandatory dependencies are only dependencies which are required for everyone no matter what in order for the package to function. And that doesn't even mean fully function either, a good example is a package like neofetch that will ONLY display images in the terminal if you have one of the optional dependencies for images installed. Otherwise, it doesn't fully function, but they still aren't mandatory dependencies.

gardotd426 commented on 2020-08-05 09:37 (UTC) (edited on 2020-08-05 09:38 (UTC) by gardotd426)

@grega it should only fail to start without gnome-keyring on desktop-environments that use gnome-keyring. That wouldn't be a mandatory dependency, because it wouldn't be necessary on desktop environments with other keyrings.

grega commented on 2020-08-05 09:32 (UTC)

Hi, would be possible to move the gnome-keyring dependency from optional to mandatory, since the app fails to start if gnome-keyring is not installed?

slondr commented on 2020-05-19 23:30 (UTC)

@hodsonus: No problem! I'm subscribed to GitHub release notifications, so as soon as they put out a new version I should be able to update it relatively quickly.

hodsonus commented on 2020-05-19 23:27 (UTC)

@slondr thanks for the response! new to Arch and the AUR and realized that it was dependent on the upstream .deb and not the git repository shortly after commenting. thanks for being understanding :).

slondr commented on 2020-05-19 23:20 (UTC)

@hodsonus Until they put out another GH release (and update the upstream .deb), I don't think so.

hodsonus commented on 2020-05-19 21:47 (UTC) (edited on 2020-05-19 21:47 (UTC) by hodsonus)

@slondr Hi, any way that we can get another update? A bug affecting Yahoo accounts was just resolved (https://github.com/Foundry376/Mailspring/issues/1974).

haleff commented on 2020-05-15 17:37 (UTC)

@slondr yeah, thanks for asking and I'm sorry that I got an panic. I last had it half a year ago only with Davinci Resolve.

slondr commented on 2020-05-15 17:34 (UTC)

@haleff I'm glad it worked for you (eventually)!

haleff commented on 2020-05-15 17:33 (UTC)

@slondr It loaded endlessly at the package build stage, but now everything has worked. (in half a day)

slondr commented on 2020-05-15 17:30 (UTC)

@haleff Where does it load infinitely for you?

haleff commented on 2020-05-15 07:37 (UTC)

Cant install new 1.7.6 version of Mailspring package. Infinite loading.

slondr commented on 2020-05-15 03:09 (UTC)

Package has been updated to 1.7.6; it compiled & installed fine for me, let me know if you have any issues

eschwartz commented on 2020-05-15 02:34 (UTC)

Yeah, that's just spam, deleted.

gardotd426 commented on 2020-05-15 02:31 (UTC)

@tmmh that's not even remotely helpful and doesn't belong on this thread whatsoever. This package (and all the other GUI email clients) exist for a reason, and regardless of your opinion on them, which is irrelevant anyway, it doesn't belong here.

gardotd426 commented on 2020-05-11 20:48 (UTC) (edited on 2020-05-11 20:50 (UTC) by gardotd426)

Yeah, this already has seemingly at least two orphan requests, when it's time, they'll orphan it.

capoeira commented on 2020-05-11 14:44 (UTC)

@eschwartz thanks for clarification

eschwartz commented on 2020-05-11 14:20 (UTC) (edited on 2020-05-11 14:22 (UTC) by eschwartz)

We're not going to orphan a package that has seen very recent maintenance without giving the maintainer the full two weeks grace period. We are also at 4 orphan requests and counting, which is completely unnecessary, so please stop that now, everyone.

Special exceptions may be made if the maintainer hasn't logged in to the AUR in a long time, and/or the package has been flagged out of date for many months. The AUR software automatically accepts requests on packages which were flagged out of date >=6 months ago. None of that is the case here.

I strongly recommend you all learn the fine art of patience.

capoeira commented on 2020-05-11 13:42 (UTC)

I agree, orphan request is the way to go. Though I don't know how this is handled. I requested one for a package once and it was orphaned in a few hours. This one seams to have requests for days and nothing is happening

eschwartz commented on 2020-05-11 12:53 (UTC) (edited on 2020-05-11 12:55 (UTC) by eschwartz)

I'll be happy to suspend the account of anyone creating duplicate packages when they know this is against the rules of submission. Maybe then people will learn that it doesn't matter how out of date this package is, your options are either submit an orphan request for this one or do nothing at all.

I guarantee you I'm more frustrated than you are.

rojo commented on 2020-05-11 12:16 (UTC)

@Raymo111

https://wiki.archlinux.org/index.php/AUR_submission_guidelines

"Check the AUR if the package already exists. If it is currently maintained, changes can be submitted in a comment for the maintainer's attention. If it is unmaintained or the maintainer is unresponsive, the package can be adopted and updated as required. Do not create duplicate packages."

I understand you are frustrated but do not create your own package. Just follow the procedure and email support staff and most likely you will become the maintainer.

I'll go ahead and send an email as well.

Raymo111 commented on 2020-05-10 22:58 (UTC)

I'm sick of waiting for mailspring to be updated so I'm maintaining https://aur.archlinux.org/packages/mailspring-latest/. I'm subscribed to the git repo and use mailspring every day, so updates will be prompt.

sachmalh commented on 2020-05-08 05:51 (UTC)

@gardotd426. Thanks @rojo basically i got the checksum from mailspring git. I would love to maintain this package @rashintha and @jnylen

jnylen commented on 2020-05-08 00:36 (UTC)

@pappfer I moved to Thunderbird. Way stabler.

gardotd426 commented on 2020-05-07 14:04 (UTC)

@rojo you just run sha256sum FILENAME and it gives it to you.

rojo commented on 2020-05-07 13:53 (UTC)

@sachmalh Thank you this worked perfectly

Out of curiosity, where did you find the new sha256sum?

hirnschmalz commented on 2020-05-06 06:09 (UTC)

@rashintha can you please provide an update for this package or hand it over to another maintainer?

gardotd426 commented on 2020-05-03 08:08 (UTC)

I was about to come say the same thing that @sachmalh said, that there was a new version and the PKGBUILD just needs updating with 1.7.6 instead of 1.7.5 in the version section, and changing the sha256sum to 176a73fc1f209f01824e9ed1d85c091ff94207c9f5578974e4335f8b8536ca8d

pappfer commented on 2020-05-01 12:13 (UTC)

@jnylen, thanks for your work so far. What did you switch to?

ObiWanKaTommy commented on 2020-05-01 10:08 (UTC)

@rashintha , if you want I can keep this package uptodate

jnylen commented on 2020-04-30 23:35 (UTC)

@knaick, I don't even use mailspring anymore. I was just being nice and updating it. I stopped now though. So just ping @rashintha if you want to collab.

knaick commented on 2020-04-30 01:02 (UTC)

@jylen might I ask if you will provide an upgrade to the package in the next days ?

sachmalh commented on 2020-04-23 19:54 (UTC) (edited on 2020-04-26 20:42 (UTC) by sachmalh)

@jnylen -- love the classic comment!!

for the restless just make these two changes in PKGBUILD, worked for me

pkgver=1.7.6

sha256sums_x86_64=('176a73fc1f209f01824e9ed1d85c091ff94207c9f5578974e4335f8b8536ca8d')

-- Sachin (even after 2 years, I still consider myself as an arch newbie)

jnylen commented on 2020-04-17 17:14 (UTC)

Calm down a bit. I'll update it soon. The new version has been out for less than a day.

timadevelop commented on 2020-04-17 17:09 (UTC)

There's a new release https://github.com/Foundry376/Mailspring/releases .. Someone?

slondr commented on 2020-04-17 14:59 (UTC)

Is anyone maintaining this?

LinuxLucas commented on 2020-04-17 14:27 (UTC)

This is my favorite email client by far! Super elegant, beautiful yet so diverse in its features!

7kronos commented on 2020-04-17 09:12 (UTC)

Also ability to add a second account should be solved by 1.7.5

b00f commented on 2020-04-15 13:40 (UTC)

Due to this comment upgrading to version 1.7.5 should solve this issue. (blank screen) https://github.com/Foundry376/Mailspring/issues/1817

Waiting for upgrade

slondr commented on 2020-03-27 14:31 (UTC)

gconf should be removed as a dependency, see the pinned comment on that package.

This is breaking updates for me.

hansva commented on 2020-03-26 10:23 (UTC)

@DiddleRiddle, it's a known bug, only solution is to downgrade to 1.7.2

DiddleRiddle commented on 2020-03-24 22:12 (UTC)

white screen issue after configure imap smtp. how to solve a problem?

capoeira commented on 2020-03-24 10:26 (UTC)

@domalak So I did just now, thanks. seams to work fine

domalak commented on 2020-03-24 07:39 (UTC)

@capoeira I've updated. Works fine so far.

capoeira commented on 2020-03-23 23:51 (UTC)

So is it safe to update if you don't need to add new accounts anyways?

hansva commented on 2020-03-21 16:25 (UTC)

Why was this package updated anyway? The current version has fundamental bugs that have not yet been resolved

jnylen commented on 2020-03-21 15:24 (UTC)

Never mind, forgot I wasn't the main maintainer anymore. Hopefully @rashintha comes back asap ;)

jnylen commented on 2020-03-21 15:23 (UTC) (edited on 2020-03-21 17:15 (UTC) by jnylen)

Sorry, been a bit busy. Bumped the version now and I will add @ali.molaei as a contributor.

Infinite.New1 commented on 2020-03-21 14:52 (UTC)

LOL

outfrost commented on 2020-03-21 14:34 (UTC)

@Infinite.New1 Surely it can't be that global pandemic that's disrupting everyone's lives right now

Infinite.New1 commented on 2020-03-21 14:13 (UTC)

There's 0 commit for the last 26 days... Something must be wrong at Foundry 376.

capoeira commented on 2020-03-21 11:19 (UTC)

issues page is full of bugreports regarding the add account bug: https://github.com/Foundry376/Mailspring/issues

question is, why is this not fixed yet after all those weeks?

ali.molaei commented on 2020-03-21 09:27 (UTC)

Hey guys, I emailed the maintainers to see if they maintain this package anymore, considering @sethmurphy18 comment about a bug in the new version, I think we should wait and see how they respond

rithvikvibhu commented on 2020-03-21 05:43 (UTC)

@Fourstepper that package doesn't exist anymore.

Infinite.New1 commented on 2020-03-20 03:58 (UTC) (edited on 2020-03-20 03:59 (UTC) by Infinite.New1)

It's been almost one month... Is this package is going to be updated or sethmurphy18's comment is right?

Fourstepper commented on 2020-03-11 11:24 (UTC)

Looks like there is a second package available as well https://aur.archlinux.org/packages/mailspring-new/ @outfrost thank you

outfrost commented on 2020-03-10 14:22 (UTC)

@Fourstepper Please see @sethmurphy18's comment

Fourstepper commented on 2020-03-10 13:29 (UTC)

I noticed this package is out of date, is it safe to use for now? Is it generally maintained?

Matthew02 commented on 2020-02-29 21:30 (UTC)

I second the motion to remove gconf from the dependency list.

sethmurphy18 commented on 2020-02-27 00:29 (UTC)

Package is out of date, but it's probably intentional. The latest version (1.7.4) has a major bug that prevents users from adding accounts. Should probably refrain from marking as out of date for now.

gilsondev commented on 2020-02-25 14:02 (UTC)

Have new version now (v1.7.4)

Archange commented on 2020-01-10 15:30 (UTC)

Indeed, mailspring should actually have a dependency on org.freedesktop.secrets just like e.g. geary.

outfrost commented on 2020-01-07 23:00 (UTC) (edited on 2020-01-07 23:06 (UTC) by outfrost)

Regarding gnome-keyring, I think the reason why it's an optional dependency is that it's possible to use other software that implements an org.freedesktop.secrets service - it's just that, for a long while, gnome-keyring has been the only one out there. That said, I think some other implementations are getting there.

Making gnome-keyring optional might be possible through a 'workaround' (more of a feature, actually), if someone looks into it: https://github.com/Foundry376/Mailspring/issues/1512

The error output from running Mailspring without an org.freedesktop.secrets service installed can be seen here.

E3LDDfrK commented on 2020-01-05 17:57 (UTC) (edited on 2020-01-05 17:57 (UTC) by E3LDDfrK)

If it won't start without gnome-keyring, I don't think you can say gnome-keyring is an optional dependency.

Haven't tried libgnome-keyring.

And I don't use gnome, so this feels forced for no good reason.

ali.molaei commented on 2020-01-03 12:32 (UTC)

I think you can remove gconf from dependancies as it is not needed by electron anymore

linkghm commented on 2020-01-03 03:18 (UTC) (edited on 2020-01-03 03:18 (UTC) by linkghm)

I also met the libsecret problem, my solution is installing gnome-keyring, and now it works.

now-im commented on 2019-10-24 19:37 (UTC)

mailsping needs "zenity" in order to show notifications. It is mentioned in preferences. Kindly add it as an optional dependency.

jacka commented on 2019-10-23 05:33 (UTC)

Great to see it's now up to date ! Thanks a lot !

ulgens commented on 2019-10-15 07:29 (UTC)

For release 1.7.1, change pkgver to 1.7.1 and sha256sum to 7f9bea33834494e019e6c1e451583a218e340c6c9cfc043c35e40fe6726e9e11

AK4EVA commented on 2019-10-14 18:52 (UTC) (edited on 2019-10-14 18:56 (UTC) by AK4EVA)

I'm not sure when this will be updated, but in the meantime, you can do the following when trying to install this package:

-Modify the pkgbuild file (usually your program of choice will give you an option to view the file, select yes)

CHANGE THE FOLLOWING: - pkgver to 1.7.0 - SHA256SUM to f70bf76692991a70887fec815672503de312a6126ba84bbe18bde921301ac811

Save and continue with build, ENJOY! :)

tasty213 commented on 2019-07-24 17:21 (UTC)

I just installed mailspring and it didn't install or at libsecret at all i've had to manually install it, i will try and reinstall looking at the package as i go

mrueg commented on 2019-07-20 12:00 (UTC)

Just tried installing mailspring with the new libsecret-only dependency. Something else that was provided by gnome-keyring seems to be missing now, as I got an error saying that libsecret was missing (which it wasn't) and the problem disappeared when I installed gnome-keyring.

jnylen commented on 2019-03-23 14:38 (UTC)

@flying-sheep, I can look into it when a new release comes if you don't mind.

flying-sheep commented on 2019-03-22 14:32 (UTC) (edited on 2019-03-22 14:45 (UTC) by flying-sheep)

Hi! mailspring uses the keytar npm package, which uses libsecret, not directly gnome-keyring.

could you please make the libgnome-keyring and gnome-keyring deps optional?

friday commented on 2019-03-20 14:35 (UTC) (edited on 2019-04-07 10:38 (UTC) by friday)

@jnylen: It seems to be possible, but you would need asar as a build dependency and it's a bit quirky. The built output also includes 65mb of files which the original build step excludes. It might be possible build it with grunt too, but that would add another dependency. From the directory app.asar is in: asar extract app.asar app; sed -i 's/updater.getState()/0/g' app/internal_packages/notifications/lib/items/update-notification.js; asar pack app app.asar; rm -rf app;

Not sure if it's fully safe. Trying it out now (notification is gone and it works).

Edit: Commented at the github issue instead since code formatting is not very readable here.

Edit 2: While it worked I found a simpler way compatible with this package: echo -e '\n127.0.0.1 updates.getmailspring.com' | sudo tee -a /etc/hosts

rashintha commented on 2019-03-20 12:49 (UTC)

@ilyes24 please check releases at https://github.com/Foundry376/Mailspring/releases before flagging the package.

jnylen commented on 2019-03-18 17:58 (UTC)

Updated it to 1.6.0. Thanks for notifying me.

@friday, Problem here is we are using the .deb file. Which means it's already compiled and built for us. So we can't really patch the binary (if you know a way do tell me). We could move to the git repo but that will make it a messy aur build.

I wrote a comment on the issue asking if there was a safe way to disable it.

friday commented on 2019-02-12 20:39 (UTC)

Suggestion: Add a patch to disable or hide the update notification: https://github.com/Foundry376/Mailspring/issues/1229 The dev doesn't seem to care much about "third-party distribution that lags behind releases". I think you just need to change this line to const updateAvailable = false or something similar: https://github.com/Foundry376/Mailspring/blob/866e41d506a26b18eb4b6fdde4e129fffce71af5/app/internal_packages/notifications/lib/items/update-notification.jsx#L25

chenlei commented on 2019-02-12 13:25 (UTC)

@rashintha It works! Thank you very much.

chenlei commented on 2019-02-12 11:56 (UTC)

@rashintha Thanks for you help, I'll try and I'll feedback.

rashintha commented on 2019-02-12 11:40 (UTC)

@chenlei

Try updating checksum. Download and extract the snapshot. Then,

$ updpkgsums

and then,

$ makepkg -si

chenlei commented on 2019-02-12 11:32 (UTC)

Is there any other way to install this app? I am a new linuxer, so please don't mind the simple question I asked.

chenlei commented on 2019-02-12 11:26 (UTC) (edited on 2019-02-12 11:27 (UTC) by chenlei)

@Pryka, @rashintha thanks for your help I am using SSD, and i just turn off my shadowsocks, but still the same error. sorry for my bad English

Pryka commented on 2019-02-12 11:14 (UTC) (edited on 2019-02-12 11:14 (UTC) by Pryka)

@chenlei connection(internet) issues or maybe HDD?

rashintha commented on 2019-02-12 10:28 (UTC)

@chenlei

Please retry. I rechecked the package. It's working fine.

Pryka commented on 2019-02-12 09:43 (UTC)

@chenlei

Try redownloading, no checksum error for me. Updated maybe 2h ago.

chenlei commented on 2019-02-12 09:06 (UTC)

正在验证 source_x86_64 文件,使用sha256sums... mailspring-1.5.6-amd64.deb ... 失败 ==> 错误: 一个或多个文件没有通过有效性检查!

sha256sums check failed sorry for my bad english

edivandjs commented on 2019-02-03 19:23 (UTC)

Thank you for making the package available in AUR. I want to report a bug. It does not show the top menus. I already reinstalled and it continues like this. Use Manjaro with XFCE interface.

rashintha commented on 2019-01-06 09:30 (UTC)

Thank you @dbalan. I have updated it to v1.5.5.

dbalan commented on 2019-01-06 05:10 (UTC)

Apologies for the radio silence, I have been travelling and don't have acces to an archlinux box. However @rashintha had expressed their willingness to maintain the package, so I am adding them as a co-maintainer.

FabioLolix commented on 2019-01-05 19:42 (UTC)

@dbalan please use pkgver= directly, _pkgver is uneeded and you have removed the previous packager from the credits https://wiki.archlinux.org/index.php/Arch_User_Repository#Rules_of_submission

ezekielnin commented on 2019-01-03 03:26 (UTC)

updpkgsums works perfectly for me! Thanks a lot!

faasie commented on 2019-01-03 01:37 (UTC)

@ezekielnin - That's a good question. Once you update the version in the PKGBUILD, you need to update the packagesums for that new package.

Here's how you do it: Update package version in PKGBUILD Generate new checksums with: (of course you don't include the $ in the command)

$ updpkgsums

Test install

$ makepkg -si

Update .SRCINFO

$ makepkg --printsrcinfo > .SRCINFO

And you should be all set.

ezekielnin commented on 2019-01-02 23:55 (UTC) (edited on 2019-01-02 23:55 (UTC) by ezekielnin)

@kerwin : newbie question : what do you mean update dpkg sums? If I clone the git, then makepkg -si, I still get version 1.5.3. Thank you for clarifying this. (again noob here)

kerwin commented on 2018-12-31 04:14 (UTC)

same script that I build Mailspring 1.5.4 can work ,so only need to update dpkg sums then it work!

kode54 commented on 2018-12-30 03:35 (UTC) (edited on 2018-12-30 03:37 (UTC) by kode54)

You may wish to investigate if Mailspring 1.5.4 really needs the copies of libEGL and libGLESv2 that it now bundles in /usr/share/mailspring/swiftshader.

Also, shouldn't this technically be a -bin package, since it installs from pre-built binaries packaged for Debian? This name should be reserved for building the package from source.

now-im commented on 2018-12-04 06:03 (UTC)

In KDE wayland gnome-keyring-daemon is not starting. Anyone facing the same problem?

dbalan commented on 2018-11-30 14:54 (UTC)

@now-im Added libappindicator-gtk3 as an optdependency.

now-im commented on 2018-11-30 13:26 (UTC)

libappindicator-gtk3 should be added as an optional dependency as KDE needs it to show system tray icon. Even in the preference, it is mentioned.

frigaut commented on 2018-11-20 08:35 (UTC)

Is that only me, or mailspring has issues with glibc compat? I get a lot of core dumps (one every 10-15mn) due to what appears to be glibc compatibility. Some seems to have minor effects, other results in freezing the interface. The whole thing is making mailspring essentially unusable.

I have tried to link mailspring to glibc2.27, but that fails because some other library that mailspring is using are requiring 2.28, and I didn't have the time to investigate further.

Just wondering if I am the only one. Also, it seems to me that this is the (almost) first occurrence in which archlinux rolling release system has shown a drawback.

Anonymo commented on 2018-11-08 20:45 (UTC)

Tired of the warning, updated to 1.5.2 https://justpaste.it/4x4su

cake808 commented on 2018-10-27 08:49 (UTC)

If you're having the libsecret / keyring issue, try this: https://github.com/Foundry376/Mailspring/issues/511#issuecomment-363842150

Archange commented on 2018-10-23 09:49 (UTC)

I don’t think there is an hard dependency on gnome-keyring, is it? Because KDE Wallet implement libsecret AFAIK, so you should be able to use it.

Pryka commented on 2018-10-23 04:37 (UTC)

Is there any way to change libsecret and gnome-keyring to KDE-wallet?

Or this is a nogo? Can't find any information about mailspring wallet support.

christcb commented on 2018-08-31 14:46 (UTC)

Mailspring 1.4.2-1 absolutely working with no issues under Manjaro-KDE

fevenius commented on 2018-08-27 15:05 (UTC) (edited on 2018-08-27 15:09 (UTC) by fevenius)

Why is gtk2 needed?
As of mailspring 1.3.0 electron 2.x is being used and mailspring should therefore solely depend on gtk3, shouldn't it?

jnylen commented on 2018-08-16 20:46 (UTC)

It's in stable now. 2.28-4.

Updated to 1.4.2. Sorry for the slow update.

Pryka commented on 2018-08-16 10:19 (UTC)

Fixed glibc is in testing for almost a week now.

Just install it. And the issue is basically solved.

guydep commented on 2018-08-16 08:32 (UTC)

I just created a PKGBUILD that patchelfs mailspring 1.4.1 with glibc 2.27. Mailspring runs flawlessly. See the PKGBUILD here: https://pastebin.com/5vPjKc3z

guydep commented on 2018-08-15 06:27 (UTC)

The package skype-stable-bin patches automatically the binary to use glibc-2.27. This may be a good solution while the new version of glibc fixes the issues with electron. See https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=skypeforlinux-stable-bin

puttyspeller commented on 2018-08-14 16:06 (UTC)

I've fixed my version of Mailspring with the glibc workaround but now am having a problem where Mailspring crashes if I try to download an attachment. I'm fairly new to linux so am dumber than most; any advice would be appreciated.

commented on 2018-08-12 21:11 (UTC)

@jnylen, That is indeed weird. I am sorry, I'll be more careful from now on.

jnylen commented on 2018-08-12 21:04 (UTC)

@jenz, Then update. 1.4.0 was uploaded 3 days ago. Not sure why you get that message.

Please check https://github.com/Foundry376/Mailspring/releases next time when you flag.

aksh1618 commented on 2018-08-11 10:36 (UTC)

@rocka commented a PKGBUILD at Typora, which fixed it by packaging it with system electron. Could something like that be done with Mailspring?

Pauligrinder commented on 2018-08-09 08:15 (UTC) (edited on 2018-08-09 08:20 (UTC) by Pauligrinder)

Latest version (still requires the older glibc):

_pkgver=1.4.0

sha256sums_x86_64=('ed1503d36be45376d15c5ec35a2d8dab5ef8b07b318e9578ce9b5ea42c3ed528')

jamesbrink commented on 2018-08-08 02:02 (UTC)

Same workaround that is posted for slack (which is also broken) works with mailspring

grab glibc-2.27 from archive

https://archive.archlinux.org/packages/g/glibc/glibc-2.27-3-x86_64.pkg.tar.xz

mkdir /opt/glibc-2.27
sudo bsdtar xf /var/cache/pacman/pkg/glibc-2.27-3-x86_64.pkg.tar.xz --cd /opt/glibc-2.27

sudo patchelf --set-interpreter /opt/glibc-2.27/usr/lib/ld-linux-x86-64.so.2 --set-rpath \$ORIGIN:\$ORIGIN/lib/:/opt/glibc-2.27/usr/lib/ /usr/bin/mailspring

Pryka commented on 2018-08-06 06:51 (UTC) (edited on 2018-08-07 09:08 (UTC) by Pryka)

EDIT: https://bugs.archlinux.org/task/59550

For some days now I can't run Mailspring. I get core dump all the time:

Process XXXX (mailspring) of user 1000 dumped core.
Stack trace of thread 2415:
0  0x0000000000a4fa30 n/a (mailspring)

GDB:

Starting program: /usr/bin/mailspring 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault. 0x0000000000a4fa30 in ?? () (gdb) bt full 0 0x0000000000a4fa30 in () 1 0x00007ffff7d832b2 in node::http2::Http2Session::Callbacks::Callbacks(bool) () at /usr/share/mailspring/libnode.so 2 0x00007ffff7d83375 in () at /usr/share/mailspring/libnode.so 3 0x00007ffff7fe36da in call_init.part () at /lib64/ld-linux-x86-64.so.2 4 0x00007ffff7fe37da in _dl_init () at /lib64/ld-linux-x86-64.so.2 5 0x00007ffff7fd503a in _dl_start_user () at /lib64/ld-linux-x86-64.so.2 6 0x0000000000000001 in () 7 0x00007fffffffea7c in () 8 0x0000000000000000 in ()

It started to behave like this after some Arch updates. Can't pinpoint exactly which one.

simeonoff commented on 2018-06-02 06:14 (UTC) (edited on 2018-06-02 06:15 (UTC) by simeonoff)

I get the following when trying to install:

==> Making package: mailspring 1.2.2-1 (Sat 02 Jun 2018 09:09:24 AM EEST)
==> Checking runtime dependencies...
==> Installing missing dependencies...
/usr/bin/pacman: unrecognized option '--color never'
==> ERROR: 'pacman' failed to install missing dependencies.
:: failed to build mailspring package(s)

pacman version 5.1.0

jnylen commented on 2018-05-18 19:26 (UTC)

@salkiran, I follow the stable releases from https://github.com/Foundry376/Mailspring/releases

Which also is the one that notify users of outdated versions.

saikiran commented on 2018-04-09 08:42 (UTC)

I think this package is obsolete from the master, it needs to be updated to the latest version of mailspring.

jnylen commented on 2018-02-04 14:51 (UTC)

Thanks RemoteAdmin, I have just pushed an update.

RemoteAdmin commented on 2018-02-04 05:23 (UTC) (edited on 2018-02-04 05:24 (UTC) by RemoteAdmin)

I have executed readelf -d against the package and I have found two dependencies that are missing:

"gtk2" "nss"

If you add them, then you can also remove the following libraries as they are dependencies of the upper ones:

"icu" "libxext" "openssl" "libxtst" "glib2" "glibc" "libxml2" "libutil-linux"

The new dependes array therefore should be:

depends=("libgnome-keyring" "gnome-keyring" "libxss" "libtool" "c-ares" "ctemplate" "tidy" "libxkbfile" "libsecret" "gconf" 'gtk2' 'nss')

Also to verify my claim, the following contains the list of libraries requiring the new dependencies:

/usr/share/mailspring/mailspring needs libgtk-x11-2.0.so.0
/usr/share/mailspring/mailspring needs libgdk-x11-2.0.so.0
/usr/share/mailspring/mailspring needs libnss3.so
/usr/share/mailspring/mailspring needs libnssutil3.so
/usr/share/mailspring/mailspring needs libsmime3.so

hattrickharry commented on 2018-01-30 04:21 (UTC)

+1 for gnome-keyring on KDE ... installing that seemed to do the trick for me, as well.

squarezin commented on 2018-01-29 21:58 (UTC) (edited on 2018-01-29 21:58 (UTC) by squarezin)

new version:

_pkgver=1.1.2

_pkghash=8ae17ea

sha256sums_x86_64=('5d34ae89cf41bf48440aa9c05937ab8828bab78babbc71501bf3d987e4c86d0a')

jnylen commented on 2018-01-22 21:16 (UTC)

No problem. ;)

ulgens commented on 2018-01-22 21:15 (UTC)

Update was very fast, as always, thank you :)

ulgens commented on 2017-12-29 08:25 (UTC)

The update was very fast, thank you :D

playenball commented on 2017-12-19 03:22 (UTC)

Changes to PKGBUILD for latest version (1.0.11):

_pkgver=1.0.11

_pkghash=ea4b20af

sha256sums_x86_64=('9a4499fea7fcba2db727595cbdcb049ee632f94517d36e22eed8a58b72800ca7')

superhansel commented on 2017-12-15 17:07 (UTC)

I am on GNOME and while package building works flawlessly, mailspring fails to start without libxss beeing installed.

Pauligrinder commented on 2017-12-07 13:07 (UTC) (edited on 2017-12-07 13:08 (UTC) by Pauligrinder)

Changes to PKGBUILD for latest version (1.0.10):

_pkgver=1.0.10

_pkghash=d250d253

sha256sums_x86_64=('b61f2fc929946da6f83bf02c7632be044d0e50c512105ef9c9c17a9d0d5c9f90')

Tamriel commented on 2017-11-22 16:14 (UTC)

On KDE I needed gnome-keyring to get it working.

jnylen commented on 2017-10-17 11:48 (UTC)

@gnunn, Do a ticket at mailspring's repo.

gnunn commented on 2017-10-16 13:57 (UTC)

I'm finding mailspring is acting as the default handler for text files when double clicking them in Nautilus. I presume this is because of the text/plain mimetype in the mailspring desktop file? If so, would it be possible to remove it ?

jnylen commented on 2017-10-13 09:37 (UTC)

@zhjn921224, Should work fine with libgnome-keyring

ChoromPotro commented on 2017-10-13 06:32 (UTC)

1.0.4 seems to have fixed custom IMAP issue.

wezm commented on 2017-10-11 20:55 (UTC)

> mailspring: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory It seems gconf needs to be listed as a dependency too.

zhjn921224 commented on 2017-10-11 09:32 (UTC)

It seems to need gnome-keyring. libgnome-keyring is deprecated, isn't it?

jnylen commented on 2017-10-11 04:04 (UTC)

Build 1.0.3 is out. Removed libsasl2 dependency and added glibc (due to removal of libpthread) and libsecret. 1.0.3 works fine here with GMail now.

dwleonard commented on 2017-10-10 22:55 (UTC)

Build 1.0.3 is out which seems to fix the SSL certificate issues and the SASL issues, from the changelog here: https://github.com/Foundry376/Mailspring/releases/tag/1.0.3 Fixes: On Linux, Mailspring looks for your trusted SSL certificate roots in more locations, fixing the "Certificate Errors" many Fedora and ArchLinux users were seeing when linking accounts. On Linux, Mailspring bundles SASL2 and SASL2 plugins, resolving "Authentication Error" messages that users of non-Debian Linux distros saw when the local installation of SASL2 was an incompatible version. On Linux, Mailspring now links against libsecret, resolving intermittent "Identity missing required fields" errors that were caused by the Node bindings to libgnome-keyring's API.

ConorIA commented on 2017-10-09 01:06 (UTC) (edited on 2017-10-09 01:19 (UTC) by ConorIA)

According to bengotow, the link for libsasl2.so.2 should really point to: "/usr/share/mailspring/resources/app.asar.unpacked/libsasl2.so.2". Of course, the "file exists" check that you have implemented means that those who have already installed would miss the new version of the link. I've worked around that by using `pacman -Qoq /usr/libsasl2.so.2`. See here: https://gist.github.com/ConorIA/b8c7c3ef6d70902dff169afbbbff7d2b EDIT: Even with this change, I still get SSL errors. :(

mareke commented on 2017-10-08 18:02 (UTC)

https://github.com/Foundry376/Mailspring/issues/13

nobicycle commented on 2017-10-07 01:56 (UTC)

Certainly it is A beautiful and fast, but not for me. My usual client claws-mail uses 50 MB. Mailspring 676 MB. Thanks to ahrs for the patch.

deboeckj commented on 2017-10-06 17:40 (UTC)

provider: 'gmail' } { Error: SyncWorker crashed with null (code 139): /usr/share/mailspring/resources/app.asar.unpacked/mailsync: line 4: 6306 Segmentation fault (core dumped) LD_LIBRARY_PATH=". ${LD_LIBRARY_PATH}" "$(dirname $0)/mailsync.bin" "$@" at EventEmitter._electron.ipcMain.on (/src/browser/application.es6:637:19) at emitTwo (events.js:106:13) at EventEmitter.emit (events.js:194:7) at WebContents.<anonymous> (/usr/share/mailspring/resources/electron.asar/browser/api/web-contents.js:256:13) at emitTwo (events.js:106:13) at WebContents.emit (events.js:194:7) message: 'SyncWorker crashed with null (code 139):\n/usr/share/mailspring/resources/app.asar.unpacked/mailsync: line 4: 6306 Segmentation fault (core dumped) LD_LIBRARY_PATH=". ${LD_LIBRARY_PATH}" "$(dirname $0)/mailsync.bin" "$@"\n' } { log: ' *** ??:? _Bind_simple::operator()()\n *** ??:? thread::_Impl::_M_run()\n *** (unknown) clone\n ***\n\n6289 [2017-10-06 19:39:02.437] [main] [info] ------------- Starting Sync ---------------\n6289 [2017-10-06 19:39:02.443] [background] [info] Fetching XOAuth2 access token for 79534a43\n6289 [2017-10-06 19:39:02.443] [metadata] [info] Metadata delta stream starting...\n6289 [2017-10-06 19:39:03.294] [background] [info] Marking all folders as `busy`\n6289 [2017-10-06 19:39:03.294] [background] [info] Syncing folder list...\n6289 [2017-10-06 19:39:03.652] [background] [critical] \n ***\n *** Mailspring GenericException occurred during program execution: \n *** {"debuginfo":"syncFoldersAndLabels - fetchAllFolders","key":"ErrorCertificate","retryable":false,"what":"std::exception"}\n ***\n\n6289 [2017-10-06 19:39:03.653] [background] [critical] *** Stack trace (line numbers are approximate):\n *** ??:? SyncWorker::syncFoldersAndLabels()\n *** ??:? runBackgroundSyncWorker()\n *** ??:? void _Bind_simple::_M_invoke(_Index_tuple)\n *** ??:? _Bind_simple::operator()()\n *** ??:? thread::_Impl::_M_run()\n *** (unknown) clone\n ***\n\n', provider: 'gmail' } { ??:? SyncWorker::syncFoldersAndLabels() ??:? runBackgroundSyncWorker() ??:? void _Bind_simple::_M_invoke(_Index_tuple) ??:? _Bind_simple::operator()() ??:? thread::_Impl::_M_run() (unknown) clone Segfaults for me when syncing gmail.

kagashe commented on 2017-10-06 14:34 (UTC)

Thanks guys, been trying to get this to work for a couple days now.

jnylen commented on 2017-10-06 14:27 (UTC)

Thanks ahrs, I pushed it to aur.

kagashe commented on 2017-10-06 14:21 (UTC)

How do I apply the patch?

ahrs commented on 2017-10-06 11:39 (UTC) (edited on 2017-10-06 12:03 (UTC) by ahrs)

This fails to build when creating the libsasl2.so.2 symlink. Here's a patch: https://gist.github.com/anonymous/3260611e75b9ae0dccd70c42788cec03