Verifying NetworkManager Service Status
The foundation of network management in KDE Plasma is the NetworkManager daemon. If this service is inactive or crashed, no network interfaces will function correctly, regardless of hardware status. The first step in troubleshooting is to confirm that the service is running and enabled to start at boot.
To check the current status, open a terminal and execute the following command:
systemctl status NetworkManagerIf the output indicates that the service is inactive (dead) or failed, you must restart it immediately. Use the command below to restart the daemon:
sudo systemctl restart NetworkManagerAfter restarting, verify that the service is active again. If the service fails to start, check the journal logs for specific error messages using journalctl -u NetworkManager. This often reveals permission issues or conflicts with other network management tools like systemd-networkd.
Inspecting Wireless Hardware and Drivers
Even with a running NetworkManager, wireless connectivity may fail if the kernel drivers are not loaded or if the hardware is blocked by a physical switch. Linux systems manage radio state through the wireless-regdb and kernel modules such as iwlwifi for Intel cards or ath9k for Atheros chips.
Use the lspci command to identify your network controller:
lspci | grep -i networkIf the device appears but does not show up in the KDE Network Applet, check for software blocks using rfkill:
rfkill listThis command outputs a list of all wireless devices with their soft and hard block statuses. If a device shows Soft blocked: yes, you can unblock it with sudo rfkill unblock wifi. If it shows Hard blocked: yes, you must check your laptop’s physical Wi-Fi switch or keyboard shortcut (often Fn + F2) to enable the radio.
For deeper driver issues, consult the dmesg buffer to see if the firmware failed to load:
dmesg | grep -i firmwareMissing firmware packages are a common cause of silent failures. Ensure that your distribution’s firmware package (e.g., linux-firmware) is installed and up to date.
Analyzing Signal Strength and Interference
Slow speeds or intermittent drops are often due to poor signal quality rather than complete failure. KDE Plasma provides a graphical interface for this, but the command line offers more precise data. Use the wifi-menu utility from wpa_supplicant or simply scan for networks using nmcli.
nmcli device wifi listLook at the Signal column. A signal strength above -50 dBm is excellent, while anything below -80 dBm is likely to cause significant packet loss. If you are experiencing high latency, try switching to a less congested channel. Many modern routers allow manual channel selection in the admin panel; choosing channels 1, 6, or 11 for 2.4GHz bands minimizes overlap.
Additionally, interference from USB 3.0 devices can affect 2.4GHz Wi-Fi performance. Moving USB 3.0 peripherals away from the wireless antenna or using a USB extension cable can sometimes resolve inexplicable speed drops.
Configuring Static IP and DNS Settings
Sometimes the issue is not the connection itself, but the resolution of domain names or IP assignment. If you can ping an IP address (like 8.8.8.8) but cannot load websites, your DNS configuration is likely incorrect.
In KDE Plasma, navigate to System Settings > Network. Select your active connection and click Edit. Under the IPv4 or IPv6 tab, change the method from DHCP to Manual. Enter a valid DNS server, such as Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1.
If you suspect DHCP lease issues, try renewing the lease via terminal:
sudo nmcli con up "Your Connection Name"Alternatively, release and renew the IP address manually if you are using standard dhclient scripts, though nmcli is preferred in Plasma environments.
Checking for Conflicting Services
Multiple network managers can conflict with each other. For instance, having both NetworkManager and systemd-networkd enabled can lead to unpredictable behavior where one service takes over an interface unexpectedly.
Disable any secondary network services to ensure NetworkManager has full control:
sudo systemctl disable systemd-networkd
sudo systemctl stop systemd-networkdRestart NetworkManager after disabling these services to prevent conflicts. This is particularly relevant if you recently switched from a server-oriented setup to a desktop environment.
Frequently Asked Questions
Why does my Wi-Fi work on boot but disconnect randomly?
This is often caused by power-saving features in the wireless driver. You can disable power management by creating a configuration file in /etc/NetworkManager/conf.d/ with the directive [device] wifi.powersave = 2. This forces the card to stay active, preventing dropouts during low-load periods.
How do I fix the "Kernel IP Routing Table is Empty" error?
This error usually indicates that the network interface is down or lacks a valid route. Check the interface status with ip link and bring it up using sudo ip link set dev wlan0 up. Then, ensure NetworkManager assigns an IP address via DHCP or configure a static route manually.
Can I use Ethernet and Wi-Fi simultaneously on KDE Plasma?
Yes, but only if they are on different subnets or if you configure policy routing. By default, Linux uses the last-added route as the primary gateway. You can prioritize Ethernet over Wi-Fi by setting a lower metric for the Ethernet connection in the NetworkManager settings.
What should I do if the Network Manager icon is missing from the tray?
The applet might be hidden or crashed. Try restarting the plasmashell process with kquitapp5 plasmashell && kstart5 plasmashell. If the icon remains missing, reinstall the plasma-nm package via your distribution’s package manager to restore the system tray integration.
How can I test my actual network throughput in Linux?
Use the speedtest-cli tool or the iperf3 utility for local network testing. Install speedtest-cli via pip or your package manager, then run speedtest-cli to get detailed download and upload metrics compared to your ISP’s advertised speeds.