I’ve used it without those issues on cinnamon, xfce, and a variety of of tiling WMs. It fails to connect sometimes, but that happens on KDE as well, and I most certainly didn’t need to reauth every time I connect to the network. So idk what you’re talking about.
So, you’re basically running the KDE infrastructure, just not using the KDE WM? Have you done a ps and counted the number of KDE services that are running, just to run KDE Connect?
Here are the (KDE) dependencies on the Arch KDE Connect package:
I’ve used it without those issues on cinnamon, xfce, and a variety of of tiling WMs. It fails to connect sometimes, but that happens on KDE as well, and I most certainly didn’t need to reauth every time I connect to the network. So idk what you’re talking about.
So, you’re basically running the KDE infrastructure, just not using the KDE WM? Have you done a ps and counted the number of KDE services that are running, just to run KDE Connect?
Here are the (KDE) dependencies on the Arch KDE Connect package:
kcmutils kconfig kcoreaddons kcrash kdbusaddons kdeclarative kguiaddons ki18n kiconthemes kio kirigami kirigami-addons kitemmodels kjobwidgets knotifications kpeople kservice kstatusnotifieritem kwidgetsaddons kwindowsystem pulseaudio-qt qqc2-desktop-style qt6-base qt6-connectivity qt6-declarative qt6-multimedia qt6-wayland
When you run KDE Connect, you’re running most of the KDE Desktop and Qt; you’re just not using it.
Have you ever tried running it headless? I have; it doesn’t work.