Package Details: protonmail-bridge 3.10.0-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 (Qt desktop application)
Upstream URL:
Keywords: bridge email mail protonmail protonmail-bridge
Licenses: GPL-3.0-only
Submitter: aimileus
Maintainer: ali.molaei (PMBridge-Devs, BenTheTechGuy, carsme)
Last Packager: BenTheTechGuy
Votes: 106
Popularity: 2.27
First Submitted: 2018-03-02 16:03 (UTC)
Last Updated: 2024-03-21 17:22 (UTC)

Pinned Comments

carsme commented on 2023-12-08 22:34 (UTC) (edited on 2023-12-08 22:35 (UTC) by carsme)

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!

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:

Latest Comments

1 2 3 4 5 6 .. 27 Next › Last »

chardon_cs commented on 2024-04-05 14:46 (UTC) (edited on 2024-04-05 14:46 (UTC) by chardon_cs)

@ali.molaei It doesn't work... :(

I guess maybe there is something with Proton's go-crypto upstream idk.

ali.molaei commented on 2024-04-03 08:52 (UTC)

@chardon_cs It's building fine for me, try cleaning your go cache and try again?

chardon_cs commented on 2024-04-02 01:53 (UTC)

Hmm... Got this error.

go: invalid version: unknown revision edf196117233
==> ERROR: A failure occurred in prepare().
error: failed to build 'protonmail-bridge-3.10.0-1 (protonmail-bridge-core protonmail-bridge)':
error: packages failed to build: protonmail-bridge-3.10.0-1 (protonmail-bridge-core protonmail-bridge)

zangoku commented on 2024-03-23 18:37 (UTC)

@ Nocifer thank you that worked nicely!

s1gtrap commented on 2024-03-23 12:06 (UTC)

I'm getting something similar to @rev.cressy below:

make[2]: *** No rule to make target '/home/s1g/.cache/yay/protonmail-bridge/src/proton-bridge-3.10.0/internal/frontend/bridge-gui/bridgepp/bridgepp/GRPC/brmdge.pb.h', needed by 'bridgepp/CMakeFiles/bridgepp_autogen_timestamp_deps'.  Stop.
make[1]: *** [CMakeFiles/Makefile2:305: bridgepp/CMakeFiles/bridgepp_autogen_timestamp_deps.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().
-> error making: protonmail-bridge-exit status 4
-> Failed to install the following packages. Manual intervention is required:
protonmail-bridge - exit status 4
protonmail-bridge-core - exit status 4

rev.cressy commented on 2024-03-22 17:29 (UTC)

error while building after full system upgrade on Friday March 22, 2024

/usr/bin/ld: cannot find -labsl_flags: No such file or directory
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/bridge-gui.dir/build.make:591: bridge-gui] Error 1
make[1]: *** [CMakeFiles/Makefile2:170: CMakeFiles/bridge-gui.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().

Nocifer commented on 2024-03-22 08:34 (UTC)

@zangoku You need to rebuild protonmail-bridge against the latest abseil-cpp (which was updated shortly after the latest update of this package).

zangoku commented on 2024-03-21 23:57 (UTC)

No longer works since latest update, getting the following error:

protonmail-bridge: error while loading shared libraries: cannot open shared object file: No such file or directory

MTL117 commented on 2024-02-23 15:46 (UTC)

@Nocifer You are absolutely right, I hadn't thought about that! Thanks for the tips!

Nocifer commented on 2024-02-22 19:52 (UTC)

@MTL117 You could always do that export yourself in your .bashrc/.profile/etc, this would solve your issue and at the same time accommodate those of us who'd prefer keeping the downloaded Go modules stored for future rebuilds. And of course, if it's not a matter of wasted space but you simply don't want your $HOME polluted with extra folders, you could also point GOPATH to some nested folder like XDG_CACHE_HOME/go/build or some such.