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

What's happened that after update PCloud isn't more showing in Nautilus?

fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
Down: Everything Downloaded| Up: Everything Uploaded, status is CONNECTING
STATUS -------------> 12
Down: Everything Downloaded| Up: Everything Uploaded, status is READY
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
STATUS -------------> 0
Update for linux-x64-prod-v1.8.7 is not available

Fuse3 should be supported as of 1.7.2, released back in 2019.

I'll try to replicate this crash locally.

Edit: Sure enough, I can replicate this issue. I've replaced fuse3 with fuse2.

It appears that this package requires the fuse2 package.

$ pcloud                                                                                     
/opt/pcloud/resources/app/node_modules/backtrace-node/lib/backtraceClient.js:265                  
            throw e;                                                                              
            ^                                                                                     

Error: ENOENT: no such file or directory, open 'libfuse.so.2'                                     
    at Object.fs.openSync (fs.js:577:3)                                                           
    at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:166:20) 
...

If you use grep on JSON output you rely on that API pretty printing it's output. If that changes at some point in time and compact JSON is delivered, the output would still be valid, but the PKGBUILD would fail. So it's certainly better to parse the output with jq or use another tool that understands JSON.

I've attempted to remove jq as a build dependency since it seems to be the source of some reported trouble. Hopefully that helps some folks out.

broken, cant update

@fredlins This package does use the official appimage published by pCloud.

Why u not put oficial appimage? because your pkgbuild is broken

@fredlins I can't tell from your comment if your installation s failing to import GPG keys or failing to install jq. I'm assuming it's the former.

You might want to try each of these steps independently to see if there is a more localized issue.

gpg --keyserver keys.gnupg.net --recv-keys A8F7858263C1E39480B731DCEAD4F103068DF8E5

jq is available in the community repository, so you should be able to install it with pacman (or yay based on what I'm seeing in your comment).

You are distribute broken aur package

See:

==> Remove make dependencies after install? [y/N] y :: Downloaded PKGBUILD (1/1): pcloud-drive 1 pcloud-drive (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> N :: (1/1) Parsing SRCINFO: pcloud-drive

:: PGP keys need importing: -> A8F7858263C1E39480B731DCEAD4F103068DF8E5, required by: pcloud-drive ==> Import? [Y/n] Y :: Importing keys with gpg... gpg: keyserver receive failed: No name error: target not found: oniguruma error: target not found: jq  fredlins  ~ 