### System details

Dell Lattitude 5510 16GB RAM 256GB NVME SSD

### What's wrong?

# Bug Report: KDE Connect Discovery Failure on Tailscale / Local Wi-Fi

## 1. System Environment
* **OS:** Omarchy 4 (Arch-based Linux)
* **Shell/Environment:** Quickshell (Default Omarchy 4 custom graphical layer)
* **Configuration Manager:** chezmoi
* **Hardware:** Dell Latitude 5510
* **Processor:** Intel Core i5
* **Memory:** 16 GB RAM (Upgraded)
* **Storage:** 256 GB NVMe SSD
* **Network Layers:** Simultaneous local Wi-Fi and Tailscale VPN Mesh Network

---

## 2. Description of the Issue
KDE Connect completely fails to discover any local or remote mesh devices. Neither the `kdeconnect-indicator` GUI layer nor the command-line utility (`kdeconnect-cli -l`) populates available devices, despite multiple known active devices being present on both the local LAN subnet and the Tailscale network.

---

## 3. Troubleshooting Steps Attempted (No Success)
To narrow down the root cause, the following explicit diagnostic routines were performed:

* **Firewall Verification:** Confirmed that Uncomplicated Firewall (UFW) rules are explicitly allowed and reloaded for the standard KDE Connect ports (`1714:1764` over both TCP and UDP).
* **Power Cycle:** A full hardware reboot was executed to rule out temporary network adapter lockups or initialization order errors.
* **Daemon Execution Tracking:** 
  * Initially attempted execution via `/usr/lib/libexec/kdeconnectd`, which failed with a `127 exit code (No such file or directory)` due to alternative path definitions on this distribution.
  * Located and verified the running daemon under `/usr/bin/kdeconnectd` (confirmed active with `pgrep`).
* **Environment Binding Restrictions:** Attempted to explicitly force multi-adapter binding by launching the background task with customized interface hooks:
  ```bash
  KDE_CONNECT_INTERFACES=wlan0,tailscale0 /usr/bin/kdeconnectd &
  ```
* **Unicast Forcing:** Attempted to manually bypass standard UDP multicast discovery by calling direct peer targeting via the CLI flag:
  ```bash
  kdeconnect-cli --device-ip <TARGET_DEVICE_IP> --refresh
  ```
* **D-Bus Context Check:** Investigated potential environment isolation caused by the custom shell environment by wrapping the execution thread within an explicit D-Bus session framework (`dbus-run-session kdeconnect-cli -l`). 

Despite the service running actively in the background, all instances of `kdeconnect-cli -l` return an empty device list without any reported socket or broadcast errors.

---

## 4. Expected Behavior
Active devices on the same local subnet or matching Tailscale network entries should register a direct handshake profile and become visible for pairing via the CLI list tool or standard desktop notifications.