Arch Linux User Repository

@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."

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.

It appears that this package requires the fuse2 package.

$ pcloud                                                                                     
/opt/pcloud/resources/app/node_modules/backtrace-node/lib/backtraceClient.js:265                  
            throw e;                                                                              
            ^                                                                                     

Error: ENOENT: no such file or directory, open 'libfuse.so.2'                                     
    at Object.fs.openSync (fs.js:577:3)                                                           
    at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:166:20) 
...

If you use grep on JSON output you rely on that API pretty printing it's output. If that changes at some point in time and compact JSON is delivered, the output would still be valid, but the PKGBUILD would fail. So it's certainly better to parse the output with jq or use another tool that understands JSON.