Package Details: protonmail-bridge 2.1.3-1

Git Clone URL: (read-only, click to copy)
Package Base: protonmail-bridge
Description: Integrate ProtonMail paid account with any program that supports IMAP and SMTP
Upstream URL:
Keywords: bridge email mail protonmail protonmail-bridge
Licenses: GPL3
Conflicts: protonmail-bridge-bin
Submitter: aimileus
Maintainer: ali.molaei (PMBridge-Devs)
Last Packager: ali.molaei
Votes: 93
Popularity: 2.72
First Submitted: 2018-03-02 16:03 (UTC)
Last Updated: 2022-05-01 07:02 (UTC)

Pinned Comments

bthompson commented on 2021-06-17 04:13 (UTC)

Just having pass installed with a key set up wasn't enough for me, I had to follow this:

ali.molaei commented on 2020-04-16 07:52 (UTC) (edited on 2020-04-16 18:32 (UTC) by ali.molaei)

This package is now being built from source. if you want the binary version, use protonmail-bridge-bin package

Latest Comments

ali.molaei commented on 2022-04-22 15:59 (UTC)

Fixing cloning problem now, @chovy are you sure? I don't think it's out of date

chovy commented on 2022-04-21 20:44 (UTC)

out of date now.

serkonda7 commented on 2022-04-21 08:53 (UTC)

gives error Cloning into bare repository '/home/k0hlr4bi/.cache/yay/protonmail-bridge/proton-bridge'... fatal: remote error: The unauthenticated git protocol on port 9418 is no longer supported. Please see for more information. ==> ERROR: Failure while downloading proton-bridge git repo Aborting... -> error downloading sources: protonmail-bridge context: exit status 1

urawotlol commented on 2022-04-05 23:27 (UTC)

please add libgl as a dependency as --cli and everything else fails if you do not have libgl installed

Jmon12 commented on 2022-04-05 06:41 (UTC)

The error @bmckain mentions comes from the recent changes made definitive by github, see here. I would suggest to explicitly use https as follows (I'm not aware of other ways of proposing a contribution than through comments).

diff --git a/PKGBUILD b/PKGBUILD
index 9f58a3a..8535812 100644
@@ -19,7 +19,7 @@ conflicts=('protonmail-bridge-bin')
 options=('!emptydirs' '!strip')

 # Source to compile to a specific tag

 # Source to compile to a specific commit

bmckain commented on 2022-03-30 02:52 (UTC)

It would appear there are issues with the pkgbuild again. The error message

The unauthenticated git protocol on port 9418 is no longer supported.

is showing when I tried to upgrade to 2.1.1 from 1.8.12 or even do a clean install.

Zodigram commented on 2022-02-26 19:05 (UTC) (edited on 2022-02-26 19:10 (UTC) by Zodigram)

I keep getting this error when I try to run mkpkg (please let me know how to improve formatting if possible)

==> Starting prepare()...

make -C internal/frontend -f Makefile.local clean

make[1]: Entering directory '/home/zodi/protonmail-bridge/src/proton-bridge/internal/frontend'

rm -f

make[1]: Leaving directory '/home/zodi/protonmail-bridge/src/proton-bridge/internal/frontend'

rm -rf ./vendor

rm -rf vendor-cache

rm -rf cmd/Desktop-Bridge/deploy

rm -rf cmd/Import-Export/deploy

rm -f build last.log mem.pprof main.go

rm -f resource.syso

rm -f release-notes/bridge.html

rm -f release-notes/import-export.html

==> Starting build()...


cd ./utils/ && ./ bridge

git clone vendor-cache/

Cloning into 'vendor-cache/'...

remote: Enumerating objects: 9446, done.

remote: Total 9446 (delta 0), reused 0 (delta 0), pack-reused 9446

Receiving objects: 100% (9446/9446), 129.24 MiB | 2.65 MiB/s, done.

Resolving deltas: 100% (4194/4194), done.

Updating files: 100% (9714/9714), done.

if [ "linux" == "darwin" ]; then cp -f "./utils/QTBUG-88600/libqcocoa.dylib" "./vendor-cache/"; fi;

go install -v -tags=no_env

go mod vendor

ln -sf /home/zodi/protonmail-bridge/src/proton-bridge/vendor-cache/ vendor/

rm -rf deploy linux cmd/Desktop-Bridge/deploy

cp cmd/Desktop-Bridge/main.go .

qtdeploy -tags=' build_qt' -ldflags '-X -X -X' build desktop

PANI[0000] failed to remove /var/tmp/.env_linux_amd64 error="unlinkat /var/tmp/.env_linux_amd64: operation not permitted"

panic: (*logrus.Entry) 0xc00009d420

goroutine 1 [running]:{0xc00009c070, 0xc000144360, {0x0, 0x0, 0x0}, 0x0, 0x0, {0x0, 0x0}, 0x0, ...}, ...)

/home/zodi/go/pkg/mod/ +0x2b3*Entry).Log(0xc00009d3b0, 0x0, {0xc0000ad9d8, 0x1, 0x1})

/home/zodi/go/pkg/mod/ +0xa8*Entry).Logf(0xc00009d3b0, 0x0, {0x895191, 0x19}, {0xc0000ada48, 0xc0000ada58, 0x4d86aa})

/home/zodi/go/pkg/mod/ +0x85*Entry).Panicf(...)

/home/zodi/go/pkg/mod/{0xc000026280, 0x19})

/home/zodi/go/pkg/mod/ +0xa5{0x875417, 0x5}, 0x0, {0xc00002a004, 0x2e})

/home/zodi/go/pkg/mod/ +0x317


/home/zodi/go/pkg/mod/ +0x9b5

make: *** [Makefile:122: cmd/Desktop-Bridge/deploy/linux/proton-bridge] Error 2

==> ERROR: A failure occurred in build().


Any idea what I might be doing wrong?

echo commented on 2022-02-05 07:06 (UTC) (edited on 2022-02-22 23:59 (UTC) by echo)

With 2.1.0 I am getting /usr/bin/ld: cannot find -lGL adding glu to to makedepends it was able to compile without issue.

iyanmv commented on 2022-02-03 17:13 (UTC) (edited on 2022-02-03 17:14 (UTC) by iyanmv)

Even though 2.1.0 is marked as pre-release in github, they are rolling out that version through their official updater. Also, their PKGBUILD also points to this version.

