https://bugs.kde.org/show_bug.cgi?id=510121

            Bug ID: 510121
           Summary: [LXQt] KDE Connect fails to reconnect to PCs after
                    reboot with any firewall backend
    Classification: Applications
           Product: kdeconnect
      Version First 25.08.1
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: common
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

What happened:
After rebooting a PC running the LXQt desktop environment, KDE Connect fails to
reconnect to other PCs on the same local network. The mobile phone connection
is generally unaffected. This happens regardless of the firewall used
(firewalld, ufw) or its backend (nftables, iptables). Temporarily disabling and
re-enabling the firewall fixes the connection until the next reboot.

What was expected:
KDE Connect should automatically reconnect to paired devices after a system
reboot.

Steps to reproduce:
1.  Use any Arch-based distribution (Manjaro, EndeavourOS, Artix) with the
**LXQt desktop environment**.
2.  Ensure KDE Connect is installed and paired with other PCs on the local
network.
3.  Reboot the PC.
4.  Observe that KDE Connect fails to re-establish the connection to other PCs.

Additional Information:
*   **Desktop Environment:** LXQt (Version: 2.2.0, Liblxqt: 2.2.0, Qt: 6.9.0)
*   **KDE Connect Version:** kdeconnect.daemon 25.08.1
*   **Firewall:** Problem observed with `firewalld` (nftables), `ufw`
(iptables), and `iptables` (direct setup).
    *   **firewalld (nftables):** Used on EndeavourOS. Connection fails after
reboot.
    *   **ufw (iptables):** Used on Manjaro. Connection fails after reboot,
despite confirming correct `ufw` rules.
    *   **iptables (direct setup):** Used on Artix. Connection fails with ufw
enabled but works when disabled.
*   **Systemd:** The issue occurs both with (EndeavourOS, Manjaro) and without
(Artix) `systemd`.
*   **Kernel Version:** The issue is consistent across different kernel
versions (6.12, 6.16, 6.17).
*   **Display Server:** X11 (Wayland is not used).
*   **Network Interface:** Wi-Fi or Ethernet.
*   **Router:** X12 (model), X12-62D0F5 (identification)
*   **Temporary fix:** Temporarily disabling and re-enabling the firewall
allows connections to be restored until the next reboot.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to