Bug 517071 - Networks widget showing offline when connected to VLAN
Summary: Networks widget showing offline when connected to VLAN
Status: RESOLVED DUPLICATE of bug 516709
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networks widget (other bugs)
Version First Reported In: 6.6.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-03-04 08:08 UTC by slaecker
Modified: 2026-03-05 13:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Network status offline with connected VLAN (87.92 KB, image/png)
2026-03-04 08:08 UTC, slaecker
Details
Network status correct when VLAN is disconnected (67.03 KB, image/png)
2026-03-04 08:10 UTC, slaecker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description slaecker 2026-03-04 08:08:55 UTC
Created attachment 190334 [details]
Network status offline with connected VLAN

SUMMARY
When a VLAN is connected, the networks widget shows the status icon as offline. As soon as the VLAN is disconnected, it shows the status correctly.

STEPS TO REPRODUCE
1. Connect to ethernet
2. Check Network status icon showing the correct "connected" status
2. Add a VLAN connection and connect
3. Check the network status icon

OBSERVED RESULT
Network status icon switches to offline

EXPECTED RESULT
Network status icon showing the correct status.

SOFTWARE/OS VERSIONS
Linux: 6.18.13-zen1-1-zen (64-bit)
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2

ADDITIONAL INFORMATION
I'm seeing this issue for some time now, this was working before. I think it started misbehaving from 6.6.0 or 6.6.1.
Comment 1 slaecker 2026-03-04 08:10:08 UTC
Created attachment 190335 [details]
Network status correct when VLAN is disconnected
Comment 2 Nate Graham 2026-03-04 20:35:37 UTC

*** This bug has been marked as a duplicate of bug 516712 ***
Comment 3 Nate Graham 2026-03-05 13:37:07 UTC

*** This bug has been marked as a duplicate of bug 516709 ***