Package Details: pcloud-drive 1.9.9-1

Git Clone URL: (read-only, click to copy)
Package Base: pcloud-drive
Description: pCloud drive. Electron edition.
Upstream URL:
Licenses: custom
Replaces: pcloud, pcloud-git
Submitter: plague-doctor
Maintainer: plague-doctor (rew1red)
Last Packager: rew1red
Votes: 68
Popularity: 0.116007
First Submitted: 2017-04-27 21:39 (UTC)
Last Updated: 2022-02-22 14:22 (UTC)

Latest Comments

bestfriend commented on 2022-04-16 01:59 (UTC)

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

zeroconf commented on 2022-03-26 16:31 (UTC)

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 - 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/".
[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/".
[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/".
[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'

noabody commented on 2022-03-03 22:13 (UTC) (edited on 2022-03-08 01:53 (UTC) by noabody)

PKGBUILD uses --appimage-extract already. I fooled with it a bit and think this is workable. I'm running it now and it seems to be fine. Major issues are file/folder permissions, startup script, dependencies.

I set dirs to 755 and every file other than AppRun, pcloud to 644.

Script AppRun sets up the environment with LD_LIBRARY_PATH so we sym-link that to /usr/bin/pcloud. The appimage can create both a desktop and autostart icon which need to be modified. First, we trick AppRun into not creating a desktop icon then, update AutoLaunchLinux.js so that it statically points to /usr/bin/pcloud for the GUI AutoStart (Preferences -> Settings -> General -> Start pCloud Drive on system startup).

namcap just lists a bunch of additional dependencies based on the extracted image.

I write my own PKGBUILD for my own purposes. They aren't standards based, which means I break rules. This would just be a suggested method. Keep in mind, the extracted AppImage doubles the installation file system usage.

depends=(alsa-lib dbus-glib dbus-x11 fuse2 gtk3 hicolor-icon-theme libdbusmenu-gtk2 libindicator-gtk2 libxss nss zlib)
options=(!strip !emptydirs)
prepare() {
    chmod +x "$_appimage"
    ./"$_appimage" --appimage-extract
    find squashfs-root -type f -regextype posix-extended ! -iregex '.*/(AppRun|pcloud)' -exec chmod 644 "{}" +
    find squashfs-root -type d -exec chmod 755 "{}" +
    perl -pi -e 's|! -z \"\$DESKTOPINTEGRATION\"|1 = 1|gi' squashfs-root/AppRun
    perl -pi -e "s|(appPath =) arg.appPath|\1 \"/usr/bin/$_shortname\"|gi" squashfs-root/resources/app/node_modules/auto-launch/dist/AutoLaunchLinux.js
    rm -f squashfs-root/pcloud.png

package() {
    install -dm 755 "$pkgdir"/usr/{bin,share/{applications,icons}}
    cd "$srcdir"
    mv squashfs-root/usr/share/icons/hicolor "$pkgdir"/usr/share/icons/
    perl -pi -e "s|(Exec)=AppRun|\1=/usr/bin/$_shortname|gi ; s|(Name)=pcloud|\1=pCloud|gi" squashfs-root/"$_shortname".desktop
    mv squashfs-root/"$_shortname".desktop "$pkgdir"/usr/share/applications/
    mv squashfs-root "$pkgdir"/usr/share/"$pkgname"

    ln -rsf "$pkgdir"/usr/share/"$pkgname"/AppRun "$pkgdir"/usr/bin/pcloud

nlBcBj4 commented on 2021-11-26 18:55 (UTC)

@iwex what is that mean when you said unpack the package rather than using Appimage as a running point. Do we need do something after building pcloud package from AUR? Thanks

iwex commented on 2021-02-22 17:12 (UTC)

Hello! Please unpack the package and don't use AppImage as a running point.

zbe commented on 2020-10-27 12:12 (UTC)

Just change pcloud.desktop: Exec=/usr/bin/pcloud

fabmazz commented on 2020-10-27 11:36 (UTC)

On update, the autostart script is not updated. I have to manually edit ~/.config/autostart/pcloud.desktop to change the version of the AppImage binary

obelix1502 commented on 2020-09-23 14:57 (UTC) (edited on 2020-09-23 16:07 (UTC) by obelix1502)

I'ts the same in Manjaro-KDE with plasma:

Gtk-Message: 16:49:28.813: Failed to load module "appmenu-gtk-module" Down: Everything Downloaded| Up: Remaining: 361920 files, 257GB, status is CONNECTING fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option Down: Everything Downloaded| Up: Remaining: 361920 files, 257GB, status is SCANNING STATUS -------------> 13 Update for linux-x64-prod-v1.8.7 is not available

[RESOLVED] by installing appmenu-gtk-module.

btd1337 commented on 2020-09-09 00:12 (UTC)

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

rew1red commented on 2020-08-30 00:43 (UTC) (edited on 2020-08-30 01:28 (UTC) by rew1red)

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.

shack commented on 2020-08-29 23:05 (UTC)

It appears that this package requires the fuse2 package.

$ pcloud                                                                                     
            throw e;                                                                              

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

j0hannes commented on 2020-08-19 07:56 (UTC)

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.

rew1red commented on 2020-08-18 23:50 (UTC)

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.

tosziro commented on 2020-08-18 18:09 (UTC)

broken, cant update

rew1red commented on 2020-08-18 17:50 (UTC)

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

theduckchannel commented on 2020-08-17 17:28 (UTC)

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

rew1red commented on 2020-08-17 15:21 (UTC) (edited on 2020-08-18 17:52 (UTC) by rew1red)

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

theduckchannel commented on 2020-08-17 15:10 (UTC)

You are distribute broken aur package


==> 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  ~  

rew1red commented on 2020-08-04 23:35 (UTC) (edited on 2020-08-12 15:43 (UTC) by rew1red)

@plague-doctor how would you feel about a direct-appimage install? It'd let us leverage AppImage for the packaging tool that it is and avoid having to make changes if the underlying AppImage ever changed.

I'm proposing this.

rew1red commented on 2020-07-28 15:49 (UTC)

You'd be rolling the dice on whether or not it would work on a retry, but it won't hurt to have.

j0hannes commented on 2020-07-28 15:45 (UTC)

What about randomly selecting a link? It's not very deterministic but could help in cases where one resource fails it would eventually select a different host.

jq -r '.hosts[] + .path' | sort -r | head -n1

zbe commented on 2020-07-28 15:27 (UTC)

3) Yeah was just saying if anyone has any problems ever, that s/he can try that.

And this one works now. Thanks. =)

rew1red commented on 2020-07-28 15:23 (UTC)

1) Corrected the version introduced in the revision 2) Use HTTPS download link 3) I'm not inclined at the moment to use the second download link, since the list is an unknown number of elements.

