[Bug 1205087] New: Launching nautilus automatically launches nextcloud-client even if user does not have any sync accounts
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1205087 Bug ID: 1205087 Summary: Launching nautilus automatically launches nextcloud-client even if user does not have any sync accounts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: badshah400@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- On Tumbleweed (currently version 20221031, but problem started earlier) starting GNOME's file-browser nautilus automatically launches the nextcloud-desktop client with NO way to prevent this behaviour. The client is launched every time the file browser or indeed even if the file-picker is started from firefox or wherever. And this happens no matter if the user has an account or not (the client may be installed because other users on the same system may have accounts, but I doubt anyone would want this behaviour to happen to them by default, sync accounts or not). There is no way to turn this behaviour off, no checkbox, option, or anything from inside the client. After a bit of head-scratching about this highly annoying issue, I figured out that this happens due to an apparently very botched libcloudproviders integration from nextcloud-client, as documented in the following upstream bug reports (un-resolved as of this date): * https://github.com/nextcloud/desktop/issues/1982 * https://github.com/nextcloud/desktop/issues/2622 Please fix this behaviour so that I do not have to go around installing or removing a bunch of machines I administer or, worse, have to do something manually after every nextcloud-client update. So far, I have been getting around (on my personal system) by commenting put the "/usr/share/cloud-providers/com.nextcloudgmbh.Nextcloud.ini" file, but that gets over-written on every update. I submitted what I felt was a possible fix [1], but it seems to be not acceptable to the maintainer. So this is a request to have the nextcloud-client behaviour of starting up on file-browser launch some other way. Thanks in advance. [1] https://build.opensuse.org/request/show/1032731 -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1205087
https://bugzilla.suse.com/show_bug.cgi?id=1205087#c1
Atri Bhattacharya
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1205087
https://bugzilla.suse.com/show_bug.cgi?id=1205087#c2
Eric Schirra
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1205087
https://bugzilla.suse.com/show_bug.cgi?id=1205087#c4
Eric Schirra
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1205087
https://bugzilla.suse.com/show_bug.cgi?id=1205087#c5
Atri Bhattacharya
The change is in Factory and therefore also in Tumbleweed. So the next update/snapshot of Tumbleweed will also be there. Furthermore, not everything in your request was correct and I didn't want other things.
You shall have another bug for that other change too.
Who makes the request and which request is accepted is subject to the decision of the maintainer.
maintainer is not god. Decisions are to be taken for the betterment of the distro, not based on preconceived judgments. And dismissive comments like "And I use the client now since 2016 under KDE. And that without any problem" when someone is trying to help improve the package (at least in their opinion) voluntarily will simply turn off potential contributors with skins thinner than mine.
Oh well, there are more people who are not convinced by this change and still I made it.
CC them on this bug and let us have a discussion on the best way forward then.
The point is taken care of.
IT JUST IS NOT. The problem is that the recommended package will be installed by default. So, users who aren't aware of what causes this issue will have no idea they need to uninstall this obscure package named "libcloudproviders-whatever" just from seeing the client launched automatically without their consent. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1205087
https://bugzilla.suse.com/show_bug.cgi?id=1205087#c6
Eric Schirra
participants (1)
-
bugzilla_noreply@suse.com