https://bugs.kde.org/show_bug.cgi?id=358983
Bug ID: 358983
Summary: Provide option to retain non-persistent notifications
in the history
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: Notifications
Assignee: mklape...@kde.org
Reporter: kokotokos...@yopmail.fr
CC: plasma-b...@kde.org
In bug #342260 Edmundson says:
> In Plasma 5.x it was changed so they only appear in the backlog if the
> notification is persistent (i.e if the timeout == 0") That's "-t 0" on
> notify-send.
That is reasonable behaviour, I suppose. However, I believe there are user
scenarios where it is extremely useful to remember non-persistent
notifications. An example of such would be a long operation (e.g., copying a
large file) running unattended.
Reproducible: Always
Steps to Reproduce:
1. Pick a large file, or a slow disk, or a remote host on a 9600 baud modem.
Any combination that'll take a while.
2. Launch a copy or move operation, e.g., from Dolphin.
3. Go away for a while.
4. Come back.
5. Wonder what happened to your operation. Did it complete? Fail? Something
else?
Actual Results:
If the notification was non-persistent, as Dolphin's is, it will have
disappeared from screen and never gone into the history. You will not know how
it did.
Expected Results:
A configurable setting in the notifications widget should allow the user to
force notifications to persist.
It is reasonable that a notification for certain “routine” operations should be
made non-persistent by the developer, however in certain scenarios that may not
be in line with the user's wishes.
--
You are receiving this mail because:
You are watching all bug changes.
