[Bug]: Disabling "launch at system start" does not work

[kdarras]

• [X] This is a bug, not a question or a configuration issue.
• [X] This issue is not already reported on Github (I've searched it).
• [X] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• [X] I agree to follow Nextcloud's Code of Conduct

Bug description

I would like to stop NextCloud desktop from running at every system start, but unchecking the corresponding box in the settings does not do anything

Steps to reproduce

1. download Nextcloud-3.13.3-x86_64.AppImage
2. Make it executable and run on Ubuntu 24.04
3. uncheck the "launch at system start" checkbox in the settings
4. restart

Expected behavior

NextCloud Desktop client should NOT launch after restart

Which files are affected by this bug

Nextcloud-3.13.3-x86_64.AppImage

Operating system

Linux

Which version of the operating system you are running.

24.04

Package

Official Linux AppImage

Nextcloud Server version

don't know

Nextcloud Desktop Client version

3.13

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

• [ ] Default internal user-backend
• [ ] LDAP/ Active Directory
• [ ] SSO - SAML
• [ ] Other

Nextcloud Server logs

No response

Additional info

No response

[mtompkins]

Something troubling exists here. The binary is launched even if all startup invocations are removed so the problem extends outside of any AppImage. For example no systemd nor $USER/.config/autostart/.desktop file on linux, yet the binary will launch and revive itself if force-ably killed. It will also launch after a reboot for reasons unknown.

While I'm not claiming this, this is not an uncommon characteristic for a hijacked binary that has malware embedded.

This was while having the 3.14 client installed on archlinux as well as compiling the 3.13

Ref: https://gitlab.archlinux.org/archlinux/packaging/packages/nextcloud-client

[mtompkins]

The cause seems to be the following known issue:

https://gitlab.archlinux.org/archlinux/packaging/packages/nextcloud-client/-/issues/2

[kdarras]

Thanks for looking into this. Note that a few restarts later, this issue does not persist anymore on my system (strangely enough)...

[pktiuk]

This issue exists also on Fedora 40 (version 3.13.4) And on Pop OS with Flatpak (version 3.14.1)

[Rello]

Hello,

the client was enhanced significantly since the opening of this ticket. You can help us with a retest. If you are still encountering issues, please get back to us

[kdarras]

This has been fixed a few versions ago, thanks.

[kiplingw]

I can confirm the same issue with Nextcloud Desktop Client Version 4.0.4daily (Ubuntu). I have the "Launch on System Startup" disabled, yet the client ignores it and launches automatically regardless.

I don't believe this is an AppImage specific problem either because I am using the official binary deb package from the PPA.