Description of problem: I am unable to create non-persistent notifications in GNOME. Non persistent means that only the banner pops-up but the notification won't stay in the overview after the banner closes due to timeout. Easily reproducible by notify-send: (1) notify-send -t 0 aaa bbb ---> timeout 0 means persistent per the specification -> banner shows and if the timeout misses, the notification resides in the overview (2) notify-send -t 1 aaa bbb ---> timeout explicitly defined which means the user (or application developer) wants the notification to perish after the timeout -> banner shows and if the timeout misses, the notification resides in the overview (3) notify-send aaa bbb ---> no timeout specified -> banner shows and if the default timeout misses, the notification resides in the overview while in KDE: (1) notify-send -t 0 aaa bbb ---> timeout 0 means persistent per the specification -> pop-up shows and if the timeout misses, the notification resides in the overview (2) notify-send -t 1 aaa bbb ---> timeout explicitly defined which means the user (or application developer) wants the notification to perish after the timeout -> pop-up shows and if the timeout misses, the notification perishes (3) notify-send aaa bbb ---> no timeout specified -> pop-up shows and if the timeout misses, the notification perishes While I believe case (3) is up to the DE developers to set the sane default, I am strongly convinced that if the timeout is explicitly requested (2), DE must obey it and make the notification non-persistent. Version-Release number of selected component (if applicable): gnome-shell-3.16.0-1.fc22
Same behaviour in gnome-shell 3.18.5 (Fedora 23), and also notify-send -t 0 aaa bbb notify-send -t 1000 aaa bbb notify-send -t 10000 aaa bbb notify-send -t 100000 aaa bbb all of them give the same result (notification popup shows for some seconds, then disappears)
This is intentional: https://wiki.gnome.org/Design/OS/Notifications/#Non-Goals The notification timeout has not been configurable in GNOME since gnome-shell 3.0, you would need to convince upstream designers to change that. But note that there have been two major redesigns to address various issues with previous iterations, where a user/app specified timeout never came up - so chances to bring them back after five years are rather slim.