| 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: | plague-doctor (rew1red) |
| Last Packager: | rew1red |
| Votes: | 73 |
| Popularity: | 0.93 |
| First Submitted: | 2017-04-27 21:39 (UTC) |
| Last Updated: | 2023-05-30 03:42 (UTC) |
@DiV21dSREL I contacted pCloud support who got me to reproduce the crash with a debug version and then told me:
Your case was forwarded to the developers and we'll probably have a fix with the next pCloud Drive version for Linux. We'll get back to you as soon as possible.
I did a system update today and now every time I launch pcloud-drive I get the following error:
pCloud Drive is not mounted
init failed
Error reading OS release info: TypeError: Cannot read property 'substring' of undefined
Any clue what I might be doing wrong? Sway on ArchLinux, fully up to date.
Please add libappindicator-gtk3 as an optional dependency for tray menu.
Since about a week ago I'm seeing this error or similar: /tmp/.mount_pcloudVoT5Jx/pcloud: symbol lookup error: /usr/lib/libcairo.so.2: undefined symbol: FT_Get_Color_Glyph_Layer Is anyone else having a similar problem?
curl: (22) The requested URL returned error: 410 ==> FEHLER: Fehler beim Download von https://p-def2.pcloud.com/cBZ0SKsydZa6UFOrZZZdByTo7Z2ZZgC0ZkZUD0DVZVHZbZe4ZGLZTzZNzZTHZv0ZQ4Z4JZt5Z0LZG5ZWJZyc9wVZJS3ud4BYz6zFxs60znqqSVgPIs3X/pcloud Breche ab... :: Unable to build pcloud-drive - makepkg exited with code: 1 =>> Try again? [y/N]:
In 'Arch-like' Manjaro XFCE, pcloud-drive is a headache, especially with 2FA enabled. On my.pcloud.com site, each client login gets a token that's good for one calendar year. If you don't login every week or so, the client has to log back in.
Lately, when that happens, I get to the username entry and see a popup that says [bad login] before I type anything. I know that means I need to close pcloud (check the task manager and kill any running instance), then open a console and type rm -rf ~/.pcloud ~/.config/pcloud then pcloud.
It's like a brand new login, so a new token will be assigned and a new device will be registered on the security tab. This is, however, the only reliable way I've found to get logged in. It's also very important to wait patiently and not click any buttons a second time during the logon process.
@theDrake Thank you! Might be a bit early to be sure. Maybe I missed some [conflicted] files. But it seems to be working for now.
For those experiencing segmentation faults, it might help to search for any files ending in [conflicted] and resolving those supposed conflicts (e.g., by deleting the marked file if you determine there is currently no real conflict between it and the original file).
Hey there! I've got the same problem since the last update. Is there an easy fix? Or is this something we have to wait for on pCloud's end?
FYI : After today's reboot I started getting segmentation fault:
$ pcloud
Down: Remaining: 39 files, 75.1KB| Up: Remaining: 542 files, 13.2MB, status is SCANNING
STATUS -------------> 13
Update for linux-x64-prod-v1.10.0 is not available
Down: Remaining: 43 files, 78.3KB| Up: Remaining: 542 files, 13.2MB, status is SCANNING
STATUS -------------> 13
Segmentation fault (core dumped)
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."