SUMMARY When connected to a network with no internet, and trying to interact with the network applet latte-dock becomes prone to freeze for tens of seconds, these can even happen with frequency (under a minute after a prior freeze). I think if the issue happened recently it's more likely to happen soon again while connected to internet-less networks. STEPS TO REPRODUCE 1. Connecting to a network with no internet. 2. Interacting with the Network applet, sometimes just bringing it up is enough, sometimes disconnecting/connecting networks triggers it. OBSERVED RESULT MY latte-dock panels freeze and become unresponsive, other programs can still be used while this happens. EXPECTED RESULT No freezes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.11.19 (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION When this happens journalctl shows a lot of: systemd-resolved[310]: Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1. (as well as other ips for different servers, it alternates). I'm not sure if it's directly related as sometimes I see them in the log in intervals I don't remember having freezes, but they do appear very often when the problem appears, with nothing else appearing within. I'm also not 100% sure if this is strictly a lattedock issue because sometimes the moment the docks unfreeze it'll be accompanied by a notification coming through at the same time, but as this doesn't often happen I don't know if it's a coincidence or if other parts are getting frozen as well.
Latte does not change anything to applets. Isnt this reproducable with plasma panels?
info...
Also happens with plasmashell, and also determined that if there are notifications open during the freeze, they'll remain frozen as well. There sees to be a single exception to the freeze and it's the circle animation when in the middle of connecting, if it is playing when the freeze happens they'll keep being animated. But every other widget is frozen, for example netspeed widget will get stuck and so will the time (won't change until it unfreezes). I tried changing NetworkManager's backend, but it seems whether I'm using wpa_supplicant or iwd has no effect on this. This time the log also had: plasmashell[570]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height" kded5[524]: plasma-nm: Unhandled active connection state change: 3 kded5[524]: plasma-nm: Unhandled active connection state change: 1 kded5[524]: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." kdeconnectd[581]: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." NetworkManager[317]: <info> [1622320307.2731] audit: op="statistics" arg="refresh-rate-ms" pid=329669 uid=1000 result="success"
What component should this bug be filled against then?
*** This bug has been marked as a duplicate of bug 406110 ***