Bug 502422

Summary: Notifications suppressed by DND mode that are configured to not appear in the history can't be found after you edit DND mode
Product: [Plasma] plasmashell Reporter: Nate Graham <nate>
Component: NotificationsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde
Priority: NOR Keywords: usability
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nate Graham 2025-04-04 19:42:01 UTC 
STEPS TO REPRODUCE
1. Enter DND mode
2. run `notify-send-send foo bar` in a terminal window
3. Exit DND mode -> A notification appears telling me I missed a notification while DND mode was active
4. Look for the missed notifications


OBSERVED RESULT
The missed notification cannot be found in the history or anywhere else.


EXPECTED RESULT
The missed notifications appear in the history.


ADDITIONAL INFORMATION
This happens because `notify-send` notifications count as "Other Applications", and those are configured to not appear in the history. And this is the problem: the "Show in history" setting should be honored normally, but *not* when a notification comes in during DND mode. The problem will be seen with real apps too if you uncheck "Show in history" for them.
Comment 1 Kai Uwe Broulik 2025-04-04 20:01:06 UTC 
Not show in history means not show in history.
Comment 2 Kai Uwe Broulik 2025-04-04 20:01:58 UTC 
$ notify-send -h string:desktop-entry:firefox foo bar
Comment 3 Nate Graham 2025-04-04 20:09:32 UTC 
I don't want to see these notifications in the history when they're normal popups, because I already saw them when they appeared.

But while DND mode is active, that reason doesn't apply anymore: because DND mode is active, I don't see the popups at all, and then not seeing them in the history either means I can never seen them at all.
Comment 4 Nate Graham 2025-06-03 22:49:23 UTC 
Forward-duping to the same bug report I opened later, forgetting that I had already opened this one!

*** This bug has been marked as a duplicate of bug 504571 ***