In general, it never makes sense to show a notification in response to a successful direct user action. The user expects that their action is completed successfully; there's no reason to say "the thing you did worked!" Applying this principle to plasma-nm, there's no reason to show a "Network disconnected" notification when the user clicks on the "Disconnect" button in the plasma-nm network list. This notification should only appear in response to a disconnection that was not initiated by the user.
always found that unnerving too, but luckily one can switch it off with 3 clicks. Cluttering the desktop with somewhat pointless notifications is being frowned upon.
at least we have a "do not disturb" mode by now, which I make use of heavily!
An additional element to assess this bug: a problem I found with this behavior is that at times, the notifications prevent the user from using plasma-nm to connect to another network until the user closes them, because they cover the widget.
That's fixed in Plasma 5.17.
"Network disconnected" notification only appears after plasma-nm popup to be closed. Operating System: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1
*** Bug 421369 has been marked as a duplicate of this bug. ***
This is quite silly, I'm sure you could fix it when you get a moment Nate ;)
Believe it or not, I have looked into it, and it's not as easy as it seems, because you need to disambiguate the sources of the disconnection (happened naturally vs user-initiated) and the code isn't set up for this right now. It needs some refactoring to support it.
Sadly, I fully believe this. I don't know why, and this might be due to the recent improvements related to the notifications, this has been less an issue for me. Ah, yes, obviously after rereading my comment from last year: the notifications do not cover the network widget anymore!
Bulk transfer as requested in T17796