Edit: Ups, just read comments below... okay, I see they are not very consistent. No rush, we can wait till they change the flag in the following days.

ali.molaei commented on 2021-12-14 14:04 (UTC)

@mjandrews I opened an issue for it:

mjandrews commented on 2021-12-06 20:06 (UTC) (edited on 2021-12-06 20:06 (UTC) by mjandrews)

With regard to the inconsistent information about releases (i.e. GitHub listing v.1.8.12 as pre-release yet it being listed as the latest official binary elsewhere, etc), I was going to open an Issue on GitHub (as suggested by @ali.molaei), but they want a specific template to be used for Issues (understandably) and it did not look like my query would be welcome. On the template, however, they do say to contact for matters that don't fit the template. So I did that. I will report back if I learn something that clarifies the situation.

ali.molaei commented on 2021-12-06 15:43 (UTC)

@mjandrews Thanks for your reply.

I understand, and this happened before too, maybe it's better to have a conversation about it with the developers on protonmail's github

You are right, If it is a pre-release, why notifying to update and put it on the website, If it is a final release, why is the github tag wrong?

The team on github is pretty active and will almost answer within a day or so, and fix the issues, I appreciate if you start the conversation there

mjandrews commented on 2021-12-06 15:28 (UTC)

@ali.molaei I take your point. Just to provide some context, today the gui app started saying my version out of date and nagging me to update. I did what I described below with PKGBUILD and now the app is happy again. Also here it lists 1.8.12 as the latest version. I see now, and it not notice before, that on GitHub 1.8.12 is listed as pre-release and 1.8.10 is "Latest", but something funny is happening if a) the app itself is nagging me to get the latest version and b) the official binaries are 1.8.12 not 1.8.10. It seems like an inconsistency to me and maybe that just have not flagged 1.8.12 as "Latest" on GitHub but are seemingly treating it as the stable version everywhere else.

ali.molaei commented on 2021-12-06 14:52 (UTC)

