Bug 411218 - Revoke/delete "battery critical" notification once battery is adequately charged again
Summary: Revoke/delete "battery critical" notification once battery is adequately char...
Status: RESOLVED LATER
Alias: None
Product: Powerdevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.16.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-23 20:28 UTC by Albert Vaca Cintora
Modified: 2019-08-27 06:54 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot of these two notifications (78.55 KB, image/png)
2019-08-23 20:28 UTC, Albert Vaca Cintora
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Albert Vaca Cintora 2019-08-23 20:28:57 UTC
Created attachment 122308 [details]
Screenshot of these two notifications

I don't need to have a persistent notification indicator (that I have to dismiss manually) because 45 minutes ago I was low on battery, or because 38 minutes ago my wifi connection dropped.
Comment 1 Nate Graham 2019-08-24 13:32:04 UTC
The connection disconnected notification will not show up in history in Plasma 5.17.0.

The other issue is an example more general problem that we don't have the ability to remove notifications that are in the history. I think we should. :)
Comment 2 Albert Vaca Cintora 2019-08-26 23:48:14 UTC
There should be no need to revoke the notification. If the notification is transient it should not end up in the history in the first place.
Comment 3 Nate Graham 2019-08-27 00:29:35 UTC
Yes, but "Battery critical" notifications are a textbook example of what a critical notification should be, and critical notifications aren't transient.

Maybe critical notifications shouldn't go into the history either, because they're always manually dismissed (and therefore seen) by the user.
Comment 4 Kai Uwe Broulik 2019-08-27 06:54:56 UTC
> If the notification is transient

All of them are transient, making the history useless. This is unfixable with the current fdo notification spec. I have some ideas how to address this but right now can't do.