pCloud run at start-up #708
Unanswered
davidrhoderick
asked this question in
Q&A
Replies: 5 comments 4 replies
|
You can just run the AppImage directly. It should be in |
0 replies
|
There are multiple questions(?) in this issue, hence I'm replying to another one I saw:
Nope. That's not AppImageLauncher's purpose. You can set that up from your desktop environment. AppImageLauncher does not provide a reliable way to launch AppImages that would survive updates (yet), that would be a separate issue. |
0 replies
If pCloud does not properly support autostart, that's pCloud's problem. ownCloud's desktop client for instance had the same issue and needed to support AppImages explicitly. |
0 replies
|
I'll re-post this here since the other issue was a duplicate. EDIT: I later realized that I've re-edited and fixed the I'm able to reproduce this issue also. Running the
strace side effect) OLD output snippets for reference |
1 reply
|
Indeed, running strace with suid binaries can lead to a lot of misleading logging. Similarly, running it on a built AppImage also leads to a lot of problematic output. One workaround for that (which you also show) is to run these tools with |
|
After tinkering around with this a bit, it seems that something goes wrong during the AppImage FUSE mount. I've been able to replicate this behavior by trying to mount the pCloud AppImage manually. I also tried copying it into the user's homedir and forcing AppImageLauncher to integrate it first. This copied it into Then, to simulate what a normal Result: The same behavior as if we tried to launch it manually. Nothing gets mounted and it prematurely exits without starting pCloud. Running it under Expand for full
|
3 replies
|
Have you tried running It looks like this AppImage is using some non-standard (likely non-compliant) runtime, though... |
|
On my system I don't have an $ fd 'binfmt-bypass' /usr/lib
/usr/lib/appimagelauncher/libbinfmt-bypass-preload.so
/usr/lib/appimagelauncher/binfmt-bypassHere's the result when running that: $ /usr/lib/appimagelauncher/binfmt-bypass /opt/pcloud/pcloud-drive.AppImage
Using TARGET_APPIMAGE /opt/pcloud/pcloud-drive.AppImage
$ echo $?
0So it looks like the same behavior. It exits prematurely with Trying that under Expand for full
|
I'm not sure either way. However, this same I found another tool to help trace what's going on: I also checked for whether FUSE was running as a kernel module or built-in... $ lsmod | grep -i fuse
$ sudo modprobe fuse
$ lsmod | grep -i fuse
$ zgrep -E 'FUSE|CUSE|VIRTIO_FS' /proc/config.gz
CONFIG_FUSE_FS=y
CONFIG_CUSE=m
CONFIG_VIRTIO_FS=y
CONFIG_FUSE_DAX=y
CONFIG_FUSE_PASSTHROUGH=y
CONFIG_FUSE_IO_URING=y
# ^^ FUSE is already compiled into this kernelNext, I created a shell script to capture and filter a trace running the original Expand for
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Pre-submit checks
Describe the bug
Before I used AppImageLauncher, I could set up pCloud to run at start-up using a terminal command. However, since starting to use AppImageLauncher, the CLi provides no help on launching app images:
Nor are there any ways to set up an AppImage to launch on start-up:
Even setting "Start pCloud Drive on system startup" has no effect:
Expected behavior
One of the following should be possible:
ail-cli --helporail-cli --help-all, I should be able to see how to launch an application.To re-iterate, only one of those would be necessary to get this working. I can use "Startup Applications" with
ail-clito run the app the same way I would restart it using AppImageLauncher if it's not possible to configure through the AppImageLauncher GUI or if the pCloud settings can't be persisted.Steps to reproduce the issue
Screenshots
ail-clihas no manual or help outputNo ways to configure auto-startup in AppImageLauncher
pCloud Drive settings don't take affect
Distribution and desktop environment
Installed AppImageLauncher version
List of AppImages you tried
Version: 0.46.11
VSCode Version: 1.96.2
Commit: ae378be9dc2f5f1a6a1a220c6e25f9f03c8d4e10
Date: 2025-03-07T06:51:09.153Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.12.10-76061203-generic
Additional context
All reactions