Thanks to Everyone here for their support… I am now officially 100% transitioned to Asahi KDE. I’m sure my workflow productivity will take a big hit for awhile, but that’s part of the fun of a new system.
Grateful for the help!
VAULT
Thanks to Everyone here for their support… I am now officially 100% transitioned to Asahi KDE. I’m sure my workflow productivity will take a big hit for awhile, but that’s part of the fun of a new system.
Grateful for the help!
VAULT
Thats called packaging ![]()
Havent packaged an RPM yet, but really have to learn it.
I installed it via https://proton.me/support/install-bridge-linux-rpm-file:
Enter the
Downloadsfolder:cd "$HOME/Downloads"Download the Bridge:
wget 'https://proton.me/download/bridge/protonmail-bridge-3.12.0-1.x86_64.rpm'Install the Bridge:
sudo dnf install './protonmail-bridge-3.8.2-1.x86_64.rpm'Note that the version of Bridge at the time of writing this is 3.12.0, however, in the future this will change, and you will need to change the versions in the commands above. If you do not do so, the Bridge should update to the newest version soon after you launch it.
However, doesn’t automatically update. Install Proton Mail Bridge on Linux | Flathub is probably preferrable.
Please do not resurrect old threads with useless information. If you installed the bridge that way, you are not on an aarch64 machine, this thread is not relevant to you, and the method you describe will not work for the people on this thread.
Or in a friendlier tone:
This is the subcategory for Fedora Asahi remix, a version that ONLY runs on Apple M-series Macs, which use arm64 / aarch64.
So as Protonmail doesnt seem to care about packaging that as an arm64 RPM (which you can ask them to do) it may not be possible.
Is that package proprietary?
@boredsquirrel, the upstream source is available (although I don’t know whether it’s FOSS) and I don’t know whether the CI is publicly available either.
Irrespective, per Arm64 Build · Issue #323 · ProtonMail/proton-bridge · GitHub, perhaps an aarch64 package now exists? I’ve been unable to locate one, but those messages are quite clear that it should.
@cmalvi @vault Sorry to resurrect this thread! I’m in the same situation and would love to get Protonmail Bridge working on Asahi on Apple Silicon. I don’t suppose you have a copy of the build you could share with me?
@valtorna, the most versatile, that I know of, is what reddit.com/r/ProtonMail/comments/1009ggu/comment/jt0jccx cites. However, it is not trivial to configure.
However, if you’re willing to utilise an alternative Asahi distribution, [1] per wiki.archlinux.org/index.php?title=Official_repositories&oldid=859480#extra, archlinuxarm.org/packages/aarch64/protonmail-bridge may be easier. If you are not, the package may operate inside a toolbox container.
…because, per the undermentioned:
…that Proton was willing to remove their entire issues section demonstrates a lack of desire to officially produce such binaries.
[self promo] You can just build it from source, I wrote an article about how to do that https://michaelrostom.dev/how-to-install-proton-bridge-on-asahi-linux-aarch64/
Have you considered packaging it for Fedora? Mail Bridge is GPL3 so there wouldn’t be any licensing issue at all.
@wrobelda, although not trivial, some support exists:
However, without anyone else in that SIG willing to maintain it, it’s a commitment.
I think that is the main issue, to keep it working and up to date. I remember while joining Fedora in the beginning the CLI Client, was the working one included it Fedora. After that it took a while till a working GUI version of the VPN Client was available.
A further issue with the mail bridge and maintaining it is, you need the payed service for that. While the Client it selves works with the free proton VPN version too. It just shows you less Server Locations as in the payed service.
@ilikelinux, you appear to be referring to the VPN client, rather than the mail client, because Mail Bridge does not support free accounts, nor does it list servers. If your interest is with the VPN client, instead, please support my cited thread.
I just wanted to add that, when the free VPN Client version already suffers from missing maintainers then even more the Proton Mail Bridge, which is not open as free service. You need to pay for this service. If a maintainer needs to pay for a service on which he develops for free/voluntarily even more difficult it is to find a maintainer.
Giving feedback to Proton, is guaranteeing that we do have a working Software (Proton Mail Bridge), even if the package is not direct from Fedora.
Sorry for the radio silence and many thanks for your help!
I’ve been trying different things over the past few days to get it working and think I won’t be able to. It looks like ProtonMail Bridge now autoupdates itself to an x86 binary and I can’t stop it. This is probably beyond me to work out – my only solution is to think about moving away from Apple Silicon …
How about packaging the CLI version only? This would be a good compromise, I suppose.
@vault, either my request shall be denied, or this might work:
Another approach might be to have Proton Mail auto-forward to another account (if you have or can get one) that is compatible with Thunderbird or whatever you use for your local email client. Then just set your from and reply-to headers to match your Proton email. But I get it – I also use Proton mail on Asahi, and it’s kind of annoying that I have to use the browser. (See also: using the browser for Proton Drive.)