KDE Connect Broken After 7.1.9 Upgrade (7.1.10 still broken)

Started by williamrw, Yesterday at 10:50:04

Previous topic - Next topic

williamrw

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
 
 

Teriarch

Can you provide the output of the following commands with reachable
devices around:
$ uname -a
Linux arlene 7.1.10-1-siduction-amd64 #1 SMP PREEMPT_DYNAMIC siduction 7.1-10 (2026-08-23) x86_64 GNU/Linux
$ kdeconnect-cli -l
- Pixel 3: 3a89574d70d841988b3a1a660c29d56d (paired)
- CUBOT H3: 51d02e19631c4bd282e9e61ba7a89599 on 192.168.178.58 via LAN (paired and reachable)
- Pixel 3: 99fd3e01d219433f87d368e21f31faf0 (paired)
3 devices found
$ ps xa|grep kdeconnect
  3116 ?        Sl    0:00 /usr/bin/kdeconnectd
  4709 ?        Sl    0:00 kdeconnect-indicator
  19389 ?        S    0:00 /usr/lib/x86_64-linux-gnu/libexec/kf6/kioworker /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/tags.so tags  local:/run/user/1000/kdeconnect.daemonmAfdLg.3.kioworker.socket
It seems to be a local problem. Pinging the device also works with siduction kernel
7.1.10-1-siduction-amd64:
$ kdeconnect-cli --ping -d 51d02e19631c4bd282e9e61ba7a89599PS.:
The only relevant change to the 7.1.9 kernel relating to this issue is
the FIB support of nftables (see <https://forum.siduction.org/index.php?topic=10020.0>).
So I suspect some hidden firewall rule might be responsible for the blocking
of TCP/UDP port 1716 on which /usr/bin/kdeconnctd runs.