Arch Linux User Repository

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

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 https://www.pcloud.com/how-to-install-pcloud-drive-linux.html?download=electron-64 - 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/libthread_db.so.1".
[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/libthread_db.so.1".
[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/libthread_db.so.1".
[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'

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
}

@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

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

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

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

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.

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

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.