Arch Linux User Repository

NOTICE: This pkgbase is now produces two packages:

• protonmail-bridge-core: Containing the core daemon & CLI program.
• protonmail-bridge: Containing the Qt desktop application.

The second package depends on the first. If you don't have a need for the desktop application, you can now choose to only install protonmail-bridge-core.

This packaging change should be seamless and no action should be required before or after the upgrade.

Thanks to @ali.molaei and @BenTheTechGuy for the feedback regarding this change!

Just having pass installed with a key set up wasn't enough for me, I had to follow this: https://pychao.com/2020/06/10/update-on-using-protonmail-bridge-on-headless-wordpress-linux-servers/

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

Issue is with go install -v -tags=no_env github.com/therecipe/qt/cmd/

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 https://github.com/ProtonMail/proton-bridge/

By the way, I made an issue there now: https://github.com/ProtonMail/proton-bridge/issues/174

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.

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.

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

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.

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.

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.

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

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?

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 (?).

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

ArcoLinux 5.4.86-1-lts