| Git Clone URL: | https://aur.archlinux.org/pcloud-drive.git (read-only, click to copy) |
|---|---|
| Package Base: | pcloud-drive |
| Description: | pCloud drive. Electron edition. |
| Upstream URL: | https://www.pcloud.com/ |
| Licenses: | custom |
| Replaces: | pcloud, pcloud-git |
| Submitter: | plague-doctor |
| Maintainer: | rew1red |
| Last Packager: | rew1red |
| Votes: | 84 |
| Popularity: | 1.11 |
| First Submitted: | 2017-04-27 21:39 (UTC) |
| Last Updated: | 2024-11-20 15:39 (UTC) |
In addition to the already reported missing dependency to fuse2, pcloud seems to also have a dependency for libxss:
$ pcloud
pcloud: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
Installing libxss solved the issue of course.
I think it's missing the dependency fuse2, as I had fuse3 but not fuse2 and launching didn't work (error was missing libfuse.so.2. Also, it seems the sha sum is no longer correct.
Hi, is it possible to remove gconf dependency?
pCloud indeed has changed something in their package. md5sum has changed. No changelog available. Encrypt everything you send to the cloud! Trust no one! Encrypt! Encrypt! Encrypt!
It seems like 'pcloud' changed and fails md5sum check
I confirm the same issue that @rew1red reports below.
I'm seeing issues on 5.4.11-arch1-1 with only fuse3 (3.9.0-1) installed. It appears that pcloud-drive (1.7.2-1) is still seeking fuse2 when it starts up:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: ENOENT: no such file or directory, open 'libfuse.so.2'
at Object.fs.openSync (fs.js:577:3)
...
In my case, explicitly installing fuse2 does resolve this, but what I've found would indicate the dependency chain is broken.
Thank you!
Thanks so much plague-doctor, we appreciate it!
Pinned Comments
Zenzio commented on 2022-08-13 06:44 (UTC) (edited on 2022-08-13 06:45 (UTC) by Zenzio)
@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."