pCloud FUSE filesystem client stopped working

Hmmm… Something in this upgrade has stopped the pCloud FUSE filesystem client working. And trying to rebuild it from AUR falls in a heap. Something to keep me busy tomorrow :thinking:

I suspect the answer’s going to be to use my rescue partition, still on the older Manjaro, and see if I can build a statically-linked version. More to learn.

[Edit]: for the benefit of anyone who also uses this and needs a purely background method, I’ve found that rclone (in the repos) provides all the necessary functionality (not just for pCloud, but for many other cloud services too). That’s certainly my way forward.

What is the name of the pkgbuild you are using?

The pcloud-drive pkbuild is electron based but there is other pkgbuilds - hence the question :slight_smile:

Interesting… I’m actually using pcloudcc-git, but as you mention, I can see pcloud-drive Electron edition. I’ll have to give that a try and see if it builds and runs. Looks like it can be installed alongside the one I have.
I’ll report back. Thanks.

[Edit]: that one does work, though it appears to have to run with a GUI, which could be a problem. But it gives me a clue, at least.

There is a longstanding pinned comment from the AUR packager on the AUR (en) - pcloudcc-git page:

Further info about AUR (en) - pcloudcc-lneely:

pamac info pcloudcc-lneely 
Name                  : pcloudcc-lneely
Version               : 20260214T1908Z-1
Description           : pcloudcc-lneely is a simple linux console client for
                        pCloud cloud storage, forked from
                        github.com/pcloudcom/console-client and independently
                        maintained.
URL                   : https://github.com/lneely/pcloudcc-lneely
Licenses              : BSD-3-Clause
Repository            : AUR
Groups                : --
Depends On            : readline zlib fuse2 mbedtls sqlite boost
Optional Dependencies : --
Make Dependencies     : udev
Check Dependencies    : --
Provides              : pcloudcc
Replaces              : --
Conflicts With        : pcloudcc-git
Maintainer            : lkn
First Submitted       : Thu 15 Aug 2024 19:38:00
Last Modified         : Sun 15 Feb 2026 07:08:29
Votes                 : 1
Out of Date           : --
2 Likes

Just for the sake of knowledge, I created a free account on pCloud.

pcloudcc-lneely/doc/USAGE.md at main · lneely/pcloudcc-lneely · GitHub

After that I used these steps

  1. Build the pcloudcc-lneely package.

    pamac build pcloudcc-lneely
    
  2. Create a local folder ~/pcloud name is irrelevant - but do require write access (I initially just used /mnt - but the client errored out)

    mkdir ~/pcloud
    
  3. Initial login

    pcloudcc -u <email-address> -p -s -m ~/pcloud
    

    -p prompt for password
    -s save password to db
    -m specify mountpoint

  4. Terminate the client using Ctrl+c

  5. Launch the client - using daemon mode

    pcloudcc -u <email-address> -d -m ~/pcloud
    
  6. Listing the folder

     $ ls ~/pcloud -l
    total 15990
    -rw-r--r-- 1 fh fh 16371465 27 feb 10:35 'Getting started with pCloud.pdf'
    drwxr-xr-x 2 fh fh     4096 27 feb 10:35 'My Music'
    drwxr-xr-x 3 fh fh     4096 27 feb 10:49 'My Pictures'
    drwxr-xr-x 2 fh fh     4096 27 feb 10:35 'My Videos'
    

I dropped some files into the ‘My Pictures’ folder - and checked the webapp - they appeared almost instantly.

I have not setup any service to mount automagically but that would be the easy part - using a systemd user service.

Doing wishful thinking about Proton Drive being as simple as that…

1 Like

Thanks. That builds, though annoyingly, my files are on a US server, which it doesn’t support. Though since I’d already had thoughts about moving my data out of that country it’s evidently time I got my act together.

It’s a really nice and simple way to manage cloud storage.
One thing that may catch people out though is that when you do a directory listing on your drive while there’s an upload in progress, it shows there as if it’s already done. though if you shut the daemon down before it’s completed a transfer, that will continue the next time you start it.
If finishing off matters to you before you close it down, watch the output for “Down: Everything Downloaded| Up: Everything Uploaded,”

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.