Package Details: proton-mail 1.6.0-2

Git Clone URL: https://aur.archlinux.org/proton-mail.git (read-only, click to copy)
Package Base: proton-mail
Description: Proton official desktop application for Proton Mail and Proton Calendar
Upstream URL: https://proton.me
Licenses: GPL-3.0-or-later
Conflicts: protonmail-desktop
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 48
Popularity: 2.84
First Submitted: 2024-06-25 22:39 (UTC)
Last Updated: 2024-12-21 18:41 (UTC)

Pinned Comments

yochananmarqos commented on 2025-02-20 17:25 (UTC)

@marchersimon: Upstream has not updated their repo for anything newer that 1.6.0. Use proton-mail-bin.

yochananmarqos commented on 2024-06-25 22:42 (UTC)

PSA: This package is now called proton-mail building from source. Please install that instead or if you prefer, the binary version is now available as proton-mail-bin.

Latest Comments

1 2 3 4 5 Next › Last »

yochananmarqos commented on 2025-02-20 17:25 (UTC)

@marchersimon: Upstream has not updated their repo for anything newer that 1.6.0. Use proton-mail-bin.

marchersimon commented on 2025-02-20 08:07 (UTC)

Hey, there is a new version available (1.7.0) and a banner within the app says, that one should upgrade to continue using the app. Thanks :)

dojero commented on 2025-01-31 23:42 (UTC)

OK. Thanks.

yochananmarqos commented on 2025-01-31 23:21 (UTC)

@dojero: You should not have had to do anything unless there's something in your local environment causing the problem.

I build in a clean chroot and cannot reproduce it. Therefore, it is not a packaging issue.

dojero commented on 2025-01-31 23:16 (UTC)

For the prepare comment that confused you, see @kalachastan comment below mine. I had to do that.

I appreciate that not everyone is getting a segmentation fault. I am. If anyone else has experienced the problem, I'd appreciate input from you as to what you've done about it.

Thanks.

yochananmarqos commented on 2025-01-31 23:03 (UTC)

@dojero:

I get a segmentation fault

I don't.

had to fix PKGBUILD prepare section

?

dojero commented on 2025-01-31 22:33 (UTC)

I get a segmentation fault running proton-mail after a 'successful' install (had to fix PKGBUILD prepare section). I'm using Wayland Sway. The seg fault occurs after 'checking for new valid version'.

Anyone know what's happening and/or how to fix it? I've got 1.06 (two versions ago) working.

kalachastan commented on 2025-01-15 09:28 (UTC)

If your installation fails in the 'prepare()' function with the error:

sharp@npm:0.33.5 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-a6b8e83e/build.log)

then you can fix this by editing the PKGBUILD file and adding 'yarn add node-gyp --dev' right before the 'yarn install' statement in your 'prepare()' function. This should fix the issue.

(@samuel-emrys, @CarloWood)

samuel-emrys commented on 2025-01-08 13:05 (UTC)

I'm seeing the same issue as @CarloWood:

sharp@npm:0.33.5 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-a6b8e83e/build.log)

CarloWood commented on 2025-01-03 12:37 (UTC)

proton-mail is failing with:

➤ YN0009: │ sharp@npm:0.33.5 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-a19873b1/build.log) ... ==> ERROR: A failure occurred in prepare(). Aborting...

Where /tmp/xfs-a19873b1/build.log contains:

This file contains the result of Yarn building a package (sharp@npm:0.33.5)
Script name: install

sharp: Detected globally-installed libvips v8.16.0 sharp: Attempting to build from source via node-gyp sharp: Found node-addon-api sharp: Found node-gyp 11.0.0 sharp: See https://sharp.pixelplumbing.com/install#building-from-source Usage Error: Couldn't find a script name "node-gyp" in the top-level (used by sharp@npm:0.33.5). This typically happens because some package depends on "node-gyp" to build itself, but didn't list it in their dependencies. To fix that, please run "yarn add node-gyp" into your top-level workspace. You also can open an issue on the repository of the specified package to suggest them to use an optional peer dependency.

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <scriptName> ...

1 2 3 4 5 Next › Last »