https://bugs.kde.org/show_bug.cgi?id=417615
--- Comment #12 from Forest <fores...@sonic.net> --- I found some (ugly) workarounds for the unwanted kdeconnectd autostart. The process seems to be launched at session startup time from two distinct places: 1. /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop This can be disabled for individual users by copying the file to each user's ~/.config/autostart/ directory and adding Hidden=true to the [Desktop Entry] section of the copies. Alternatively, it can be disabled by default by adding a line like this to the file's [Desktop Entry] section: X-KDE-autostart-condition=kdeconnectd-autostartrc:General:Autostart:false Then, to re-enable it for a particular user, create a ~/.config/kdeconnectd-autostartrc file with Autostart=true in its [General] section. (The file name "kdeconnectd-autostartrc" is arbitrary; I chose it in hopes of avoiding conflicts with any standard files.) 2. /usr/share/dbus-1/services/org.kde.kdeconnect.service According to KDE docs*, this file tells every user's dbus session to launch kdeconnectd if something tries to contact it over d-bus. With this file in place, kdeconnectd is launched by systemd at session start even if a user disables the autostart .desktop file. The file can be moved to a backup directory to avoid this. However, I think a better fix would be to identify whatever is making org.kde.kdeconnect d-bus requests at session startup, and prevent that instead. * https://develop.kde.org/docs/use/d-bus/dbus_autostart_services/ Of course, these workarounds are hackish, and will probably revert to the normal (unwanted) behavior whenever KDE Connect package updates are installed. What we really need is for it to be configurable in the first place. Seems like a good fit for the Background Services panel. -- You are receiving this mail because: You are watching all bug changes.
