Bug 366564

KDE Connect works in every desktop, so it's by design that it autostarts everywhere.

How to disable it in gnome if I do not want to use it with gnome?

Why is it against the design to enable the option to start selectively? 
Choice is better than no choice, right?

thx, p.

I think I answerred to the wrong thread here - I can disable it with additional entries in the *.desktop files. 
So please ignore my comment. 

Though I still do not understand why autostart is enabled by default just "because it works"? 

The Gnome file indexer tracker works with every desktop. Still you wouldn't want it to autostart with KDE 
in the background, right?

Thx for your answer. Appreciated... p.

This is intended behaviour. You can use KDE Connect on all desktops, so it autostarts on all desktops. If you don't want to use it, deinstall it.

"This is intended behaviour." 

Well, that doesn't mean it's well designed... 


"You can use KDE Connect on all desktops, so it autostarts on all desktops." 

That's a clear non-sequitur: Just because it works everywhere it doesn't follow by any logic that it should run everywhere no matter what! 

At least give us a choice!    


"If you don't want to use it, deinstall it."

I like to use Kdeconnect. At least here and then...

So unistalling is not a reasonable option. 

But I do not want to use it everytime my computer starts. And certainly not everytime I use an alternative desktop environment. 


So what about my suggestion to change the default behaviour of "running in the background no maater what" to "running in the background if and when the user intends to use it"... 

Kdeconnect gives access to my computer from an outside source. Even if devs consider it secure for the moment there is a good argument to be made to completely shut it down if it is not needed. 

I have been under the impression KDE tries to not follow the Gnome appraoch of shoving features down their user's throats but instead allow for individual configuration. 

This approach acknowledges the fact that the intention of devs, as well meant as it might be, does not cover the intended workflows and use cases of the individual user.  

So according to KDE guidelines and promises of individuality - I'd still call this a bug. 

A simple option to disable KDEconnect by default (see my suggestion) and activate it when the user wants to use seems a noncontroversial solution. 

Anyone who wants to run it always and everywhere should be able to either tick an option to autostart with any chosen desktop environment or even systemwide.

I do not care if it's optin or optout - just the option suffices. 





If you don't want to use it, deinstall it.

If you don't want it in autostart just remove /etc/xdg/autostart/kdeconnectd.desktop

The question whether it should be in autostart or not is independent of the surrounding desktop  environment.

Thx for your quick answer. 

The solution you mentioned is troublesome - as with every update (monthly with KDE on ARCH for example) this file will be replaced, so it's still better to have the default content of the file changed. 


> OnlyShowIn=; 

as default does what you suggest (I think). 

There could be an option to activate it permanently in autostart as a "first run" question. This could systemwide or on a desktop environment basis by auto-editing the "kdeconnectd.desktop" either in /etc or ~./config/autostart

Or use standard XDG autostart mechanisms to disable it.

One example,
mkdir ~/.config/autostart/
cp /etc/xdg/autostart/kdeconnectd.desktop ~/.config/autostart/
echo "Hidden=true" >>  ~/.config/autostart/kdeconnectd.desktop

See also:
https://specifications.freedesktop.org/autostart-spec/autostart-spec-latest.html

re-closing

For some apps it makes sense to ask on launch, this is not one of them.

Again, you're free to customize your environment as you see fit, whether that is per-user (comment #9) or globally (you can define a custom XDG_CONFIG_DIRS variable to host a modified autostart/ dir)