Arch Linux User Repository

Exactly same issues as @nasko. I tried the appimage direct from the pcloud site and it also isn't working.

I recently started experiencing a problem starting pCloud I now have aur/pcloud-drive 1.14.16-1, but the problem also manifested couple of days back, when I had 1.14.14 -

When I type pcloud in the terminal, I'm getting this output, and the app just won't start:

$ pcloud
Using TARGET_APPIMAGE /opt/pcloud/pcloud-drive.AppImage

My fastfetch output for system info: https://gist.github.com/nasko/09bd469fae4f8b54437e5f8f28b19019

@zbe

Oh that is indeed interesting! My cache still has a pcloud-drive.AppImage from May 14th... That was when we fiddled with the file name regarding the autostart issue. That was when the version number was dropped from the file name.

So this is most certainly the cause! Is there anything the package maintainer can do in this case? Seems like it might be a behavior that could be specific to yay and possible other AUR helpers aren't affected then.

Edit: Removing the old cached file did solve the problem for me as well. Hopefully we can figure out a clean solution for everybody.

@zbe / @PhiLinux

That would make sense. I had this file versioned to prevent the problem, but changed that in https://github.com/wastrachan/pkgbuilds/commit/ab7d547fe65b5b3ea1cd936e66ab7366abb5a13a#diff-c981fdfbca16f2f727447a07effa90d44861647c18d35494ea2953b27edc97edL16-R17 to try to solve the "Duplicate Desktop Entry" problem reported a while back. If there were a way to tell the app not to create it's own desktop entry, this would be moot.

I'll see what else we can do there... a clean upgrade path is important.

I think the problem is older pcloud-drive.AppImage file in .cache/yay/pcloud-drive. I got mismatched sha256sum check as well. Just delete the file, PhiLinux.

The code matches for me too so that shouldn't be the reason.

The full link I get:

https://u.pcloud.link/publink/show?code=XZwGnW5ZrhkOy46busjMNcycWKNcbV5sKHb7

Edit: I also just checked the sha256sum of the download and it perfectly matches the one from your PKGBUILD...

3dcf61e542d9b762979d6de9d6c5f9540769e2e717a691e57365632bd1f6fda3

Weird...

@PhiLinux--

That would be an alarming change. I'm hoping I just made a mistake, but the _api_code in the PKGBUILD seems correct.

You can help in fact, if you want to go to https://www.pcloud.com/release-notes/linux.html and copy the download link for the most recent version (1.14.14 (08/08/2025) | Download), the code parameter in that link should match the _api_code in the PKGBUILD (currently XZwGnW5ZrhkOy46busjMNcycWKNcbV5sKHb7 for me)

If it doesn't match anymore, it would imply that pCloud has started generating that link on the fly and I'll need to do some refactoring to try to get a unique download link at build time. I have concerns about this.

Thanks for the update to 1.14.14, however, I'm getting an error with the validity check when trying to update via yay.

I've noticed that when I try to open the new source URL from the PKGBUILD in Firefox, I get this error message:

"This link was generated for another IP address. Try previous step again."

So maybe the URL in the PKGBUILD can't work for anybody else either?! The validity check failing might just be a consequence of the download not working in that case, I'm not entirely sure.

The output where yay fails:

==> Validating source files with sha256sums...
    LICENSE ... Passed
    pcloud-drive.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/phil/.cache/yay/pcloud-drive 
     context: exit status 1 

Let me know if there's anything else I can do to help figure it out.

suspend solution here: https://bbs.archlinux.org/viewtopic.php?id=305971

and for popup for now I just created a kwin rule to keep it in the back

On a fresh install of Arch, after installing pCloud, every time I click on the pCloud tray icon in KDE Plasma, a window pops up that says:

remote control requested an application requested access to: input devices it's this bug here https://bugs.kde.org/show_bug.cgi?id=490666

more importantly pCloud is blocking suspend for me. it just freezes the whole machine have to sysrq reboot. When I killall pCloud before sleep there are no issues whatsoever. Any ideas how to fix?

@rew1red