Bug 409323 - Revoke "Network Disconnected" notification once the network is re-connected
Summary: Revoke "Network Disconnected" notification once the network is re-connected
Status: RESOLVED FIXED
Alias: None
Product: plasma-nm
Classification: Plasma
Component: general (show other bugs)
Version: 5.16.2
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords: usability
: 409361 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-06-30 05:04 UTC by Nate Graham
Modified: 2020-04-15 14:09 UTC (History)
4 users (show)

See Also:
Latest Commit: https://cgit.kde.org/plasma-nm.git/commit/?id=9e032bf5107833c57279c4d4d89ce0567e26dc26
Version Fixed In: 5.19.0

Attachments
How my notification history looks most of the time (165.31 KB, image/png)
2019-06-30 05:04 UTC, Nate Graham 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2019-06-30 05:04:58 UTC 
Created attachment 121228 [details]
How my notification history looks most of the time

My notification history fills up with "Network Disconnected" notifications throughout the day as my computer periodically loses wifi and then re-connects. The notifications become useless spam once the network has re-connected, so I would recommend revoking them once the network re-connects. That way there will only ever be a maximum of one (if the network is still disconnected), and most of the time there will be zero (if the disconnected network has since re-connected).
Comment 1 Kai Uwe Broulik 2019-07-02 06:43:43 UTC 
*** Bug 409361 has been marked as a duplicate of this bug. ***
Comment 2 Jan Grulich 2019-07-10 09:58:14 UTC 
I experience a similar issue with notifications from Konversation or from KMail. Notificatons in plasma-nm have KNotification::CloseOnTimeout set, they should be automatically closed, which is not happening from some reason.

@Kai, do you have idea what could be wrong? I'm running Plasma on Wayland if that is relevant.
Comment 3 Kai Uwe Broulik 2019-07-10 12:12:33 UTC 
Once in history, there's nothing you can do.
We could add a "don't preserve in history flag" maybe or at least revoke the notification when its popup is still shown.
Comment 4 Nate Graham 2019-07-10 13:35:25 UTC 
(In reply to Kai Uwe Broulik from comment #3)
> Once in history, there's nothing you can do.
> We could add a "don't preserve in history flag" maybe or at least revoke the
> notification when its popup is still shown.
Hmm, I must have misunderstood some of our recent conversations then. I was left with the impression that it was possible for an app to revoke its notification and for that notification to disappear from the history.

If this isn't currently possible, what's blocking it from being possible?
Comment 5 Kai Uwe Broulik 2019-07-10 13:36:50 UTC 
> If this isn't currently possible, what's blocking it from being possible?

A redesign of KNotification class to have its lifetime not bound to the expiration of the popup and an extension to the freedesktop Notification spec to allow applications to revoke notifications after the fact. And then persuading 3rd party apps to also use that.
Comment 6 Nate Graham 2019-07-11 02:08:38 UTC 
Are there any other ways we could solve the issues brought up in this bug report? It's pretty annoying having an otherwise fairly clean notification history fill up with "Network disconnected" entries.