| Summary: | prevent stacking up | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | grannie |
| Component: | Notifications | Assignee: | Kai Uwe Broulik <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kdelibs-bugs-null, nate, nicolas.fella, plasma-bugs-null |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 5.23.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
grannie
2021-10-21 10:10:26 UTC
It's a legitimate issue, but hard to imagine how we could fix it. What would you propose to do instead when an app sends a lot of notifications in a short period of time? ok my current specific case are device notifications due to app-updates which are relayed to the pc. The phone "updates" the notifications (progress bar) - the pc seems to get multiple incoherent notifications about that So here would be the opportunity to "update" notifications (or skip if already notified) The general case: Easy would probably be a max stack size - like: show only up to three notification boxes at the same time - or group them by sending application A similar problem occurs when I restart akonadi (with several mail accounts attached) - they all complain about akonadi not being responsive - that may be grouped? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |