https://bugs.kde.org/show_bug.cgi?id=521961
--- Comment #3 from Stanley Chan <[email protected]> --- # ๐ Bug Report: Plasma Network Management Applet Does Not Display IPv4 Address (Arch Linux + NetworkManager) ## ๐ Summary After upgrading Arch Linux system packages (including NetworkManager and KDE Plasma components), the KDE Plasma Network Management applet no longer displays IPv4 address information for active wired connections. However, NetworkManager successfully obtains and assigns an IP address at the system level. Only MAC address information is shown in the KDE UI, while IPv4/IPv6 details are missing. --- ## ๐ฅ๏ธ System Environment * OS: Arch Linux (rolling release) * Desktop Environment: KDE Plasma (latest version after system upgrade) * Network Stack: * NetworkManager: 1.56.1-1 * DHCP client: internal (NetworkManager built-in) * Backend DNS: systemd-resolved (symlink mode) * Interface: Ethernet (enp5s0) * KDE Network Applet: plasma-nm (latest from Arch repos) --- ## ๐ Steps to Reproduce 1. Upgrade system packages: ```bash pacman -Syu ``` 2. Reboot system 3. Connect via wired Ethernet (DHCP) 4. Open KDE Plasma Network Management widget 5. Check connection details --- ## โ Expected Result The KDE Network Management applet should display: * IPv4 address (e.g., 192.168.2.215) * Gateway * DNS servers * IPv6 configuration (if available) --- ## โ Actual Result KDE Plasma Network Management applet only shows: * MAC address of interface * No IPv4 address * No IPv6 address * No gateway or DNS information However, system-level networking works correctly. --- ## ๐ NetworkManager Logs (Relevant Excerpt) The following logs confirm that DHCP and IP assignment are successful: ``` dhcp4 (enp5s0): state changed new lease, address=192.168.2.215 policy: set 'Wired connection 1' as default for IPv4 routing and DNS device (enp5s0): state change: ip-config -> activated Activation: successful, device activated. manager: NetworkManager state is now CONNECTED_GLOBAL ``` This confirms: * DHCP lease successfully obtained * IPv4 address assigned: 192.168.2.215 * Device fully activated and routed --- ## ๐ Additional Observations * NetworkManager version: 1.56.1-1 (Arch Linux) * Plasma appears unable to retrieve IP configuration via D-Bus * `nmcli` correctly shows IP information * System routing and connectivity are fully functional Example (system-level confirmation): ``` nmcli device show enp5s0 IP4.ADDRESS[1]: 192.168.2.215/24 ``` --- ## ๐งฉ Suspected Cause The issue appears to be a mismatch or regression between: * `plasma-nm` (KDE Network Management applet) * `NetworkManager` D-Bus API (Device.IP4Config interface) Possible causes: 1. Plasma Network Management applet failing to query IP4Config via D-Bus 2. API changes or timing differences in NetworkManager 1.56+ 3. Plasma 6 compatibility regression with newer NetworkManager versions 4. Missing or broken integration in `org.freedesktop.NetworkManager.Device.IP4Config` --- ## ๐งช Workaround Status * `nmcli` shows correct IP information โ * `ip addr` shows correct IP assignment โ * KDE UI does not display IP โ No user-side fix currently available in GUI layer. --- ## ๐ Impact * Affects usability of KDE Network Management applet * Misleading UI (shows incomplete connection state) * Forces users to rely on CLI tools (`nmcli`, `ip`) --- ## ๐ Request Please investigate potential regression in: * `plasma-nm` D-Bus integration with NetworkManager 1.56+ * IPv4/IPv6 data retrieval in KDE Plasma network widget --- ## ๐งพ Attachments * NetworkManager system journal logs (filtered) * `nmcli device show` output (available upon request) --- -- You are receiving this mail because: You are watching all bug changes.