zbe commented on 2020-07-28 15:19 (UTC)

Ah it's just http instead of https. It's super slow download though, at least for me. (it failed now during writing this) Last time I just changed .hosts[0] to .hosts[1] so it used other server provided in that json page.

I guess you could drop jq and use awk or something instead to get relevant lines.

j0hannes commented on 2020-07-28 15:16 (UTC)

But it appears to install the previous version instead of the current one.

zbe commented on 2020-07-28 15:04 (UTC)

Ok that was fast.

rew1red commented on 2020-07-28 15:01 (UTC)

I made an attempt to drop 'jq' as a build dep and made some incorrect assumptions about how download URLs are built.

I've reverted said change and am building the download URL as before.

zbe commented on 2020-07-28 14:56 (UTC)

Source doesn't work. Need to change p-def4 to some other server.

j0hannes commented on 2020-07-28 14:31 (UTC)

curl: (22) The requested URL returned error: 410 Gone

j0hannes commented on 2020-07-28 10:02 (UTC)

@rew1red, now would be the perfect time for a version bump ;)

Parintachin commented on 2020-07-26 20:42 (UTC)

Thank you @plague-doctor for the update (o:

plague-doctor commented on 2020-07-25 23:00 (UTC)

@rew1red, thanks for the offer. I am happy to have a little help. Thanks. And sorry for not attending to the this package in a timely manner, but not having much time recently.

rew1red commented on 2020-07-25 04:04 (UTC)

@plague-doctor do you have any interest in an additional maintainer just to help with pkgver bumps? Happy to offer a hand if you'd like one.

telmo commented on 2020-07-20 11:27 (UTC)

@etiennewan Thanks for the patch! The program was driving me insane, even if I set it to "never" remember me about the update it would keep showing me the popup again and again.

j0hannes commented on 2020-07-12 20:31 (UTC)

I can confirm that the patch works.

etiennewan commented on 2020-07-02 22:01 (UTC) (edited on 2020-07-03 21:28 (UTC) by etiennewan)

This patch should be enough for version 1.8.5

gr211 commented on 2020-06-27 15:12 (UTC)

now at version 1.8.5

j0hannes commented on 2020-05-30 07:12 (UTC)

now at version 1.8.4

papa33 commented on 2020-05-22 17:51 (UTC)

Hello. v1.8.3 released.

j0hannes commented on 2020-05-22 14:53 (UTC)

I have sent several bug reports. I hope things have been fixed in the new version. For now, I will download and install the current version manually until the package is updated.

maucejo commented on 2020-05-22 11:40 (UTC)

[Solved] I have installed the latest version (1.8.2) and it works!! So, I think, there is a bug in version 1.8.0.

maucejo commented on 2020-05-22 11:31 (UTC)

@henry75, thanks for the suggestion, but it doesn' work. Just for curiosity, I have tried on kunbuntu (20.04) in a virtual machine to see whether it works. And it works like a charm. I will try to investigate which dependencies is missing. I don't know if I am the sole having this issue.

henry75 commented on 2020-05-22 07:51 (UTC)

@maucejo, try this: Open your "System Monitor", search the running processes for "pcloud", end all "pcloud" processes. Try restarting pCloud.

maucejo commented on 2020-05-21 19:24 (UTC)

Hi, I am facing a strange problem with the package on a fresh install of Arch using KDE. The program is installed and started properly. However, after signing in nothing happens (no tray icon, cloud drive not mounted). I have downgraded my kernel without success. Do you have any idea? Thanks

pete_mitchell commented on 2020-04-21 06:19 (UTC)

md5sum has changed, as spotted by others in Jan. Is this a (security) worry? As I'd like to install this. Thanks.

dwzg commented on 2020-04-10 19:31 (UTC)

This program fails to start for me after installing because of missing ''. This is fixed after manually installing fuse2. Apparently the PKGBUILD lacks the necessary dependency fuse2, which should be fixed. This was already mentioned 2 months ago by @sum01

henry75 commented on 2020-03-22 22:29 (UTC)

The package always fails to start for me. First, the login window appeared but I got stuck after entering my credentials. Later, not even the login window appeared anymore. Any ideas what the issue could be/how to diagnose? All the dependencies seem installed. I installed pcloud-drive through "Add/Remove Software"

Viski commented on 2020-03-20 05:35 (UTC) (edited on 2020-03-20 05:37 (UTC) by Viski)

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: cannot open shared object file: No such file or directory

Installing libxss solved the issue of course.

sum01 commented on 2020-02-01 20:27 (UTC)

I think it's missing the dependency fuse2, as I had fuse3 but not fuse2 and launching didn't work (error was missing Also, it seems the sha sum is no longer correct.

rvlobato commented on 2020-01-21 00:16 (UTC)

Hi, is it possible to remove gconf dependency?

plague-doctor commented on 2020-01-20 23:19 (UTC)

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!

heaveaxy commented on 2020-01-18 07:55 (UTC)

It seems like 'pcloud' changed and fails md5sum check

coxackie commented on 2020-01-16 17:17 (UTC)

I confirm the same issue that @rew1red reports below.

rew1red commented on 2020-01-16 15:53 (UTC)

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

divineglobe commented on 2019-12-30 02:20 (UTC)

Thank you!

securitybreach commented on 2019-12-18 02:00 (UTC)

Thanks so much plague-doctor, we appreciate it!

coxackie commented on 2019-12-18 01:15 (UTC)

@ Reteip - many thanks. This is useful for plague-doctor to update dependencies when the package is updated.

Reteip commented on 2019-12-18 00:55 (UTC)

@coxackie Yes, working well with Fuse and Kernel: x86_64 Linux 5.4.2-1-MANJARO

coxackie commented on 2019-12-18 00:44 (UTC)

Great news - has anyone tried it with only fuse3 installed?

olddog commented on 2019-12-17 03:11 (UTC)

Through appimage, updated to 1.7.2 - works (again).

zbe commented on 2019-12-16 16:58 (UTC) (edited on 2019-12-16 17:17 (UTC) by zbe)

Apparently there is 1.7.2 out; * Added support for Fuse 3.0 and later * Added support for Kernel 5.4.0 and later

Trying to test appimage but it still says it's 1.7.1. Edit: It works now.

stoner commented on 2019-12-14 16:55 (UTC)

@securitybreach So far I used to rclone mount different cloud drives at once (with a simple bash script), mainly to have a quick overview of all my cloud storage, but I used pcloud-drive to really manage this storage space. Apparently rcloud mount is a bit to slow to replace pcloud-drive to handle with larger files. The issue with opening files is due to the fact LibreOffice f.i. tries to open the file before it is fully downloaded in the background. Yesterday I have experimented with an alternative file manager (polo-bin in AUR) with built-in support for cloud storage. Polo discovers existing rclone configs and presents them in a cloud menu for browsing (so no need to mount them first). You can add new configs by the same menu also. When opening a file from the cloud you have visual feedback the file is downloaded first (/tmp) and then opened correctly. Maybe an alternative to consider if a pcloud-drive update takes too long.

stoner commented on 2019-12-13 14:14 (UTC)

"rclone mount pdrive ..." is on a new line of course.

securitybreach commented on 2019-12-13 14:05 (UTC)

Thanks stoner

stoner commented on 2019-12-13 14:04 (UTC)

Set up a new remote first using an interactive rclone configuration session by typing 'rclone config' at the command line.

Assuming you have created a remote with the name "pdrive"

mkdir -p -v /home/user/pdrive rclone mount pdrive: /home/user/pdrive/ --daemon --vfs-cache-mode writes --allow-non-empty

I am using this in a script to mount several cloud services at once without the need to install separate applications for each. The "allow-non-empty" is optional, added to avoid errors when relaunching the script (and one or more drives are still mounted).

securitybreach commented on 2019-12-13 13:23 (UTC)

Great news, thanks coxackie!

coxackie commented on 2019-12-13 13:22 (UTC)

as I have mentioned before: pCloud devs are supposedly working on it. Today I asked again and got a response that hopefully by the end of next week there will be a new version to deal with the issue.

securitybreach commented on 2019-12-13 13:20 (UTC)

Stoner, can you give us some details on how to do that? Thanks

stoner commented on 2019-12-13 13:19 (UTC)

Using rclone mount for now as an alternative (option --vfs-cache-mode writes)

Only issue so far (as with all rclone mounted drives): opening (excel) files from a mounted drive results in an import dialog from LibreOffice. Probably the file needs to be cached first. Once that dialog closed the file can be (re)opened normally as long as the remote drive stays mounted. Maybe I should try out other caching options to solve this.

securitybreach commented on 2019-12-12 20:50 (UTC)

That sucks big time!

olddog commented on 2019-12-12 20:24 (UTC)

I opened a ticket with pCloud, they came back with the following:

Kernel 5.4 is a mainline and we still do not support it.

We will support this Kernel version with the next version of pCloud Drive app. Meanwhile, you can use your pCloud account via the website or mobile apps. Or you can downgrade your Kernel to 5.3 until the release of the new version of pCloud Drive

obelix1502 commented on 2019-12-12 11:31 (UTC)

I have exactly the same problem as tiukov under Manjaro kernel 5.3. When pcloud is mounted, I get an error message telling me that a connection node is missing. So, under XFCE, Thunar can't mount my /home.

tiukov commented on 2019-12-10 19:49 (UTC)

Doesn't mount drive on 5.4.2-1-MANJARO

securitybreach commented on 2019-12-06 15:55 (UTC)

Thanks for the info coxackie!

coxackie commented on 2019-12-06 15:44 (UTC)

The pcloud devs are working on this issue with kernel 5.4.x, I was told. Will let you know when there are news.

papa33 commented on 2019-12-06 15:36 (UTC)

Bad news. Error still persists with Linux 5.4.2-arch1-1.

jskier commented on 2019-12-03 15:48 (UTC)

LTS works okay. I submitted issue to pcloud (am subscriber), although probably irrelevant since this is kernel ~ fuse related.

coxackie commented on 2019-12-03 10:29 (UTC)

I confirm that on Linux 5.4 there is an issue with the fuse system. The issue appears also when using pcloudcc.

HanFox commented on 2019-11-30 15:13 (UTC)

Just as a heads-up, I did post about a fuse issue the other day, but I found out it it's only happening on Linux 5.4.

I see no one else reporting the issue elsewhere, and I did post on the forum, but sadly to no answer.

So, as Linux 5.4 will probably be promoted to stable soon maybe someone more clever than I can figure out the issue.

Dwa30v commented on 2019-02-14 15:21 (UTC) (edited on 2019-02-14 15:33 (UTC) by Dwa30v)

when using wget downloading the snapshot:

==> Retrieving sources...
  -> Downloading pcloud...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 81432  100 81432    0     0  60815      0  0:00:01  0:00:01 --:--:--  185k
==> Validating source_x86_64 files with md5sums...
    pcloud ... FAILED
==> ERROR: One or more files did not pass the validity check!

when using git clone all worked well.

devl_archer commented on 2019-02-13 10:13 (UTC) (edited on 2019-02-13 10:14 (UTC) by devl_archer)

the latest update does not work because of the linked source:

==> Making package: pcloud-drive 1.4.8-1 (Wed 13 Feb 2019 11:10:13 AM CET)
==> Retrieving sources...
  -> Downloading pcloud-drive-1.4.8-1...
  % Total    % Received % Xferd  Average Speed   Time    Time         Time  Current    
                                 Dload  Upload   Total   Spent             Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:--          --:--:--     0
curl: (22) The requested URL returned error: 410 Gone
==> ERROR: Failure while downloading <>
Error downloading sources: pcloud-drive

coxackie commented on 2018-12-08 21:31 (UTC)

@papa33: I was in fact experiencing similar problems, and even some more, like inconsistent files across different machines on the pcloud-drive. After I was clearing the cache and re-logging in, things would be ok for a while, but then same would happen. (Eventually reverted to dropbox for critical sync needs, and only use pcloud more for storage.) I also contacted them - they indeed give generic feedback. The problem is that the development does not seem to be open-source, and there is no way to reach the developers directly. It is too bad, because it is otherwise a great service in terms of fuse speed capability - easily overtakes everything else I have used.

papa33 commented on 2018-12-08 06:47 (UTC)

I have (it's not new) a major problem with pcloud-drive. After a few hours of use, it simply stop syncing local and remote folders (as far as I can say, it is more a problem of sync local-->remote, the remote folder is not updated any more, whatever change I do locally). I have contacted them but they avoid really answering and just keep me asking the same questions like how do you sync? --> well, I use pcloud-drive, no? what files do you sync? --> well, the usual stuff... Like duprezjm they asked me to install the debug version, but it was totally useless... Question : Anyone else with similar problems? I would like to know if I am alone (or not) with this issue. Thanks.

duprezjm commented on 2018-11-14 14:26 (UTC)

HI, I got a problem of synchronization with the last version of pcloud-drive (1.4.5) I wrote to pcloud support and they sell me a debug version to install.... But I don't know how to write (or modify) the pkbuild... Can you help me ? If, you are ok, I can ask pcloud if they are ok if I send to you the link of the debug-version... JM

coxackie commented on 2018-09-24 10:44 (UTC)

pcloud-drive (1.4.1-1) will not start if libxss is not present. Maybe it should be added as a dependency?

Muffaroo commented on 2018-09-20 19:05 (UTC)

If dependencies are installed first and it resumes trying to build pcloud-drive, it attempts to download pcloud instead of pcloud drive the first time and fails. Starting up makepkg again builds successfully. Thank you for the convenient package. Not complaining, but thought I should let you know about this issue.

papa33 commented on 2018-09-17 20:11 (UTC)

Fix for me: install sni-qt.

coxackie commented on 2018-09-17 16:48 (UTC) (edited on 2018-09-18 10:16 (UTC) by coxackie)

Same here - tray icon always missing after update to 1.4.1, even if it starts. (Also getting "init failed" sometimes.) Even when the pCloudDrive is mounted, any changes there do not seem to be saved to the drive.

Edit: Suddenly, the problems disappeared. Not sure what changed.

papa33 commented on 2018-09-17 16:41 (UTC) (edited on 2018-09-17 16:47 (UTC) by papa33)

Same problem, although "sometimes" it starts. But the tray icon is always missing (Cinnamon).

Edit : I removed /home/user/.pcloud and /home/user/.config/pcloud folders. Then it started normally (I had to login of course). But then I quit/restarted and it did not start again ("init failed").

manouchk commented on 2018-09-17 16:23 (UTC) (edited on 2018-09-17 16:24 (UTC) by manouchk)

I just upgraded to 1.4.1 and get the message "init failed" and pcloud does not start.

avernan commented on 2018-09-07 14:55 (UTC)

The package also depends on fuse2

leomao commented on 2018-09-03 07:55 (UTC)

This package also depends on gconf. This should be added into the depends list.

plague-doctor commented on 2018-08-27 17:56 (UTC)

@slot try to remove, and re-install the app. Version 1.2.2-4 is not patched.

slot commented on 2018-08-27 17:47 (UTC)

I get: "Init Failed" upon startup how do I remove the patch?

RemoteAdmin commented on 2018-08-25 08:58 (UTC)

Your download link expired

mereghost commented on 2018-08-22 08:21 (UTC)

I can confirm what dreamersbrow said. I removed the patch from the PKGBUILD and it's working perfectly, instead of crashing as saghm reported.

saghm commented on 2018-08-21 15:52 (UTC)

When I try to install this, the checksum verification fails. I assume this is just due to an incorrect update to the PKGBUILD, but it should be fixed so that users can install this package without having to disable them.

dreamersbrow commented on 2018-08-20 01:23 (UTC)

It looks like that glibc issue has been fixed. I downloaded the appimage directly from pcloud and it is now working fine.

rvlobato commented on 2018-08-18 15:34 (UTC)

Hi, the patched package started to crash down (I was using the previous version with the "glibc-fix-r-and-electron-git" from the issue: and it was working) on Arch Linux, in Manjaro I have this "pcloud: /opt/pcloud/glibc/usr/lib/ version `GLIBC_2.28' not found (required by /usr/lib/"

plague-doctor commented on 2018-08-09 21:50 (UTC)

Thanks @lisu_ml. I will incorporate your patch. A nice workaround. :-)

lisu_ml commented on 2018-08-09 02:39 (UTC)

The patch to make pcloud-drive use older version of glibc (shipped within package):

lisu_ml commented on 2018-08-08 08:08 (UTC)

More info about the issue:

lisu_ml commented on 2018-08-07 08:40 (UTC)

pcloud doesn't start for me due to segfault. It seems to be caused by recent update of glibc from 2.27-3 to 2.28-1. Downgrading glibc to 2.27-3 resolves the issue.

controlxfreak commented on 2018-07-29 22:54 (UTC) (edited on 2018-07-29 22:55 (UTC) by controlxfreak)

This appears to have a dependency on fuse as well.

I think you should add: makedepends=('jq','sed','fuse')

r0b0h0b0 commented on 2018-04-29 08:58 (UTC) (edited on 2018-04-29 08:58 (UTC) by r0b0h0b0)

Can confirm what @anilg found. The package builds only when built after cloning.

DR34D_0 commented on 2018-04-29 04:33 (UTC)

Have dependencies. Successful makepkg. See application. Doesn't do anything?<br> Am I supposed to do something special once it's installed to make it work?

HanFox commented on 2018-04-12 14:31 (UTC)


lorenzosu commented on 2018-04-12 14:24 (UTC)

This won't work as the server it used isn't reachable any more. The new binary is here:

anilg commented on 2018-03-25 06:07 (UTC) (edited on 2018-03-25 06:13 (UTC) by anilg)

Using makepkg -csi on the snapshot I got ==> Validating source_x86_64 files with md5sums... pcloud ... FAILED ==> ERROR: One or more files did not pass the validity check!

I then did git clone and tried again and that built and ran successfully.

brabes commented on 2018-01-28 09:25 (UTC) (edited on 2018-01-28 09:25 (UTC) by brabes)

Currently this install the icons and some unnecessary libs to /usr/usr/share/icons and /usr/usr/lib -- here is a fix

@@ -26,7 +26,8 @@ prepare() {
 package() {
   install -d "$pkgdir"/{/usr/bin,opt}
   cp -r "${srcdir}/squashfs-root/app" "${pkgdir}/opt/${PN}"
-  cp -r "${srcdir}/squashfs-root/usr" "${pkgdir}/usr"
+  mkdir -p "${pkgdir}/usr/share/icons/hicolor"
+  cp -r "${srcdir}/squashfs-root/usr/share/icons/" "${pkgdir}/usr/share/"
   ln -s "/opt/${PN}/${PN}" "${pkgdir}/usr/bin/${PN}"
   install -Dm644 "${srcdir}/squashfs-root/${PN}.desktop" "${pkgdir}/usr/share/applications/${PN}.desktop"
   sed -i 's/AppRun/pcloud/' "${pkgdir}/usr/share/applications/${PN}.desktop"

plague-doctor commented on 2017-12-14 02:34 (UTC)

No, it doesn't.

lipe_cantarelli commented on 2017-12-12 13:40 (UTC)

This needs lib32-gtk2 as dep.

plague-doctor commented on 2017-10-28 20:18 (UTC)

Hmmm... Not really.

HanFox commented on 2017-10-28 19:46 (UTC)

Does anyone else have an issue with the tray icon just being a white square with a small blue line on it? I had this same issue 6 months ago when this package was new so went back to the old client thinking it'd be fixed one day and it's still like that. Using KDE Plasma. If no one has any clues I'll prod the pCloud contact form.

plague-doctor commented on 2017-09-25 02:35 (UTC)

@Svea, if you could point me to the "public download page" which does not require me to use API calls, I will be more than happy to accommodate the change.

Svea commented on 2017-09-23 10:06 (UTC) (edited on 2017-09-23 10:13 (UTC) by Svea)

The md5sum of the Appimage does not match the sum in the PKGBUILD, any reason for downloading via the api url, instead of the public download page (which gets the correct sum)? EDIT: Okay, the file being downloaded is not the Appimage, so i don't know.

romain.maurer commented on 2017-08-27 22:02 (UTC)

0.4.0-2 had the same problem. I was able to install it after running "updpkgsums" though so something must still be wrong in the PKGBUILD. Cheers, Romain

romain.maurer commented on 2017-08-26 12:02 (UTC)

Hi, I got the following error trying to install using pacaur. Would that mean that the package is out of date? (sorry if this is not the right place for this type of comment...) :: Checking pcloud-drive integrity... ==> Making package: pcloud-drive 0.4.0-1 (Sat Aug 26 21:42:02 AEST 2017) ==> Retrieving sources... -> Found pcloud ==> Validating source_x86_64 files with md5sums... pcloud ... FAILED ==> ERROR: One or more files did not pass the validity check! :: failed to verify pcloud-drive integrity

ZeroBit commented on 2017-08-25 19:57 (UTC)

Excellent app. Much better than pcloud-drive. It starts minimized in tray. Thank you. What is the way to make it wait establishing Wi-Fi connection with NetworkManager in KDE before it starts? At the moment it starts (with autostart) before establishing connection and, therefore, each time asks for password

argymeg commented on 2017-08-24 03:42 (UTC)

I (and, I assume, others) received an e-mail from pCloud suggesting I move to this version of the app. I assume it's safe to remove the warning from the description?

plague-doctor commented on 2017-07-26 22:18 (UTC)

The version number 0.4.0 is still current. The official, stable version of pCloud is still in beta stage.

plague-doctor commented on 2017-04-28 20:53 (UTC)

@HanFox, Unfortunately not. There is nothing official yet, but when you go to their download page, there is this info next to Electron: "Our new (beta) application in AppImage format. Supported by all major desktop Linux distributions. Download the application, make it executable, and run! No need to install. No system libraries or system preferences are altered." I have contacted pCloud Team and been told not to use previous version as the new one is under heavy development.

HanFox commented on 2017-04-28 12:14 (UTC)

Can you point me towards a blog post or upstream repo or anything about this? All I can find is a gitlab on their site that hasn't been updated in 7 months.

plague-doctor commented on 2017-04-27 21:47 (UTC)

This version of pCloud client is no longer developed. pCloud team is working on the Electron edition which is (and will be) distributed as AppImage format. I personally hate AppImage, so I have created an AUR package: "pcloud-drive". However this is a very early beta, so all kind of black magic and voo-doo might happen.

HanFox commented on 2017-04-25 08:33 (UTC) (edited on 2017-04-26 22:58 (UTC) by HanFox)

No longer works after latest openssl update. psyncgui: /usr/lib/ version `OPENSSL_1.0.1' not found (required by psyncgui) psyncgui: /usr/lib/ version `OPENSSL_1.0.0' not found (required by psyncgui) psyncgui: /usr/lib/ version `OPENSSL_1.0.0' not found (required by psyncgui) EDIT: Quick and dirty fix for now, if anyone wants it: 1) Install libopenssl-1.0-compat from the AUR 2) Run the program with: LD_PRELOAD=/usr/lib/openssl-1.0-compat/ psyncgui

plague-doctor commented on 2017-03-22 21:26 (UTC)

Package is failing Integrity Check. Please fix

Sandman007 commented on 2016-11-29 18:08 (UTC)

Build fails. Integrity Check fails. ERROR: Integrity checks (sha256) differ in size from the source array. :: failed to verify pcloud integrity

joshg253 commented on 2016-11-01 23:28 (UTC)

As stated below, this won't remember the password. Any ideas on how to fix that?

bonbonboi commented on 2016-06-09 19:00 (UTC) (edited on 2016-06-09 19:13 (UTC) by bonbonboi)

Dead build by default, changed to 634fcec47799c2c8fd9f7cdf68bd48b135102a81fed51df58161b9984faf75f6 works with packer helper!

ginoboy commented on 2016-03-25 03:06 (UTC)

Every time you restart system need to put email and password. :(

bezerkk commented on 2016-03-09 15:22 (UTC)

Just some current namcap output you may look into to time-permitting... => [v]iew package contents [c]heck package with namcap ==> --------------------------------------------------- ==> c pcloud W: Description should not contain the package name. pcloud W: Unused shared library '/usr/lib/' by file ('usr/bin/psyncgui') pcloud E: unknown is not a common license (it's not in /usr/share/licenses/common/) pcloud W: File (.BUILDINFO) exists in a non-standard directory.

xpt commented on 2016-02-08 19:46 (UTC)

mark fuse as a dependency please

plamens commented on 2015-03-25 21:28 (UTC)

The link you are using to download the deb package is temporary and expired.