Bug 342260 - Non persistent notifications no longer appear in the backlog at all
Summary: Non persistent notifications no longer appear in the backlog at all
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.1.1
Platform: Other Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
: 349499 350694 357750 358978 372548 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-27 21:38 UTC by illumilore
Modified: 2017-08-11 13:59 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description illumilore 2014-12-27 21:38:13 UTC
When using plasma5, many notification icons no longer show up in the system tray, such as audacious, nomachine, or the notification icon that comes up when using notify-send. the icons also get stuck alot, like network manager continually showing the rotating circle that it shows when connecting even though it connected long ago, or the downward arrow that brings up status and notifications will freeze halfway through its animation where it rotates to an upward arrow.

Reproducible: Always
Comment 1 David Edmundson 2014-12-27 23:39:46 UTC
Can you stick to one issue per report.  The part about the continually spinning wheel is very unrelated, same for this downward arrow. Otherwise we'll fix one part and the rest will get lost.

From now on I'm treating this as just this notifications not appearing in the notification backlog.

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. 

I think this is up for some debate as you're not the first commenter to mention this.
Comment 2 Martin Klapetek 2014-12-27 23:50:13 UTC
I believe that these reports are the result of kde4 putting _everything_ in the tray popup, which was technically not correct. In Plasma5 we just made it correct by following the specification properly.

If they are not made persistent by the author, they should not persist. If the developer wants them to stay behind, it is in his hands.

Furthermore I'd like to see the paradigm to change a bit and push more towards StatusNotifiers for persistent things that are supposed to notify the user. They offer greater flexibility and are not hidden away in a popup which you can easily miss.
Comment 3 illumilore 2014-12-28 00:00:04 UTC
But what about all of the other applications that don't show up in the system tray, such as audacious and nomachine? Those used to work in plasma4, but not in plasma5. Gtk apps that use the system tray in general also seem to be bugged with not showing up.
Comment 4 David Edmundson 2014-12-28 00:00:59 UTC
wait, now we're talking about something completely different.

They aren't the notifications sent by notify-send.
Comment 5 David Edmundson 2014-12-28 00:11:18 UTC
For those ones, please read: http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/

Hope that has everything you need,
Comment 6 illumilore 2014-12-28 00:53:11 UTC
I have verified that I already have libappindicator1 and 3-1 installed, along with sni-qt, but the gtk apps are still not showing up.
Comment 7 David Edmundson 2014-12-28 12:53:14 UTC
I /think/ GTK needs compiling with libappindicator. 

Which distro are you on? They might need prodding.

app indicator changes GTK apps from using Xembed (the 90s way of putting an item into a panel) into sending data over DBus using the StatusNotifier specification. 

The Plasma side of using StatusNotifier clearly works, as we have plenty of other things using it. We are not going to re-support xembed, as it's been deprecated for over 5 years and has a lot of problems)
Comment 8 illumilore 2014-12-28 18:08:50 UTC
OpenSuse 13.2 64bit
Comment 9 illumilore 2015-01-01 23:55:55 UTC
So is it because opensuse doesn't have the correct things installed when it is being built?
Comment 10 Martin Klapetek 2015-01-12 15:07:38 UTC
I suggest you ask the openSuse folks, or maybe a file a bug with their packaging?

Also please open separate bug report for separate issues, it makes tracking and triaging harder when there are multiple bugs in one report.

Thanks
Comment 11 illumilore 2015-01-14 21:09:47 UTC
Why is it wontfix if your comment makes it seem to be upstream instead?
Comment 12 Martin Klapetek 2015-01-14 21:12:10 UTC
Because your report is titled "Non persistent notifications no longer appear in the backlog at all" and I already explained why.

Then you asked about your missing icons in systray (and that's what I suggested as upstream issue) and that's completely unrelated issue to the original report.

As I said, please open separate bugs for separate issues, the notification history, this report, is closed.
Comment 13 Martin Klapetek 2015-06-23 22:24:40 UTC
*** Bug 349499 has been marked as a duplicate of this bug. ***
Comment 14 Martin Klapetek 2015-07-28 10:58:55 UTC
*** Bug 350694 has been marked as a duplicate of this bug. ***
Comment 15 Stuart K. Smith 2015-10-23 19:28:25 UTC
So home come using notifier-send with -t 0 still doesn't leave the notification in Status and Notifications > Notifications ? Isn't that where notification history is supposed to be? The -t 0 option leaves it on the desktop until you manually close it, but it's still not in history. Why even have the history in Status and Notifications if there's never anything in there?

Not resolved and not fixed, IMO.

Kubuntu 15.04
Comment 16 Martin Klapetek 2015-10-23 19:33:42 UTC
Works here. Please update your Plasma.
Comment 17 Stuart K. Smith 2015-10-23 20:34:39 UTC
Thanks for tremendously quick response and your help despite my apparent poor attitude. 

I booted into Wily (Kubuntu 15.10) and tested it and it did not work. I don't use 15.10 daily yet, so I hadn't updated it in a while, so I did that (279 packages) and rebooted back into 15.10 and it worked as advertised!

Booting back into 15.04, it now works here as well. I had updated some packages recently but hadn't rebooted in a week or so - so either a recent package update fixed it or It appears the issue was fixed very recently or something else was blocking it on my system. 

Resolved and FIXED, IMO. 
Thanks again.
Comment 18 Martin Klapetek 2016-02-03 19:31:32 UTC
*** Bug 357750 has been marked as a duplicate of this bug. ***
Comment 19 Martin Klapetek 2016-02-04 13:11:53 UTC
*** Bug 358978 has been marked as a duplicate of this bug. ***
Comment 20 Martin Klapetek 2016-11-16 18:54:00 UTC
*** Bug 372548 has been marked as a duplicate of this bug. ***
Comment 21 Martin Klapetek 2017-03-24 23:35:44 UTC
*** Bug 378032 has been marked as a duplicate of this bug. ***