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?

There is a hacky way of converting it to a systemd service

First, move /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop out of that autostart dir and make sure KDE Connect is not started (possibly kill it). Keep in mind that this file will come back if you reinstall or upgrade the package. Then copy the file to ~/.config/systemd/user/ and do

# 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

    • boredsquirrel@slrpnk.netOP
      0·
      6 months ago

      I am currently experimenting with this. I dont know what the best solution is. I will add a new post about this in KDE Discuss and Lemmy.

      • system or user services?
      • common directory?
      • order of launch
      • what are the dependencies and what depends on them

      It is pretty crazy that entire KDE Plasma doesnt use systemd, and I can now (after looking through /etc/xdg/autostart add geoclue, baloo and orca to the possibly unwanted processes).

  • mox@lemmy.sdf.org
    0·
    6 months ago

    Petition the KDE maintainers to make it work like all the other KDE Background Services, rather than the ridiculous current approach of launching it at session start (whether the user wants it or not) and allowing systemd to automatically re-launch it (also against the user’s wishes).

    • boredsquirrel@slrpnk.netOP
      0·
      6 months ago

      Can you explain how systemd relaunches it?

      I want to test converting some noncritical but annoying services to systemd services. Then I will experiment with changing all to systemd services in a VM.

      But if there is some strange systemd action in there that relaunches things, this needs to be adapted too.

      • mox@lemmy.sdf.org
        0·
        6 months ago

        It uses a dbus service definition to make it re-launch when that service is called.

      • m4@kbin.social
        0·
        6 months ago

        I suspect @mox is confused somehow - as far as I know, KDEConnect does not provide any system service interface so systemd can handle it. It all happens in the KDE user session.

        I know this because I don’t use systemd and have KDEConnect working and autolaunching here.