https://bugs.kde.org/show_bug.cgi?id=516709
--- Comment #15 from kodirovsshik <[email protected]> --- 1. > For me the VLAN shows up as connection, but the icon is still red. I'm having the same issue on 6.6.2, no matter the state of the VLAN connection or connectivity check (none, limited, full). I tried testing on 6.3 (that's the one I was able to get easily with Kubuntu 25.10). Here is what I got: If the cable is not plugged in, I get a disconnected icon no matter what. All other experiments are done with cable connected at all times. If the cable is connected and there's only an Ethernet connection, I get either the standard connected icon (white wire) if connection is up or the disconnected icon (red/colored wire) if it is down; hovering over the icon displays an appropriate description (connected to "Wired Ethernet 1"/disconnected respectively). Totally correct and expected behavior. When a VLAN connection is added, its state doesn't affect the displayed icon at all. That is, when the Ethernet connection is down, the icon is ALWAYS a colored wire - no matter what state the VLAN connection is (down/up) and connectivity check result (limited/full), at least to the extent of my experiments. And bringing up the Ethernet connection sets the icon to white (assuming full connectivity). Interestingly enough, hovering over an icon with a connected VLAN (either full or limited) and disconnected Ethernet connection displays no description whatsoever. I wasn't able to get a limited connection icon any way other than having a limited connectivity on the Ethernet connection. 2. > These steps work to create a broken VLAN without connectivity Just to make sure we're on the same page, by "a broken VLAN without connectivity" you mean "VLAN with no internet connection", is that correct? And the output of ``` nmcli networking connectivity check ``` is "limited" and not "none", is that correct? Because if it's "none" it suggests there's probably a difference in our environments I failed to account for and the VLAN you created might be misconfigured. Were there any error-looking messages when you ran the commands? nmcli is verbose and outputs messages on success too, error messages might have blended in. Also, just to clarify, "limited" connectivity means there is an interface that is successfully configured (has an IP address, even if a static nonsense one), but NetworkManager can't reach the internet. It's a completely valid connection state, and the tray icon should reflect "limited" state if this is the "main" connection, not "disconnected". > how do I create a working one so I can test that case too? VLANs are a mix of software and hardware(network equipment firmware) solutions. Creating a VLAN connection that will give you full network connectivity requires configuring the LAN port on your networking equipment (like a managed network switch) in a specific way, and to the extent of my experience home ISP routers are much more likely to not support VLANs than to support them. If it's absolutely essential to set up a full connectivity VLAN connection, I can try to come up with *some* setup (which would involve nontrivial virtual routing that I'd be hesitant to run on a daily-driver machine). 3. Strange. I don't have this issue on my main OS installation but I was able to reproduce the issue on a Kubuntu 25 live ISO. Assuming the connections show up in system settings but not in the pop-up widget, this looks like another bug. A workaround I found is to restart plasmashell: ``` systemctl --user restart plasma-plasmashell ``` And as far as I can see this does not affect the icon though, the tray is still showing fallback one even after the connection shows up in the widget. -- You are receiving this mail because: You are watching all bug changes.
