Bug 390861

Summary: disable kdeconnectd if plasmoid is not active
Product: [Applications] kdeconnect Reporter: rockonthemoonfm
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: kde, nicolas.fella, rdieter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: attachment-562-0.html

Description rockonthemoonfm 2018-02-21 18:31:15 UTC
I don't have a smartphone, so I disabled kdeconnect widget, but the daemon is always active on plasma startup, and there's no easy way to disable it.
It could become a dbus service that gets activated/deactivated depending on the widget state.
Comment 1 Rex Dieter 2018-02-21 18:55:50 UTC
There's more interfaces to kdeconnectd than just the plasma widget, kdeconnect-cli for example.

You have several options to fully disable it (though these are mostly manual processes):
* uninstall
* disable the autostart service
Comment 2 rockonthemoonfm 2018-02-22 09:16:47 UTC
Created attachment 110892 [details]
attachment-562-0.html

From kdeconnect-cli you cannot disable, nor stop the service.
You cannot neither disable it from System Settings -> Startup and Shutdown
-> Background Services, nor from System Settings > KDE Connect
On NEON, probably until KF 5.43, uninstalling KDE Connect would uninstall
Spectacle and other pkgs too.
As of now, uninstalling Works For Me.

P.S. - wouldn't be more correct to call it Plasma Connect then KDE Connect?
:D

2018-02-21 19:55 GMT+01:00 Rex Dieter <bugzilla_noreply@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=390861
>
> Rex Dieter <rdieter@gmail.com> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>                  CC|                            |rdieter@gmail.com
>
> --- Comment #1 from Rex Dieter <rdieter@gmail.com> ---
> There's more interfaces to kdeconnectd than just the plasma widget,
> kdeconnect-cli for example.
>
> You have several options to fully disable it (though these are mostly
> manual
> processes):
> * uninstall
> * disable the autostart service
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Kai Uwe Broulik 2018-02-22 09:46:35 UTC
KDE Connect used to be shoehorned ontop of a kded module which allowed to disable it from the background services settings, now it's a regular startup application.

The only way so far I can see is copy the kdeconnectd.desktop file from /etc/xdg/autostart to ~/.config/autostart and add Hidden=true to the file, that will overrule the system-wide one.
Comment 4 Nicolas Fella 2018-09-27 14:38:22 UTC
If you don't use KDE Connect at all you can uninstall it. Besides that you can just remove it from autostart.

Disabling it when the plasmoid is not active makes no sense since it can be used on other desktop environments as well