Bug 475957

Summary: plasma-nm5 does not show wireless networks after stop/start of NetworkManager
Product: [Plasma] plasma-nm Reporter: Ilan <ilanco>
Component: appletAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, nicolas.fella
Priority: NOR    
Version: 5.27.8   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: nm applet after restarting NetworkManager

Description Ilan 2023-10-22 09:16:56 UTC
Created attachment 162495 [details]
nm applet after restarting NetworkManager

SUMMARY

NM applet does not show list of wireless networks, wireless icon after restarting NetworkManager. However, connect/disconnect events are shown and wifi is working. nmcli command return expected results.


STEPS TO REPRODUCE
1. restart networking / NetworkManager
2. nm icon changes to disconnect and wifi options are gone

OBSERVED RESULT
nm icon changes to disconnect and wifi options are gone

EXPECTED RESULT
wireless network list is available and icon shows correct status

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Comment 1 Ilan 2023-10-22 09:21:18 UTC
Additional logs from plasmashell after running `systemctl restart NetworkManager`:

Could not find the Plasmoid for Plasma::FrameSvgItem(0x560396a359f0) QQmlContext(0x560395c73f70) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x560396a359f0) QQmlContext(0x560395c73f70) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:151: TypeError: Cannot read property 'expanded' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:125: TypeError: Cannot read property 'compactRepresentationItem' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null
Could not find the Plasmoid for Plasma::FrameSvgItem(0x5603961e6c00) QQmlContext(0x560395c73f70) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x5603961e6c00) QQmlContext(0x560395c73f70) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x560396a587a0) QQmlContext(0x560395c73f70) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x560396a587a0) QQmlContext(0x560395c73f70) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
QQmlExpression: Expression file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:181:21 depends on non-NOTIFYable properties:
    QAction::priority
    QAction::priority
    QAction::priority
QQmlExpression: Expression file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:82:17 depends on non-NOTIFYable properties:
    QAction::priority
    QAction::priority
    QAction::priority
    QAction::priority
    QAction::priority
trying to show an empty dialog
Comment 2 Nicolas Fella 2023-10-22 13:17:20 UTC
I can't reproduce this via "sudo systemctl restart NetworkManager.service"
Comment 3 Ilan 2023-10-22 14:06:15 UTC
Thanks for checking Nicolas. I wonder what difference there could be between our systems. Are you using wpa_supplicant or iwd?
Comment 4 Nate Graham 2023-10-25 21:01:06 UTC

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