@mjandrews This package has never been on the latest commit, this is the latest stable release, and 1.8.11, 1.8.12 releases are marked as "Pre-release" on Github ( so, this package is up-to-date in my opinion; if you want an up-to-latest-commit package I recommend you to create a separate protonmail-bridge-git package.

About the commit being used for this package, it is one commit after the 1.8.10 which is just fixing go.sum file which was preventing the package from being compiled. it will be replaced by a tag when another stable release is available.

mjandrews commented on 2021-12-06 14:46 (UTC)

Here's my patch of PKGBUILD to get it working with latest version as of December 6, 2021

From 497bd49c4ef955472b1db97dba07710b44a54585 Mon Sep 17 00:00:00 2001
From: Mark Andrews <>
Date: Mon, 6 Dec 2021 14:40:59 +0000
Subject: [PATCH] Use latest commit from upstream Git repo

Bump latest version to 1.8.12
 PKGBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index fbcfcf1..56ea4a2 100644
@@ -3,7 +3,7 @@
 # Contributor: aimileus <me at aimileus dot nl>

 pkgdesc="Integrate ProtonMail paid account with any program that supports IMAP and SMTP"
@@ -23,7 +23,7 @@ options=('!emptydirs' '!strip')
 #        "protonmail-bridge.desktop")

 # Source to compile to a specific commit


t3pfaffe commented on 2021-11-08 18:27 (UTC) (edited on 2021-11-08 18:28 (UTC) by t3pfaffe)

I was also failing to update/install in the same way as @rockryeidel but on paru. I tried the usual cache cleaning/rebuild methods with paru --redownload --rebuild <pkg_name> and paru -Scc to no avail.

The solution I found was to remove (or more cautiously move it elsewhere) the ~/.cache/paru/clone/protonmail-bridge/ directory and its contents

ali.molaei commented on 2021-11-05 11:43 (UTC)

@rockryeidel can you try a clean build? I'm not familiar with pamac, but you can download the PKGBUILD on your system and put it in a package, then run makepkg in that folder and see if it builds?

Archking commented on 2021-11-05 08:06 (UTC)

No pgp in this package is prompted to enter the key ring and hopes to be repaired. Or can it be poured manually? How much is it

rockryeidel commented on 2021-11-03 21:42 (UTC) (edited on 2021-11-03 22:29 (UTC) by rockryeidel)

I am getting this error when attempting updated from 1.8.10-1:

ERROR: /var/tmp/pamac-build-rockyreidel/protonmail-bridge/proton-bridge is not a clone of Aborting...

Any advice on further troubleshooting this? I don't believe there are any modifications on my build.

Update: Resetting the package build files resolved this. I must have had some edits to my build files previously.

lbravo commented on 2021-11-02 18:42 (UTC)

I can confirm it works now, thank you for the really quick fix!

ali.molaei commented on 2021-11-02 18:25 (UTC)

@lbravo Thanks for letting me know, this should be working now

lbravo commented on 2021-11-02 18:06 (UTC)

Dear maintainer,

I've had the following error while building the package:

Cloning into bare repository '/tmp/protonmail-bridge-5963774757701969506/protonmail-bridge/proton-bridge'... fatal: remote error: The unauthenticated git protocol on port 9418 is no longer supported. Please see for more information. ==> ERRO: Falha ao baixar o repositório proton-bridge do tipo git Abortando...

Thank you

brittAnderson commented on 2021-10-31 10:08 (UTC)

At the protonmail website you can download a package build for 1.8.10. I only needed qt5-quickcontrols as an additional dependency. It will change the package name to protonmail-bridge-bin.

ali.molaei commented on 2021-06-25 14:28 (UTC)

1.8.7 is flagged as pre-release on GitHub so I think this is the latest release

bthompson commented on 2021-06-17 04:13 (UTC)

Just having pass installed with a key set up wasn't enough for me, I had to follow this:

ali.molaei commented on 2021-05-21 21:08 (UTC)

Sorry, it's fixed now

eimis commented on 2021-05-21 21:03 (UTC)

@iyanmv thanks that worked

iyanmv commented on 2021-05-21 21:01 (UTC)

eimis: just copy the same line at the beginning of build() and it should work.

iyanmv commented on 2021-05-21 20:59 (UTC)

It looks like the trick in prepare() doesn't work anymore

export PATH=$PATH:$(go env GOPATH)/bin/

iyanmv commented on 2021-05-21 20:54 (UTC)

eimis: same problem here.

eimis commented on 2021-05-21 19:49 (UTC)

hello, is this just for me, qtdeploy executable not found, not sure what provides it

remote: Total 9446 (delta 0), reused 0 (delta 0), pack-reused 9446
Receiving objects: 100% (9446/9446), 129.24 MiB | 19.65 MiB/s, done.
Resolving deltas: 100% (4194/4194), done.
Updating files: 100% (9714/9714), done.
if [ "linux" == "darwin" ]; then cp -f "./utils/QTBUG-88600/libqcocoa.dylib" "./vendor-cache/"; fi;
ln -sf /home/eimis/.cache/yay/protonmail-bridge/src/proton-bridge/vendor-cache/ vendor/
rm -rf deploy linux cmd/Desktop-Bridge/deploy
cp cmd/Desktop-Bridge/main.go .
qtdeploy -tags=' build_qt' -ldflags '-X -X -X' build desktop
make: qtdeploy: No such file or directory
make: *** [Makefile:148: cmd/Desktop-Bridge/deploy/linux/proton-bridge] Error 127
==> ERROR: A failure occurred in build().
error making: protonmail-bridge

Spixmaster commented on 2021-05-01 04:55 (UTC) (edited on 2021-05-01 18:12 (UTC) by Spixmaster)

I was not aware of these serious issues.

I need to say. Protonmail Bridge is the worst software I have installed on my computer. I know that this has nothing to do with the AUR packager. It just breaks regularly. You can be sure at this moment that there will still be issues in the future. Protonmail Bridge does not respect system settings like window decorations, theme and settings like window wobbling when moving it. Their versioning sucks and is not understandable. The repository hosts 2 pieces of software and I seriously do not know to which software the tags refer. They had a convention with prefixes "br-" for Bridge and "ie-" for Import-Export but they do not even follow it anymore. The GUI has even more problems. I notice every time that if I lost the Internet connection and press the reconnect button on the GUI the complete window is not responsive anymore, not a little bit. It cannot be moved, no buttons can be pressed, nothing.

Do not they test their software before publishing it? Does anyone feel responsible for all these issues on the developer side?

I may consider switching to the no GUI version like I did with the VPN software. I will not even start talking about that. It is even worse for Linux. For Windows, it is great though.

ali.molaei commented on 2021-04-30 15:25 (UTC)

@eimis yes it's the problem, and more than that, 1.7.0 and 1.7.1 are marked as pre-releases


eimis commented on 2021-04-30 14:38 (UTC)

Version 1.7.1 is already out. Where is the problem with updating?

maybe this:

Updating files: 100% (9714/9714), done.
if [ "linux" == "darwin" ]; then cp -f "./utils/QTBUG-88600/libqcocoa.dylib" "./vendor-cache/"; fi;
go install -v -tags=no_env
/home/eimis/go/pkg/mod/ no required module provides package; to add it:
    go get
/home/eimis/go/pkg/mod/ no required module provides package; to add it:
    go get
make: *** [Makefile:180: prepare-vendor] Error 1
==> ERROR: A failure occurred in prepare().

Spixmaster commented on 2021-04-30 10:21 (UTC)

Version 1.7.1 is already out. Where is the problem with updating?

ali.molaei commented on 2021-04-25 16:57 (UTC)

I am aware of 1.7.0 but there are some issues building the package, waiting for upstream to resolve it

ali.molaei commented on 2021-04-03 06:34 (UTC) (edited on 2021-04-03 06:38 (UTC) by ali.molaei)

@iyanmv It's a little bit of a legacy that I am not downloading the tar.gz file

First, the GitHub repository didn't have tags when we started to build it from the source

Second, Sometimes we want to add a fix like the last version which we compiled from one commit after the 1.6.6 tag

Third, I think tar.gz files didn't have proper versioning sometimes, I was switched to tar.gz in 2020-05-25 and switched back to git and tags in 2020-08-14, before that it was using the tar.gz

About the build function though, you are right, I will fix that in the next version

iyanmv commented on 2021-04-02 12:50 (UTC)

Hi ali.molaei! Thanks for maintaining this package. Just a few things I saw today when installing it. Why don't you use the tar.gz from the version instead of cloning the git repo?


Also, you shouldn't build the package in the prepare function. Use build instead [1].


Spixmaster commented on 2021-03-05 05:53 (UTC)

@ali.molaei I thought my problem was a different one. Nevertheless, it is working now. Thank you for your work.

ali.molaei commented on 2021-03-04 20:22 (UTC)

@Spixmaster I'm well aware of this issue, if you read the comments, I mentioned it before :)

Actually, this commit is fixed the issue, But it's not included in the latest tag

Spixmaster commented on 2021-03-04 19:58 (UTC)

The package is not building.

go: downloading v0.0.0-20200117012304-6edc0a871e69
go: downloading v0.0.0-20200323222414-85ca7c5b95cd
/home/user/.go/pkg/mod/ no required module provides package; to add it:
        go get
/home/user/.go/pkg/mod/ no required module provides package; to add it:
        go get
make: *** [Makefile:172: prepare-vendor] Fehler 1
==> FEHLER: Ein Fehler geschah in prepare().
    Breche ab...
error making: protonmail-bridge

ali.molaei commented on 2021-03-01 09:12 (UTC)

@captainfeeny thanks for letting me know a new tag is on GitHub, but I'm not gonna update this package until this issue gets fixed

I can fix it temporarily in the PKGBUILD but I don't, the reason is it makes the PKGBUILD specific to some versions and makes it not a general script.

And also, On the website, the latest version is still 1.6.3, so I will wait until at least it changes

ali.molaei commented on 2021-02-23 06:20 (UTC) (edited on 2021-02-23 07:39 (UTC) by ali.molaei)

I've got a Flag Out-of-date message from @lpc123 with this comment:

Issue is with go install -v -tags=no_env

First, this is a comment, not an Out-of-date report, please don't do this. Second, thanks to check for the problem, but Makefile is not built by me, please report the problem upstream

By the way, I made an issue there now:

tinwasp commented on 2021-02-19 16:49 (UTC)

Same issue here: lost my account settings with my last update from 1.5.7-1 to 1.6.3-1. This may have happened before but certainly not with the last half dozen updates or so. Decided to downgrade again to 1.5.7-1; now everything's back. Not sure, what the new version does differently.

RonObvious commented on 2021-02-19 13:03 (UTC) (edited on 2021-02-19 13:05 (UTC) by RonObvious)

I've found a work-around -- but be warned, it might be dangerous.

I checked the "issues" in the github site for the bridge, and saw several things that were a little similar, but not exactly the problem we've been discussing. However, I did find a reference to the directory "~/.password-store", and found two subdirectories in ~/ .password-store/protonmail-credentials" on my machine. One of the subdirectories was rather old.

So, I tried removing the "~/.password-store" directory (or rather, I moved it to a different name, so I could restore it if needed). After restarting the bridge, and reconfiguring Thunderbird (since I now had new passwords to give to TBird), I can close the bridge and my account is still there when I restart the bridge. I also tried logging out and back in (my "normal" way to close and reopen the bridge), and my account is still there.

So, apparently, in my case at least:
1) protonmail-bridge is the only application using the "~/.password-store" directory and
2) it can get poisoned, but
3) removing it and logging in all over again (to protonmail, and then to Tbird) fixes everything.

