### System details

- Omarchy **4.0.4-1**
- Affected component: **omarchy.network**

## Description

After restarting NetworkManager, the network icon in the `omarchy.network` widget incorrectly changes from the **Ethernet icon to the Wi-Fi icon**, while the actual network connection remains Ethernet.

NetworkManager and the routing table continue to correctly report `enp34s0` as the connected and active interface.

Restarting the Omarchy shell immediately restores the correct Ethernet icon.

## Steps to reproduce

1. Start Omarchy with an active Ethernet connection.
2. Confirm that `omarchy.network` displays the Ethernet icon.
3. Restart NetworkManager: `sudo systemctl restart NetworkManager`
4. Wait for the Ethernet connection to be restored.
5. Observe the network icon.

## Actual behavior

The **icon changes from Ethernet to Wi-Fi**, although the connected interface remains Ethernet.

Immediately after reproducing the issue:

```
$ nmcli device status

DEVICE      TYPE      STATE                   CONNECTION
enp34s0     ethernet  connected               Wired connection 1
tailscale0  tun       connected               tailscale0
docker0     bridge    connected (externally)  docker0
lo          loopback  connected (externally)  lo
```

The routing table also confirms that Ethernet remains the active interface:

```
$ ip route

default via 192.168.1.1 dev enp34s0 proto static metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev enp34s0 proto kernel scope link src 192.168.1.69 metric 100

```
There is **no Wi-Fi interface** involved in the active connection.

## Workaround

Running: `omarchy restart shell` immediately restores the Ethernet icon.

This indicates that restarting the shell causes the network state used by the widget to be reinitialized correctly.

## Expected behavior

After NetworkManager restarts and the Ethernet connection is restored, `omarchy.network` should automatically refresh its network state and continue displaying the Ethernet icon.

A shell restart should not be required.

## Likely cause

This appears to be related to [#7324](https://github.com/basecamp/omarchy/issues/7324).

That issue documents a NetworkManager/Quickshell networking state desynchronization after NetworkManager restarts.

The network widget relies on the Quickshell networking state to determine the connection type. If that state is not correctly re-bound after NetworkManager's D-Bus service restarts, the widget can display an incorrect connection icon even though NetworkManager itself reports the correct device state.

## Proposed fix

`Quickshell.Networking` should detect when NetworkManager's D-Bus service is restarted and automatically re-bind/refresh its network state.

This should re-synchronize the wired and Wi-Fi device states with `omarchy.network` without requiring a shell restart.