Arch Linux User Repository

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.

Great to see the segmentation fault was not about my installation and can be fixed rather easily. I've tried the solution of setting the environment variable to X11, populating, and then switching to Wayland. It works perfectly.

For those encountering the segfault under wayland, try running it under X11:

ELECTRON_OZONE_PLATFORM_HINT=x11 proton-mail

The app seemingly cannot populate its windowBounds setting in .config/Proton\ Mail/config.json when running under wayland. Once that key is populated, the app works under wayland too.

Credit to @Joboy on the proton-mail-bin thread for the fix. Have tested and it worked for me on this version too.

Hi! I get Segementation fault when running the latest build. Here is the error when tryng to run it in a terminal:

10:40:07.401 (sentry) › Sentry DSN is not set 10:40:07.409 (main) › App start is mac: false is windows: false islinux: true version: 1.8.0 params [ '/opt/proton-mail/Proton Mail' ] 10:40:07.415 (main) › Build info: {"appVersion":"1.8.0"} 10:40:07.416 (main) › Desktop features: inapppayments:true, themeselection:true, earlyaccess:true, multiaccount:true, latestversioncheck:true, installsource:true, mailtotelemetry:false, mailtoupdate:true, esuserchoice:true, fulltheme:true, storeversion:true, heartbeatmetrics:true, statstelemetry:true, restrictedthemeselection:true, clearappmodal:true 10:40:07.593 (protocol) › Checking default mailto Can't open bumblebee display. 10:40:07.669 (protocol) › App default mailto client status { isDefault: false, wasChecked: true, shouldBeDefault: true, wasDefaultInPast: false, canUpdateDefault: true, lastReport: { wasDefault: false, timestamp: 0 } } 10:40:07.673 (update) › Initialization of update checks. 10:40:07.676 (update) › Checking for new valid version. Segmentation fault (core dumped) ..... I tried to install the snap (desperate) and now I get that it can't connect to the Wayland display. Is there no Wayland support for proton-mail maybe?

libpxbackend-1.0.so: cannot open shared object file: No such file or directory Failed to load module: /home/mgns/snap/proton-mail/common/.cache/gio-modules/libgiolibproxy.so 12:59:27.362 (main) › AppID generated { id: '670c9cbd-c962-4df2-b033-80a8d1dbb042', hash: 'abc9e7c6a266ef1805fc982507708ff21aba41de1bcf0491b9c8f413d1998fb2', distribution: 0.6710495815226769 } 12:59:27.374 (settings) › Settings not found, using default settings 12:59:27.421 (main) › App start is mac: false is windows: false islinux: true version: 1.8.0 params [ '/snap/proton-mail/21/usr/lib/proton-mail/Proton Mail Beta', '--no-sandbox', '--disable-seccomp-filter-sandbox' ] 12:59:27.425 (main) › Build info: {"idaTag":"ida-332","buildTag":"ida-332","appVersion":"1.8.0"} 12:59:27.426 (main) › Desktop features: inapppayments:true, themeselection:true, earlyaccess:true, multiaccount:true, latestversioncheck:true, installsource:true, mailtotelemetry:false, mailtoupdate:true, esuserchoice:true, fulltheme:true, storeversion:true, heartbeatmetrics:true, statstelemetry:true, restrictedthemeselection:true, clearappmodal:true 12:59:27.433 (main) › Enable check default mail to app 12:59:27.434 (protocol) › Requested to check if app default mailto. Current status: true 12:59:27.436 (protocol) › Storing default protocols: { mailto: { shouldBeDefault: true, wasDefaultInPast: false, lastReport: { wasDefault: false, timestamp: 0 }, canUpdateDefault: true } } [8290:0505/125927.448648:ERROR:wayland_connection.cc(196)] Failed to connect to Wayland display: No such file or directory (2) [8290:0505/125927.448711:ERROR:ozone_platform_wayland.cc(264)] Failed to initialize Wayland platform [8290:0505/125927.448728:ERROR:env.cc(257)] The platform failed to initialize. Exiting. [0505/125927.469567:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) Segmentation fault (core dumped)

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

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 :)

OK. Thanks.

@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.

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.

@dojero:

I get a segmentation fault

I don't.

had to fix PKGBUILD prepare section

?