[Bug]: Client autostarts even if autostart is disabled

[Razer0123]

⚠️ Before submitting, please verify the following: ⚠️

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

Bug description

I have disabled Nextcloud autostart in settings, but it keeps autostarting

Steps to reproduce

1. Disable autostart in settings
2. Reboot

Expected behavior

No autostart

Which files are affected by this bug

none

Operating system

Linux

Which version of the operating system you are running.

Fedora 39

Package

Distro package manager

Nextcloud Server version

no idea

Nextcloud Desktop Client version

3.10.0

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

Updated from a minor version (ex. 3.4.2 to 3.4.4)

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

[regulator-g]

occurs with both flatpak and native versions

removing nextcloud-client-nautilus helps but every time nautilus is launched the nextcloud desktop client starts too

opening nemo doesnt start nextcloud though

[topas-rec]

I can confirm that nextcloud client starts when Nautilus is started.
Autostart in nextcloud is disabled.

Properties of the started process are besides other:

---

When Nautilus is closed and nextcloud is quit (Menu - quit, not just closing the window) then starting nautilus again does not have the above mentioned side effect.

[regulator-g]

I think this is happening in KDE plasma/Dolphin too, noticed Nextcloud running when I didn't start it although if I quit it, it doesnt seem to start up again thankfully

[thinkORo]

How can I prevent this automatic start? Since I first have to decrypt an encrypted drive, the autostart is extremely annoying.

Hint: I'm not running on KDE but XFCE4. Therefore it seems like a general "misbehaviour".

[Imberflur]

It seems to be triggered by the cloud providers integration.

@thinkORo
I was able to at least temporarily work around it by commenting out the lines noted in #1982 (comment)

I also found some other discussion around this issue here https://gitlab.gnome.org/World/libcloudproviders/-/issues/17

[ckstevenson]

It seems to be triggered by the cloud providers integration.

@thinkORo I was able to at least temporarily work around it by commenting out the lines noted in #1982 (comment)

I also found some other discussion around this issue here https://gitlab.gnome.org/World/libcloudproviders/-/issues/17

Nice link. This is the same way I experience the issue. I only use nextcloudcmd to sync some data in a script, so it is extremely annoying when I need to upload a file via a gtk application and then the Nextcloud client opens up. I want to say the issue for me started after I switched to the dbus-broker some weeks ago, but I am unsure.

Edit: initial tests show the temporary work around also fixing the issue for me.

[topas-rec]

Happens for me also with the dbus-daemon-units installed instead of dbus-broker-units.

[topas-rec]

@thinkORo
I was able to at least temporarily work around it by commenting out the lines noted in #1982 (comment)

Doesn't work on my machine anymore. If someone has another workaround please let me know, because I uninstalled it.