Bug 394163 - Not all available connections listed in plasma-nm applet
Summary: Not all available connections listed in plasma-nm applet
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-12 13:15 UTC by valdikss
Modified: 2020-12-19 04:35 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
video (949.98 KB, video/mp4)
2018-05-12 13:15 UTC, valdikss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description valdikss 2018-05-12 13:15:12 UTC
Created attachment 112597 [details]
video

Sometimes plasma-nm applet does not show all available items which should be available for connection. This has been spotted with Wi-Fi networks and VPN connections, but probably happens with all types of connections.

This condition usually happens when the same connections are available via multiple interfaces. In the attached video, I was using external USB Wi-Fi card and unplugged it prior recording. After that, NEXXAP and O2Mobile networks were not seen in the list as available Wi-Fi connections when the Wi-Fi is enabled, but shown when Wi-Fi is disabled.

The connections could be activated by right-clicking on the connection in the network configuration dialog.
Comment 1 valdikss 2018-09-08 13:17:56 UTC
Do you need any additional information from me? This bug is reproducible in KDE 5.13.4, Frameworks 5.48.0, Qt 5.10.1, Fedora 28.
Comment 2 emelenas 2018-12-04 18:56:54 UTC
I can confirm the same behavior, but with only one (internal) wifi card. It usually happens after a resume from a suspend where the wifi network was previously connected and set to no auto connection. The video exactly reproduces my experience. It is amazing to see the netwoks you are looking for when you disable wifi. I'm running a Fedora 29, kde-plasma 5.14.3, qt-5.11.1
Comment 3 Justin Zobel 2020-11-19 22:42:26 UTC
I've just tested this on 5.20.3 and I cannot reproduce the issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 4 Bug Janitor Service 2020-12-04 04:34:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2020-12-19 04:35:42 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!