You are not logged in.
pcloud-drive on the AUR: https://aur.archlinux.org/packages/pcloud-drive/
I am using kernel 5.4 due to the benefits for AMD RX 5700 users and preferably would like to continue, and I'm unsure of any other fuse issues. At least nothing comes up in the Bug Tracker or via other searches.
When running pCloud Drive via the cli this output occurs:
Down: Everything Downloaded| Up: Everything Uploaded, status is CONNECTING
Update for linux-x64-prod-v1.7.1 is not available
fuse: reading device: Invalid argument
Down: Everything Downloaded| Up: Everything Uploaded, status is SCANNING
Down: Everything Downloaded| Up: Everything Uploaded, status is READY
fuse: missing mountpoint parameter
I'm not sure exactly how the fuse mountpoint is being created here. I'd like to find that out, but I'm not sure how (the app's code doesn't give me many hints). I did reach out to pCloud's support for info, but as they don't support Arch Linux I'm not holding my breath with them.
So does anyone have any inkling to why there would be an issue on linux 5.4, and if there's a possible fix?
Offline
Just wanted to say I'm having the same issue so you're not alone. I haven't found a solution so I just rolled my kernel back to 5.3.13 for now. Let us know if you hear anything from pCloud support. Thanks.
Offline
https://git.kernel.org/pub/scm/linux/ke … 5ad5982958
is queued for 5.4.2 is the issue still present with that commit applied?
Offline
Same issue for me. Had to roll back from 5.4.1 to 5.3.13.
Offline
Thanks for the post. I have been beating my head against a wall for the last hour trying to figure out what was going on.
"Every normal man must be tempted at times to spit upon his hands, hoist the black flag, and begin slitting throats." -- H.L. Mencken
Website Configs
Forum Admin: Bruno's All Things Linux
securitybreach<a>archlinux.us
Offline
Kernel 5.4.2 was published today but I always have the same issue as previous posters...
Then, I downgraded again to 5.3.13 to have pcloud working. Any info ?
Thanks for this thread
Offline
Could someone affected bisect the kernel between 5.3 and 5.4 and find the causal commit?
Offline
Great idea, but I've never compiled a kernel and certainly not bisecting between two releases...
Offline
It appears to be this commit: fuse: require /dev/fuse reads to have enough buffer capacity (take 2), where they're now enforcing a minimum buffer size. Probably something for the pCloud devs to address. But with this commit removed pCloud Drive seems to run fine on 5.4.2.
Offline