@rew1red
Thanks again for the follow-up!
Edit: I just saw your patch from a few hours ago and it's basically exactly what I suggested regarding the autostart. The issue with the duplicate desktop entries as described below still remains, as you said, which is fine for me.
Regarding the DESKTOPINTEGRATION=false
, I couldn't really find any information on it's usage at all. From what I can tell, it's a flag used by "AppImageKit", but even on their GitHub there's nothing documented about it. (More about that below.)
Regarding the issue of the autostart breaking upon updates: I was able to confirm, that pCloud literally just creates an autostart entry based on the binary's filename.
So to avoid breaking the autostart the solution seems to be to install the AppImage in /opt/pcloud/pcloud-drive.AppImage
without version information in the filename, so that it can remain unchanged across updates.
What I've done in my tests:
- deactivated all existing pcloud related desktop files by moving them to *.desktop.bak
files (including the one in ~/.config/autostart/
)
- confirmed they disappeared from the GNOME launcher
- moved /usr/bin/pcloud
to /usr/bin/pcloud.bak
(the one that was symlinked /opt/pcloud/pcloud-drive-1.14.12-1.AppImage
)
- moved the "full-name" binary in /opt/pcloud/pcloud-drive-1.14.12-1.AppImage
to a *.bak
file, to make sure it's not being used by anything accidentally
- copied that file to a "short-name": /opt/pcloud/pcloud-drive.AppImage
- created a new symlink in /usr/bin/pcloud -> /opt/pcloud/pcloud-drive.AppImage
- activated the /usr/share/applications/pcloud.desktop
file again (the one that this AUR package created, referencing /usr/bin/pcloud
in Exec
)
- started pcloud through GNOME launcher
- disabled autostart in preferences, applied, enabled autostart again, applied
- ~/.config/autostart/pcloud-drive.AppImage.desktop
got created by the application
- restarted my system
- the autostart did indeed lead to a new ~/.local/share/applications/appimagekit-pcloud.desktop
file being created, which shoes up as an additional "pcloud" (lower-case 'c') in GNOME launcher because the ~/.config/autostart/pcloud-drive.AppImage.desktop
file doesn't include the env DESKTOPINTEGRATION=false
flag
So if I did everything correctly, that would be one possible solution to at least avoid the autostart from breaking.
As for the duplicate desktop entry: since the AppImageKit creates the file in ~/.local/share/applications/appimagekit-pcloud.desktop
maybe the solution for this PKGBUILD
is to simply put the desktop file there as well upon installation instead of in /usr/share/applications/pcloud.desktop
. That should also make the sed
patches to the desktop file pretty much obsolete and we could instead just replace AppRun
with the Exec command that otherwise would also be generated by the AppImageKit, namely "/opt/pcloud/pcloud-drive.AppImage" %U
(after my file name change of the binary). I'm not sure about best practices for AUR packages, so I would totally understand, if you'd rather not touch anything in the user's %HOME
.
The duplicate desktop entry doesn't bother me much, the autostart issue is more important to me.
I hope my tests help you out a bit. Thanks for your time!
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."