Bug 494038 - Blank networks show up in Networks widget when Wi-Fi is disabled
Summary: Blank networks show up in Networks widget when Wi-Fi is disabled
Status: RESOLVED DUPLICATE of bug 493116
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray (show other bugs)
Version: 6.1.5
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-03 14:59 UTC by Marcus
Modified: 2024-10-03 15:27 UTC (History)
2 users (show)

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


Attachments
Wi-Fi disabled with a bunch of blank networks (27.82 KB, image/png)
2024-10-03 14:59 UTC, Marcus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus 2024-10-03 14:59:28 UTC
Created attachment 174367 [details]
Wi-Fi disabled with a bunch of blank networks

SUMMARY


STEPS TO REPRODUCE
1. Click on the Networks widget
2. Turn Wi-Fi off

OBSERVED RESULT
All Wi-Fi networks disappear and wired networks keep showing in the Networks widget.
Then a bunch of blank networks appear in the Networks widget.

EXPECTED RESULT
All Wi-Fi networks disappear and wired networks keep showing, but blank networks don't appear in the Networks widget.

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: Arch Linux 
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Kernel Version: 6.11.1-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
NetworkManager version: 1.50.0

Blank networks persist even when Wi-Fi is re-enabled.
core-testing, extra-testing and multilib-testing repositories are also enabled.
When you *try* to configure these blank networks, it brings up a configuration screen for a network that actually exists.
Comment 1 Filip 2024-10-03 15:27:58 UTC

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