| Summary: | Revoke/delete "battery critical" notification once battery is adequately charged again | ||
|---|---|---|---|
| Product: | [Unmaintained] Powerdevil | Reporter: | Albert Vaca Cintora <albertvaka> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | kde, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.16.4 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot of these two notifications | ||
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. :) 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. 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. > 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.
|
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.