Hello,I am experiencing an issue where KDE Connect has stopped working entirely following recent kernel updates on siduction.Problem Description:
KDE Connect was working perfectly until I updated the system. The break initially occurred immediately after upgrading to kernel version 7.1.9. Upgrading further to 7.1.10 did not resolve the issue; KDE Connect remains non-functional (it cannot detect or pair with any devices on the same local network).Environment:- OS: siduction (unstable)
- Desktop Environment: KDE Plasma
- Working Kernel: 7.1.8
- Broken Kernels: 7.1.9-1-siduction-amd64 and 7.1.10-1-siduction-amd64
Steps to Reproduce:- Boot into siduction using kernel 7.1.9 or 7.1.10.
- Open KDE Connect.
- Attempt to refresh or find previously paired local network devices (e.g., Android phone).
- Notice that no devices appear, and communication fails.
Troubleshooting Done:
- Confirmed both devices are on the exact same Wi-Fi network.
- Swapping back to an older kernel temporarily fixes the issue, which isolates the problem to the 7.1.9+ kernel updates.
Thank you for looking into this![/list]
williamrw@williamrw-asussid:
~$ uname -a
Linux williamrw-asussid 7.1.10-1-siduction-amd64 #1 SMP PREEMPT_DYNAMIC siduction 7.1-10 (2026-08-23) x86_64 GNU/Linux
williamrw@williamrw-asussid:
~$ ps -ef | grep kdeconnect
william+ 2430 1973 0 11:09 ? 00:00:00 /usr/bin/kdeconnectd
william+ 3510 3496 0 11:12 pts/1 00:00:00 grep kdeconnect
williamrw@williamrw-asussid:
~$ journalctl -b --user -u kdeconnect
-- No entries --
williamrw@williamrw-asussid:
~$ inxi -Fz
System: Kernel: 7.1.10-1-siduction-amd64
arch: x86_64
bits: 64
Desktop: KDE Plasma
v: 6.7.4
Distro: siduction 2025.1.0 shine-on - kde -
(202503241412)
Machine: Type: Laptop
System: ASUSTeK
product: ASUS TUF Gaming F16 FX608JHR_FX608JHR
v: 1.0
serial: <superuser required>
Mobo: ASUSTeK
model: FX608JHR
v: 1.0
serial: <superuser required>
Firmware: UEFI
vendor: American Megatrends LLC.
v: FX608JHR.312
date: 05/07/2026
Battery: ID-1: BAT0
charge: 71.5 Wh (83%)
condition: 86.2/90 Wh (95.7%)
CPU: Info: 16-core (8-mt/8-st)
model: Intel Core i7-14650HX
bits: 64
type: MST AMCP
cache: L2: 24 MiB
Speed (MHz): avg: 800
min/max: 800/5000:5200:3700
cores: 1: 800
2: 800
3: 800
4: 800
5: 800
6: 800
7: 800
8: 800
9: 800
10: 800
11: 800
12: 800
13: 800
14: 800
15: 800
16: 800
17: 800
18: 800
19: 800
20: 800
21: 800
22: 800
23: 800
24: 800
Graphics: Device-1: Intel Raptor Lake-S UHD Graphics
driver: i915
v: kernel
Device-2: NVIDIA GB207M [GeForce RTX 5050 Max-Q / Mobile]
driver: nvidia
v: 580.178.04
Device-3: Shinetech ASUS FHD webcam
driver: uvcvideo
type: USB
Display: wayland
server: X.org
v: 1.21.1.24
with: Xwayland
v: 24.1.13
compositor: kwin_wayland
driver: X: loaded: modesetting,nvidia
unloaded: fbdev,nouveau,vesa
dri: iris
gpu: i915
resolution: 1920x1200~165Hz
API: EGL
v: 1.5
drivers: iris,nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL
v: 4.6.0
compat-v: 4.6
vendor: intel mesa
v: 26.1.6-1
renderer: Mesa Intel Graphics (RPL-S)
API: Vulkan
v: 1.4.357
drivers: intel,nvidia,llvmpipe
surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor
gpu: nvidia-smi
wl: wayland-info
x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio: Device-1: Intel 700 Series Family HD Audio
driver: snd_hda_intel
Device-2: NVIDIA GB207 High Definition Audio
driver: snd_hda_intel
API: ALSA
v: k7.1.10-1-siduction-amd64
status: kernel-api
Server-1: PipeWire
v: 1.6.8
status: active
Network: Device-1: Realtek RTL8852CE PCIe 802.11ax Wireless Network
driver: rtw89_8852ce
IF: wlan0
state: up
mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp109s0
state: down
mac: <filter>
Device-3: Realtek RTL8153 Gigabit Ethernet Adapter
driver: r8152
type: USB
IF: enx00e04cadb005
state: down
mac: <filter>
Bluetooth: Device-1: IMC Networks Bluetooth Radio
driver: btusb
type: USB
Report: hciconfig
ID: hci0
state: up
address: <filter>
bt-v: 5.3
Drives: Local Storage: total: 8.67 TiB
used: 1.72 TiB (19.9%)
ID-1: /dev/nvme0n1
vendor: Western Digital
model: WD Green SN3000 1TB
size: 931.51 GiB
ID-2: /dev/nvme1n1
vendor: Corsair
model: MP600 MICRO
size: 931.51 GiB
ID-3: /dev/nvme2n1
vendor: Western Digital
model: WD Blue SN5000 2TB
size: 1.82 TiB
ID-4: /dev/nvme3n1
vendor: Lexar
model: SSD NQ780 1TB
size: 953.87 GiB
ID-5: /dev/nvme4n1
vendor: Western Digital
model: WD BLACK SN850X 1000GB
size: 931.51 GiB
ID-6: /dev/sda
model: XS1000
size: 1.82 TiB
type: USB
ID-7: /dev/sdb
vendor: Kingston
model: SNV3S1000G
size: 931.51 GiB
type: USB
ID-8: /dev/sdc
vendor: Eaget
model: N/A
size: 476.94 GiB
type: USB
Partition: ID-1: /
size: 931.22 GiB
used: 55.33 GiB (5.9%)
fs: btrfs
dev: /dev/nvme1n1p2
ID-2: /boot/efi
size: 299.4 MiB
used: 640 KiB (0.2%)
fs: vfat
dev: /dev/nvme1n1p1
ID-3: /home
size: 931.22 GiB
used: 55.33 GiB (5.9%)
fs: btrfs
dev: /dev/nvme1n1p2
ID-4: /var/log
size: 931.22 GiB
used: 55.33 GiB (5.9%)
fs: btrfs
dev: /dev/nvme1n1p2
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 45.2 C
mobo: N/A
Fan Speeds (rpm): cpu: 2400
Info: Memory: total: 32 GiB
note: est.
available: 30.94 GiB
used: 3.62 GiB (11.7%)
Processes: 535
Uptime: 13m
Shell: Bash
inxi: 3.3.41
Well, I used to have the same problem.
I investigate spare time to, hopefully, solve it.
In short, the culprit is firewalld.
Quote: https://userbase.kde.org/KDEConnect#firewalld
[...]
If your firewall is firewalld, you can open the necessary ports with:
sudo firewall-cmd --permanent --zone=home --add-service=kdeconnect
sudo firewall-cmd --reload
Note
This allows KDE Connect to be accessed from outside while you're in the "home" zone. A zone can be assigned to your WiFi connection in network settings. For safety, you should rather avoid running KDE Connect in "public" zone.
But it doesn't work because the home-zone wasn't active.
# firewall-cmd --get-active-zones
docker
interfaces: docker0
libvirt
interfaces: virbr0
public (default
interfaces: wlan0
No home zone active!
So I had to activate that zone to get it working.
firewall-cmd --permanent --zone=home --change-interface=wlan0
I am using a laptop connected via Wi-Fi/wlan0 to the Network/Internet.
# firewall-cmd --get-active-zones
docker
interfaces: docker0
home
interfaces: wlan0
libvirt
interfaces: virbr0
public (default)
Don't forget to reload firewalld.
Here is my home.xml
# cat /etc/firewalld/zones/home.xml
<?xml version="1.0" encoding="utf-8"?>
<zone>
<short>Home</short>
<description>For use in home areas. You mostly trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.</description>
<service name="ssh"/>
<service name="mdns"/>
<service name="samba-client"/>
<service name="dhcpv6-client"/>
<service name="kdeconnect"/>
<masquerade/>
<forward/>
</zone>
Problem: After upgrading to kernel 7.1.9 and through 7.2.2 phone was not reachable:
Solution below:
KDE Connect is now working correctly on kernel 7.2.2. ✅
My final result:
OnePlus 13: 08d76a1981a644199b60068898c92814
on 192.168.1.19 via LAN (reachable)
1 device found
And the permanent firewalld configuration is:
home zone
1716/tcp
1716/udp
Final diagnosis
The kernel upgrade itself wasn't breaking KDE Connect. The problem was that after the upgrade, my firewalld home zone no longer allowed KDE Connect's port 1716.
The decisive test was:
Phone → 192.168.1.16:1716 TCP SYN
with no SYN-ACK.
After adding:
firewall-cmd --permanent --zone=home --add-port=1716/tcp
firewall-cmd --permanent --zone=home --add-port=1716/udp
the phone immediately became:
via LAN (reachable)