This workaround will (obviously (?)) not work if some other application is using the "~/.password-store" directory. Presumably, just eliminating the "protonmail-credentials" subdirectory would be safer, but I can't say whether that would also fix the problem.

RonObvious commented on 2021-02-19 11:46 (UTC)

@cybr8 -- Regarding "pass init": I used my protonmail address as the 2nd argument, i.e. "pass init".

However... I'm still having problems. I can get the bridge up and running, for exactly one session, but if I "close the bridge" and restart it, my account is gone. I've tried clearing the cache and clearing the keychain (using the bridge, after "adding an account"), but I can't the bridge to restart the way it used to.

I'm not at all sure that this has to do with PKGBUILD or AUR or arch, I will go check to see if proton has some kind of website like this one -- but if any other arch/AUR users are also having this problem, and find a solution, I'd love to hear about it. Sorry for bothering everyone who is NOT having this problem.

By the way, I'm using fairly vanilla gnome, and am usng the bride with Thunderbird, for what that's worth.

cybr8 commented on 2021-02-18 09:15 (UTC) (edited on 2021-02-18 09:24 (UTC) by cybr8)

I ran into the same issue as @RonObvious and tried the "pass init" command but didn't succeed. I now get: "credential store: exit status 1: gpg: Fehler beim automatischen holen von '<my-protonmail-address>' Meldungen: Allgemeiner Fehler, Allgemeiner Fehler" still trying to fix this.

hakayova commented on 2021-02-18 03:12 (UTC) (edited on 2021-02-18 03:12 (UTC) by hakayova)

is there anyone else with the same issue?

This happens to me every once in a while with protonmail-bridge-nogui but not with protonmail-bridge. Even more commonly, i.e. with every reboot, I need to stop the bridge service, run protonmail -c confirm that I am logged in via info (occasionally I am not), quit out and restart bridge service. If I need to login again, sometimes the server password is regenerated and I have to change email client settings accordingly. It is annoying but simple to work with and provides an important service, I can live with it. I am sorry for hijacking the thread.

eimis commented on 2021-02-17 10:03 (UTC)

is there anyone else with the same issue?

just updated to 1.6.3 and it's fine, didn't ask me to log in again or anything

ali.molaei commented on 2021-02-17 09:51 (UTC)

Hey @RonObvious, I don't think there are problems with PKGBUILD, because of the fact that -bin package's PKGBUILD is almost exactly a copy of the official PKGBUILD, It looks like to be a problem with your system's default keyring/password-manager, ProtonMail-Bridge stores your passwords in gnome-keyring or pass, and if it cannot open them, then it cannot log you back in! but why it cannot open, and why it wants you to initialize it again? I don't know

And BTW, It didn't happen for me yet, that it wants me to re-login, is there anyone else with the same issue?

RonObvious commented on 2021-02-17 09:39 (UTC)

Had some problems with today's update, but the bridge seems to be running again. My account settings were gone, so I had to add my account again, i.e. enter my name and password (and 2-factor auth code). Then I got an error message telling me

"failed to add user to credentials store: exit status 1: Error: You must run: pass init your-gpg-id before you may use the password store."

(I then switched from protonmail-bridge-bin to protonmail-bridge and had the same problem). I was unsure what was meant by "your-gpg-id" but after running "pass init <my-protonmail-address>" everything worked. The bridge is back up and running. This is not the first time I had to login to protonmail all over again, but the first time I had to run "pass init". I wonder if there's a way to preserve all the settings -- or put another way, if this is a problem with protonmail's software, or with the PKGBUILD (?).

SandboxGeneral commented on 2021-01-02 17:25 (UTC)

Finally working again for me as well once the env's were commented out. Thanks.

ArcoLinux 5.4.86-1-lts

senders commented on 2021-01-02 17:23 (UTC)

@ali.molaei - the latest revision with the commented out envs worked for me.

Linux manjaro-desktop 5.9.11-3-MANJARO #1 SMP PREEMPT Sat Nov 28 09:08:57 UTC 2020 x86_64 GNU/Linux

ali.molaei commented on 2021-01-02 15:48 (UTC) (edited on 2021-01-02 15:49 (UTC) by ali.molaei)

I removed the Environment Variables suggested by Wiki for now to check it more. (although it is being built and run with no problem on my machine)

It should definitely work now because actually nothing is changed compared to 1.5.4-1

If you have problems, try a clean build and if the problem persist, let me know, thanks and sorry for problems

RonObvious commented on 2021-01-02 15:07 (UTC)

I'm having the same problem as Onoketa (et. al.).

As a (hopefully temporary) workaround, the protonmail-bridge-bin package seems to work.

Onoketa commented on 2021-01-02 06:25 (UTC)

same problem after update

ali.molaei commented on 2021-01-02 05:09 (UTC)

I think the problem is solved now

zangoku commented on 2021-01-02 01:34 (UTC)

Same error here

Spixmaster commented on 2021-01-01 19:14 (UTC)

@eimis I get the same error.

eimis commented on 2021-01-01 19:12 (UTC)

I'm getting

protonmail-bridge: symbol lookup error: protonmail-bridge: undefined symbol: _ZdlPvm, version Qt_5

