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

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/

Same error here, happy to donate to fix

@zeroconf @bestfriend I had the same issue initially, but after a reinstall I get the following message:

osVersion -> Arch Linux x64
appVersion -> 1.9.9
init failed
Error reading OS release info: Error: Cannot find module '../screen'

@zeroconf I have a similar problem. Did you end up solving your error?

pCloud client won't start anymore :( Error message:

Segmentation fault (core dumped)

That's first time for me. Hopefully can you fix this. Possibly a kind of electron framework update... When to download from https://www.pcloud.com/how-to-install-pcloud-drive-linux.html?download=electron-64 - this will crash, too.

Longer debug log, when running via gdb (GNU Debugger)

Starting program: /usr/bin/pcloud 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Detaching after fork from child process 2535]
process 2531 is executing new program: /usr/bin/bash
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Detaching after fork from child process 2540]
[Detaching after fork from child process 2541]
[Detaching after fork from child process 2545]
process 2531 is executing new program: /tmp/.mount_pcloud9xwE7c/pcloud
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffeffae640 (LWP 2549)]
[Detaching after fork from child process 2550]
[New Thread 0x7fffef652640 (LWP 2551)]
[New Thread 0x7fffeee51640 (LWP 2552)]
[New Thread 0x7fffee650640 (LWP 2553)]
[New Thread 0x7fffede4f640 (LWP 2554)]
[New Thread 0x7fffef6d0640 (LWP 2555)]
[New Thread 0x7fffec9ff640 (LWP 2556)]
[Thread 0x7fffec9ff640 (LWP 2556) exited]
[New Thread 0x7fffec9ff640 (LWP 2557)]
[New Thread 0x7fffebadd640 (LWP 2558)]
[New Thread 0x7fffeb2dc640 (LWP 2559)]
[New Thread 0x7fffed246640 (LWP 2560)]
[New Thread 0x7fffeaadb640 (LWP 2561)]
[New Thread 0x7fffea2da640 (LWP 2562)]
[New Thread 0x7fffe9ad9640 (LWP 2563)]
[New Thread 0x7fffe92d8640 (LWP 2564)]
[New Thread 0x7fffe8ad7640 (LWP 2565)]
[New Thread 0x7fffe82d6640 (LWP 2566)]
[New Thread 0x7fffe7ad5640 (LWP 2567)]
[New Thread 0x7fffe72d4640 (LWP 2568)]
[New Thread 0x7fffe6ad3640 (LWP 2569)]
[New Thread 0x7fffe62d2640 (LWP 2570)]
[New Thread 0x7fffe5ad1640 (LWP 2571)]
[New Thread 0x7fffe52d0640 (LWP 2572)]
[New Thread 0x7fffe4530640 (LWP 2573)]
[New Thread 0x7fffe3d2f640 (LWP 2574)]
[New Thread 0x7fffe352e640 (LWP 2575)]
[New Thread 0x7fffdea50640 (LWP 2576)]
[New Thread 0x7fffde24f640 (LWP 2577)]
[New Thread 0x7fffdda4e640 (LWP 2578)]
[New Thread 0x7fffdd24d640 (LWP 2579)]
[New Thread 0x7fffdca4c640 (LWP 2580)]
[New Thread 0x7fffdc24b640 (LWP 2581)]
appVersion -> 1.9.9
[New Thread 0x7fffdba4a640 (LWP 2585)]
[Detaching after fork from child process 2586]
[New Thread 0x7fffdb249640 (LWP 2587)]
init failed
[New Thread 0x7fffed23d640 (LWP 2588)]
[New Thread 0x7fffdaa48640 (LWP 2589)]
[New Thread 0x7fffdaa27640 (LWP 2590)]
Error reading OS release info: Error: Cannot find module '../screen'