Arch Linux User Repository

@cirlo I contacted their support when I had trouble running pCloud in Sway with GDK_BACKEND=wayland (without ",x11"). Their response was: "Unfortunately, we are having troubles updating the app to the latest electron versions because of inside security libraries that we are using. Our devs know about this issue and electron version update is already planed."

For those experiencing segmentation faults, it might help to search for any files ending in [conflicted] and resolving those supposed conflicts (e.g., by deleting the marked file if you determine there is currently no real conflict between it and the original file).

Hey there! I've got the same problem since the last update. Is there an easy fix? Or is this something we have to wait for on pCloud's end?

FYI : After today's reboot I started getting segmentation fault:

$ pcloud 
Down: Remaining: 39 files, 75.1KB| Up: Remaining: 542 files, 13.2MB, status is SCANNING
STATUS -------------> 13
Update for linux-x64-prod-v1.10.0 is not available
Down: Remaining: 43 files, 78.3KB| Up: Remaining: 542 files, 13.2MB, status is SCANNING
STATUS -------------> 13
Segmentation fault (core dumped)

@cirlo I contacted their support when I had trouble running pCloud in Sway with GDK_BACKEND=wayland (without ",x11"). Their response was: "Unfortunately, we are having troubles updating the app to the latest electron versions because of inside security libraries that we are using. Our devs know about this issue and electron version update is already planed."

should perhaps @plague-doctor step in for unflagging the package?

Also: do you perhaps think it would be feasable for us, linux/AUR community, to ask for an update of pCloud so that they rebase it to an electron version that supports wayland (not just xwayland)?

@zeroconf --

Thanks for your notes here! I hope this helps a few people out. I agree... it'd be fantastic if pCloud could weigh in. If there was a consistent (or official) answer we could consider patching the .desktop file.

As you noticed, pCloud is not out of date, one of the commentators below erroneously flagged it out of date because of the launch issues affecting a few users. That's not what the out of date flag is for, and unfortunately, the "unflag" option here in the AUR hasn't been functional for me.

According Electron documentation suggests there could be also:

pcloud --no-sandbox​

Let us know, what worked, if any.

As pcloud is using Electron framework, this might help (having similar experience with another Electron-based app, where this solved issue, although not ideal solution):

pcloud --disable-gpu-sandbox

In my current PC the pCloud 1.9.9 works fine.

You may get hints also from Chromium CLI parameters

If issue persist, I guess it is good time to ask also from pCloud customer support and share results also here so also Arch community can benefit.

Actually wondered, why pcloud is flagged out of date as at pcloud.com is also latest version 1.9.9 - https://www.pcloud.com/release-notes/linux.html

I also only have that problem on one of two machines. Removing all pcloud folders didn't help.

Hi folks, I had the same problem as @zeroconf and @bestfriend, but the odd thing was that the segmentation fault only occurred in some of my PCs. The solution for me was to remove these subdirectories in the affected PCs: ~/.pcloud/ ~/.config/pcloud/