after the last update. No idea x( but 2020-12-18 still builds and works fine.

ali.molaei commented on 2021-01-01 09:09 (UTC) (edited on 2021-01-01 09:09 (UTC) by ali.molaei)

@Spixmaster I can move it to src folder of the package and use go modules needed from there, but it have some downsides, Like you will be downloading go modules after each update, even if you have downloaded the latest version earlier, So I recommend you to add this line to your ~/.profile or ~/.bash_profile

export GOPATH=$HOME/.go

It will hide the default go modules folder and use .go instead of go, so you will not see it each time you build a go package

ali.molaei commented on 2021-01-01 09:01 (UTC)

@blackpoll gnome-keyring is not required for this package, it's optional, and I wonder if protonmail-bridge also works with KWallet or not, maybe ask the upstream devs on github

blackpoll commented on 2020-12-31 15:01 (UTC) (edited on 2020-12-31 15:18 (UTC) by blackpoll)

How to use this with KDE Plasma? Must I install gnome-keyring or is there another way?

Spixmaster commented on 2020-12-16 16:26 (UTC) (edited on 2021-01-01 21:17 (UTC) by Spixmaster)

Issue: With the installation a folder "go" is created in the home directory. Can this be solved? It is really annoying.

Spixmaster commented on 2020-12-13 07:02 (UTC) (edited on 2020-12-13 09:41 (UTC) by Spixmaster)

This software does not work anymore. Out of a sudden, it says that no keychain management is installed on the system although pass and gnome-keyring are both installed.

Edit: It works again! I assume that the issue was due to gnome-keyring as the update 1:3.36.0-1 to 1:3.36.0-3 solved the issue.

Dwa30v commented on 2020-11-26 08:23 (UTC)

Wonderful. Thanks you so much, @ali.molaei. Highly appreciated!

ali.molaei commented on 2020-11-26 07:30 (UTC)

Hey @Dwa30v, You can now use these packages: Compile from Source:


Dwa30v commented on 2020-11-14 09:23 (UTC) (edited on 2020-11-14 09:23 (UTC) by Dwa30v)

Hiya, Ali. Would it be possible for you to create and maintain a package for ProtonMail's Import-Export app as well?

Thank you!

Spixmaster commented on 2020-10-23 13:53 (UTC) (edited on 2020-10-23 13:54 (UTC) by Spixmaster)

The new tags just came out:

ali.molaei commented on 2020-10-23 08:09 (UTC)

@nfraprado thanks for clearing that up :)

nfraprado commented on 2020-10-22 15:15 (UTC)

For everybody wondering where the protonmail-bridge update to v1.4.4 is, as mentioned in by one of the devs, it will be merged shortly in github. So just wait a little, as the AUR package can only be updated after the release is actually added in Github :).

Spixmaster commented on 2020-10-21 12:45 (UTC)

The versioning of ProtonMail Bridge is one big mess. They do not tag and have somehow two independent projects hosted in one repo.

ali.molaei commented on 2020-10-12 08:44 (UTC)

@Spixmaster I don't know about it either, due to "" I think 1.3.3 is still the latest stable release.

Spixmaster commented on 2020-10-10 08:32 (UTC)

