Kdeconnect is very cool but also pretty sensitive. There are many reasons why people would like to turn it off.

I already tried placing an empty autostart file with the same name in ~/.local/share/applications/ (same with discovernotifier) and this didnt do anything.

Another option would be simply closing the firewall (which will be done by default) but I think this doesnt affect bluetooth?

# One time so systemd picks up the new file:
systemctl --user daemon-reload
# to start/stop:
systemctl --user start kdeconnect.service
systemctl --user stop kdeconnect.service
# to enable, which means it is started automatically when you login (and killed when you logout. The --now part also starts/stops it right away
systemctl --user enable --now kdeconnect.service
# and disable
systemctl --user disable --now kdeconnect.service
# output status and log (add e.g. -n 30, if you want to have more log lines)
systemctl --user status kdeconnect.service

Uninstalling is not an option, as on Fedora Atomic desktops users cant reinstall apps that were uninstalled in the image building process.

I am planning a uBlue variant with enhanced security and need to fix this issue. Especially using it via bluetooth is great, but of course also attack surface.

Relevant KDE Discuss post

KDE Bug

Other requests

• 1
• 2
• 3