Take a look at the new versions ( Why did they switch from v1.3.3 to ie-x.x.x? I assume that "ie" stands for import, export but as this is only a new feature would not just a new version major make more sense?

dreieck commented on 2020-08-26 08:46 (UTC) (edited on 2020-08-26 08:46 (UTC) by dreieck)

Can you move make build please to the build()-function (but making sure that all the download still happens in prepare())?

Egns commented on 2020-08-14 12:41 (UTC)

@ali.molaei thanks for the fast fix! It all works now.

Spixmaster commented on 2020-08-14 09:07 (UTC)

@ali.molaei It works now. Thanks for the fast update.

ali.molaei commented on 2020-08-14 08:30 (UTC) (edited on 2020-08-14 08:31 (UTC) by ali.molaei)

Sorry for the problems happened during this update. I tested the new version last night and it worked fine for me, but today I had login problems too!

I switched to cloning git repo and checking out the tag version instead of downloading tag tar.gz file to fix the wrong version problem. I may switch back to old method in later versions.

BTW, This is a known problem

Egns commented on 2020-08-14 08:13 (UTC)

The latest version is broken now. Can't login to protonmail-bridge any more. Login attempts fail with error "Invalid app version".

KucharczykL commented on 2020-08-14 06:16 (UTC)


That's not protonmail-bridge but protonmail-bridge-bin (different package).

huck commented on 2020-08-14 06:10 (UTC)

I was able to use the current version by installing manually.

mkdir /tmp/build && cd /tmp/build


makepkg -s --install

Spixmaster commented on 2020-08-14 06:02 (UTC) (edited on 2020-08-14 06:09 (UTC) by Spixmaster)

@ali.molaei There is not only a problem that the software states that there is a new version but one cannot even log in. It says "Invalid app version". This version is not usable. An older version needs to be used.

ali.molaei commented on 2020-08-11 15:10 (UTC)

@mranderson17 thanks.

@huck this package is being built from source

huck commented on 2020-08-11 14:12 (UTC)

Why would someone choose this protonmail-bridge package over the protonmail-bridge-bin package for installation or viceversa?

mranderson17 commented on 2020-08-08 20:38 (UTC) (edited on 2020-08-09 01:49 (UTC) by mranderson17)

@ali.molaei it looks like 1.3.2 might be a beta release according to . The git tag just doesn't have "-beta*" appended to it.

There is a v1.2.8 tag on github which would be the current version I think, at least the version number matches the binary available here as well as the version in the update now banner within the application.

EDIT: Nevermind... the mystery continues. Building v1.2.8 from the source posted to github actually builds v1.2.7:

grep VERSION proton-bridge-1.2.8/Makefile

ali.molaei commented on 2020-08-05 05:35 (UTC)

@TheCynicalTeam I don't know how to update this package as it is compiling from source, as you can see here: There is a 1.2.8-beta (Stable releases are labeled live) and a 1.3.2 (!) release!

I emailed the proton team and asked them, I think I will wait until they respond or have a (live) release.

TheRepoClub commented on 2020-08-04 10:18 (UTC) please update

ali.molaei commented on 2020-07-03 08:08 (UTC)

@k31n_n4m3 thanks for info, will fix them in 1.2.8

k31n_n4m3 commented on 2020-06-27 08:21 (UTC)

The package git is missing from makedepends. And gcc should not be in makedepends because it is in the group base-devel

KucharczykL commented on 2020-06-24 08:55 (UTC)


Yes, started getting it today but people elsewhere are reporting it in other Proton apps like VPN so it's probably not a proton-bridge issue.

eimis commented on 2020-06-24 07:51 (UTC)

anybody else getting Invalid app version while logging in? PMB shows disconnected on launch

ali.molaei commented on 2020-05-31 15:35 (UTC)

Hi @faky

Maybe this issue is relevant

faky commented on 2020-05-31 08:22 (UTC)

Hi all, i have an issue with this package. I can start it with console "protonmail-bridge" command. But then i have to leave console window opened. I cannot make it start automatically (startup applications) or via Menu shortcut - nothing happens. Anyone have a tip on how to debug/solve this?

ali.molaei commented on 2020-05-25 11:31 (UTC)

I was waiting for this package is now updated

mavrix commented on 2020-05-24 19:10 (UTC)

It does appear to be officially the current version though... It's the only version linked on with no mention of it still being beta.

ali.molaei commented on 2020-05-20 11:29 (UTC)

It seems like 1.2.7 is still in beta

KucharczykL commented on 2020-05-04 13:06 (UTC)

It seems like the icons are copied to the correct directory (/usr/share/icons/hicolor/scalable/apps) but the desktop file refers to the original location.

kausban commented on 2020-04-17 10:03 (UTC)

@ali.molaei: Ok, I had time so I made a simpler PKGBUILD that does what I need.

ali.molaei commented on 2020-04-17 07:35 (UTC) (edited on 2020-04-17 07:35 (UTC) by ali.molaei)

@kausban I don't think making dependencies optional is a good choice, people will fail to compile by default then, I don't think -cli is a bad idea, just see multiple mongodb-bin packages that are created after mine with minor changes in each ¯\(ツ)

kausban commented on 2020-04-17 07:22 (UTC) (edited on 2020-04-17 07:22 (UTC) by kausban)

@hakayova: Using the "--cli" option you can start the application without GUI. It in fact doesn't need X-server to function. I am unsure about gnome-keyring, but pass runs happily using pgp identities and a cli pinentry program.

I run an instance on my private headless server (configured over ssh) to forward a selection of emails from my "secondary" email to my private email.

I wrote the following systemd user service (placed in ~/.config/systemd/user) that launches the bridge with --cli flag inside "screen".

@ali.molaei: Thanks. I describe my setup above. I still use the "--cli" option and login using the interactive cli menu. One doesn't need to login in every time - it uses the pass (or presumably gnome-keyring) to save the login details.

I was only suggesting, commenting the sed command in your PKGBUILD and making those dependencies optional since the package can be built in that configuration as well (see the PKGBUILD I link in my previous comment). That way people can easily edit the PKGBUILD if they want the pacakge built with the 'nogui' flag.

| I suggest to create a protonmail-bridge-cli package

Didn't think its a big enough change to be a separate aur package - I can create one if people care enough though. If it doesn't make sense for you to add (its quite non standard), I can just do it for myself personally over your PKGBUILD.

ali.molaei commented on 2020-04-17 07:05 (UTC)

@kausban I changed it to be a link instead of bash script, thanks

To have a cli build, I don't understand fully how you use it in cli mode, how can you login that way? BTW, you can use protonmail-bridge -c to use it in cli mode, If you don't want to have qt dependencies, I suggest to create a protonmail-bridge-cli package (I see you have some packages under maintenance too, so you can :D). It cannot be in this package.

hakayova commented on 2020-04-16 22:31 (UTC)

@kausban: When using protonmail bridge without the gui, is it available as a daemon/user service? Or does it need to be launched by a console command and then turned off? In other words, would it be accessible via ssh when the X-server is down?

kausban commented on 2020-04-16 21:57 (UTC) (edited on 2020-04-16 22:00 (UTC) by kausban)

First off, thanks for already creating the PKGBUILD to build from source. 2 points:

  1. I noticed that the "protonmail-bridge" script installed in "/usr/bin/" is unnecessarily using bash (minor). More importantly prevents passing any command line arguments. May I suggest creating a softlink to the binary as follows:

    ln -s "/opt/protonmail-bridge/proton-bridge" "$pkgdir/usr/bin/protonmail-bridge"

  2. I run the bridge with no gui. For such use it can be built without the qt, dejavu and theme dependencies. A few commented options in the PKGBUILD can enable this. I used the following: Basically just added this in the prepare function:

    sed -i 's/pmapi_prod/pmapi_prod nogui/' Makefile

ali.molaei commented on 2020-04-16 07:52 (UTC) (edited on 2020-04-16 18:32 (UTC) by ali.molaei)

This package is now being built from source. if you want the binary version, use protonmail-bridge-bin package

eimis commented on 2020-04-15 18:27 (UTC)

I told them it was written in Go, but they didn't believe me.

noxx commented on 2020-04-15 18:25 (UTC)

regarding to the bridge is now open source available here:

ali.molaei commented on 2020-04-04 08:44 (UTC)

@blackpoll this package was not being updated, so I created -bin package, after that this repo became orphan and I adopted it, right now, there is no difference between this package and the -bin package

I emailed the official ProtonMail bridge team and gave access to both repos to them. once bridge become open-source, -bin will be downloading the bridge and packaging it from binary and this repo will build it from source

blackpoll commented on 2020-04-02 21:05 (UTC)

I don't understand which to install between this and the -bin version? Why are there two versions and what are the use cases for each one?

ali.molaei commented on 2020-03-29 08:23 (UTC)

I emailed the ProtonMail team to see if I can use this repo for building from source and keep the -bin package for binary download, waiting for their answer

ali.molaei commented on 2020-03-29 08:08 (UTC)

@mprom thanks for letting me know, I think the arch linux convention is that packages that are not building from source and just coping a binary should have a -bin at the end of them, but this repo have move votes and users using it, so, I don't know what to do with these packages and keep which one, maybe I keep both for a while and then remove one of them

mprom commented on 2020-03-29 08:03 (UTC)

@ali.molaei This package is now orphaned. Can you perhaps adopt it?

ali.molaei commented on 2020-03-21 09:23 (UTC) (edited on 2020-03-21 09:24 (UTC) by ali.molaei)

Hey there, I emailed Lenovsky a week ago about this package and I didn't hear from him/her until now, I created the protonmail-bridge-bin package that is up to date and you can use it now I also didn't use the Protonmail's official PKGBUILD because it had not copied proper icons for the application, as this package does. and the rest is the same work in both

maciex commented on 2020-03-12 10:29 (UTC)

@zakkak you are right, I haven't noticed. Thank you. So if the Proton Developers write PKGBUILD, maybe they can maintain an aur package?

digital_mystik commented on 2020-03-12 04:48 (UTC) (edited on 2020-03-12 04:48 (UTC) by digital_mystik)

@maciex it's from Protonmail themselves. There is a prompt in 1.2.3 that links to various ways to upgrade, with one being the PKGBUILD they wrote. I personally just edited the pkgver and the sha256sum in the AUR PKGBUILD to the new one in the mean time using the info from the link.

maciex commented on 2020-03-11 22:49 (UTC)

@zakkak who made PKGBUILD you've just linked?

zakkak commented on 2020-03-11 17:37 (UTC) (edited on 2020-03-11 17:37 (UTC) by zakkak)

Version 1.2.5 is now available:

hakayova commented on 2020-03-09 02:39 (UTC)

Please excuse my ignorance but why is this package flagged out-of-date? It is the last available version as far as I know.

treeshateorcs commented on 2020-01-11 19:08 (UTC)

never mind, it just crashes anyway

treeshateorcs commented on 2020-01-11 19:06 (UTC)

no service file?

commented on 2019-11-26 19:32 (UTC)

Perhaps it should be altered from optional to needed dependency.

No, I got the same error, but that's because I didn't have pass set up, protonamil-bridge can use pass as well, so it's optional which keychain will you use.

If you don't want gnome-keyring then install pass

pacman -S pass

And then initialise it with your key (if you don't use pass , just create a new key)

pass init

Then restart protonmail-bridge and it will work.

Too bad they don't use KDE's manager but that is not something to say here but to the Protonmail developers.

RonnyD commented on 2019-10-07 15:49 (UTC)

I got the error "Incorrect Mailbox password". After contacting the support, I got the info to install gnome-keyring.

As I am running KDE, it was not installed by default. Installing it solved the problem. Perhaps it should be altered from optional to needed dependency.

CaptainVascular commented on 2019-08-26 17:57 (UTC)

If you're like me and always want the latest beta as soon as it comes out, feel free to use my script:

It pulls the current official PKGBUILD directly from and runs makepkg if it has changed.

eimis commented on 2019-07-20 08:54 (UTC)

if you're an XFCE user you might've noticed that the system tray icon doesn't always show after XFCE starts. I've come up with a workaround script that has to be set in the 'Session and Startup' instead of protonmailBridge directly.

grunch commented on 2019-07-11 13:44 (UTC)

1.1.6 Works as expected here (with Evolution and Thunderbird). Thanks for committing the latest stable!

Lenovsky commented on 2019-07-07 17:49 (UTC)

The latest stable version is still 1.1.5 as soon as 1.1.6 will be promoted to stable, I'll update the package.

ksc commented on 2019-07-07 10:36 (UTC) (edited on 2019-07-07 10:38 (UTC) by ksc)

The received email (07/02/2019)from the ProtonMail team with packages for 1.1.6-1 have attachments that are not up-to-date. However, the links provided in the email are 1.1.6-1.

Works perfectly with makepkg to build the new 1.1.6-1 version.

Maybe have this new version uploaded here?

hakayova commented on 2019-07-06 01:01 (UTC)

+1 for creating the package for 1.1.6-1. I wish I could help instead of requesting. Thanks in advance!

grunch commented on 2019-07-04 02:57 (UTC)

I received email from the ProtonMail folks announcing the availability of version 1.1.6 for Linux. Here's the link:

autodidact commented on 2019-05-25 03:19 (UTC) (edited on 2019-05-27 21:27 (UTC) by autodidact)

"ProtonMail Bridge is not able to detected a supported password manager (pass,gnome-keyring). Please, install and setup supported password manager and restart the application"

pass only seems to work temporarily when using multiple addresses mode... Account dissapears, pass rm -rf protonmail-credentials, reboot, and then re-run seems to allow me to log in again temporarily.

Note: two factor auth is enabled on my account

Will do testing with gnome-keyring as suggested by above error seeing as pass is not working well.

Update: After installing gnome-keyring and updating my ~/.xinitrc things seem to be working as expected.

I didn't have much success in pass being reliable.

hughw94 commented on 2019-05-23 08:26 (UTC) (edited on 2019-05-23 08:28 (UTC) by hughw94)

I am able to download the 1.1.5-1 package but the .deb file fails the sha256 check. Could be corrupted or an incorrect signature. I have contacted to ask them to check the checksum.

latgarf commented on 2019-05-22 22:22 (UTC) (edited on 2019-05-22 22:24 (UTC) by latgarf)

Is the problem I've encountered worth someone's attention? Looks like file protonmail-bridge_1.1.5-1_amd64.deb is not available from protonmail's site...

$ makepkg -si ==> Making package: protonmail-bridge-bin 1.1.5-1 (2019-05-22T22:18:33 UTC) -> Downloading protonmail-bridge_1.1.5-1_amd64.deb... curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading

robotshateme commented on 2019-05-22 20:29 (UTC)

Dear ProtonMail Supporter,

An updated ProtonMail Bridge version for Linux is now available. You can find the links to the deb and rpm packages here:

If your package system does not support deb, rpm or PKGBUILD, you can either extract the binaries from deb file (see or let us know what package system you use.

We're looking forward to hearing your feedback at

Lenovsky commented on 2019-05-22 20:09 (UTC)

@robotshateme, are you sure? It looks that the v1.1.5 is still unavailable ;)

robotshateme commented on 2019-05-22 10:17 (UTC)

1.1.5-1 out today

hakayova commented on 2019-04-26 14:57 (UTC)

@eimis Thank you for the lead. I will check it out and see what I can achieve. I will keep this forum informed.

eimis commented on 2019-04-26 13:24 (UTC)

@hakayova Check out xvfb-run, have it execute "/usr/lib/protonmail/bridge/protonmail-bridge --no-window". That can be put into a .service file. Basically, xvfb-run runs GUI apps under a fake X server. If you come up with a pretty .service file, maybe Lenovsky could put it into this package (service disabled by default of course)

hakayova commented on 2019-04-26 13:18 (UTC)

Is there a way to run protonmail-bridge as a systemd service without GUI? I prefer to logout from KDE but would like to be able to sync emails in the background. I reached out to the protonmail-bridge team and they haven't responded yet.

hakayova commented on 2019-04-23 04:32 (UTC)

Thank you for providing this package. It installs and works well for me.

kflak commented on 2019-04-06 12:30 (UTC)

This just in from Protonmail (1.1.4 is not yet publicly available, but I sent them a mail asking them kindly to put it up as soon as possible for the benefit of us arch creatures):


We've just released our Bridge beta build version 1.1.4. This build should contain a fix for the constant re-download of messages in the email client and higher CPU usage. Sync performance is also improved and the sending error from Apple Mail (error: encoding for ") when trying to send a blank message is resolved.

The builds for Windows and Mac are on the links below: • win: • mac:

If you're using Linux, please let us know so we can send it to you right away when it's ready. Note that once you've installed this build, you will receive new incoming updates for the beta build. If you want to unsubscribe from the beta, you will need to reinstall the Bridge app on your device by using the current live version here:

Apologies to have kept you waiting with the beta version of the Bridge app and for the issues that you've experienced with the latest version of the Bridge app.

If the issue still persists on your device or if you're experiencing another issue, please let us know by replying here so we can assist and debug it further.

Looking forward to your reply!

Best Regards, The ProtonMail Team

eimis commented on 2019-03-05 14:32 (UTC) (edited on 2019-03-05 15:55 (UTC) by eimis)

@ak-il kinda unsurprising, because IME the bridge app on Linux has been buggy since release

EDIT actually 1.1.3 is out you only need to change the pkgver

alexkubica commented on 2019-03-05 13:56 (UTC) returns 404, and it seems protonmail disabled the download for linux on:

Lenovsky commented on 2019-02-13 11:48 (UTC)

Thanks for all the helpful information. The package will be updated soon.

fbarriga commented on 2019-02-13 11:08 (UTC) (edited on 2019-02-13 11:15 (UTC) by fbarriga)

Please update to 1.1.1-1: _pkgver=1.1.1 _pkgrel=1 sha256sums=('5744fb4efadaf30be0511b0cc6ceef53e5562175d0a1c09db81d7b91bef71a91')

And the following files has been renamed: - Desktop-Bridge.desktop -> ProtonMail_Bridge.desktop - Desktop-Bridge.svg -> ProtonMail_Bridge.svg

hughw94 commented on 2019-02-12 13:34 (UTC) (edited on 2019-02-12 13:34 (UTC) by hughw94)

Just to say that the newest PKGBUILD provided by ProtonMail (send to me via email), seems to have changed some parameters and the command to run the program has changed from Desktop-Bridge to protonmail-bridge. When I updated using their PKGBUILD, I ended up with duplicate packages that caused all sorts of problems. Not sure whether this will affect the AUR package?

mranderson17 commented on 2019-02-11 18:00 (UTC)

looks like new download link is


tomjshore commented on 2019-02-07 22:22 (UTC)

I did have a problem with gnome-keyring I was getting the error "No such interface ?org.freedesktop.Secret.Collection?" when logging in.

I fixed this follow this guide thanks Arch wiki

Thieso commented on 2018-12-26 15:58 (UTC) (edited on 2018-12-26 16:01 (UTC) by Thieso)

Hi, I installed the package using yay on arch linux but for some reason it doesn't start the gui. The cli interface works.

When trying to open the gui the following message appears: (Can you help me with that?) (error message too long and I can't format it here)

aimileus commented on 2018-08-23 14:03 (UTC)

Thanks, ProtonMail did not send me an email with the updated Bridge...

typewar commented on 2018-08-22 18:34 (UTC)

Link is dead.

Seems like the new link is

I have been unable to install the package on my own, I really need this to be updated

aimileus commented on 2018-07-31 18:21 (UTC)

@physkets, technically yes, but most closed sourced packages (e.g. spotify) do not include the '-bin' suffix, as proprietery software are always binaries by definition. I do not expect that ProtonMail releases the source code of the Bridge, but if they do I will update this package to compile form source.

physkets commented on 2018-07-31 06:48 (UTC)

Shouldn't the name of this package end with a "-bin"? To prepare for a time when ProtonMail release the source for the application. This package can still stay on.

eimis commented on 2018-06-29 15:01 (UTC)

This is awesome, thank you!

Aerion commented on 2018-05-22 14:52 (UTC) (edited on 2018-05-22 16:35 (UTC) by Aerion)

This updated completely wiped my ProtonMail Bridge configuration. Has anyone else experience this?

EDIT: upon further inspection it turns out that after logging into the bridge again with my PM credentials, and changing to split addresses mode I need to open the account configuration for each of my aliases again and enter new passwords into Thunderbird. Not a complete wipe, but annoying nevertheless, especially if this is going to happen with every single update.

aimileus commented on 2018-05-17 04:37 (UTC)

@gammahermit, ProtonMail just released an update, I updated the package.

gammahermit commented on 2018-05-17 00:27 (UTC) (edited on 2018-05-17 03:04 (UTC) by gammahermit)

The source package is no longer available from the protonmail site. Edit: updating the version to 1.0.4 in the PKGBUILD fixes it.

aimileus commented on 2018-05-16 17:17 (UTC)

@samhh, I would contact ProtonMail about the issue. If the issue is about a missing dependency or another packaging issue I will update the PKGBUILD, but all the dependencies in the official one are included (either explicitly or implicitly).

samhh commented on 2018-05-16 16:06 (UTC)

No luck for me, seems to hang for a while at "Adding account" before giving up and going back to the home screen sans new account.

aimileus commented on 2018-03-10 15:14 (UTC)

@frenchbeard, wjhandley, you seem to be correct, I added gnome-keyring as a dependency.

frenchbeard commented on 2018-03-09 12:30 (UTC) (edited on 2018-03-09 12:30 (UTC) by frenchbeard)

I can confirm the same behaviour here, requires gnome-keyring to finalize any account addition. Will check further tonight to see if it actually requires gnome-keyring or just any gcr compatible keyring.

wjhandley commented on 2018-03-05 21:02 (UTC)

In order to get this package to work, I had to install gnome-keyring. Without it, I was unable to add accounts, either via the cli or the gui, merely getting back to 'no accounts added' without any further feedback.