Bug 347795

Summary:	Notifications icon stays active after all updates were installed
Product:	[Unmaintained] muon	Reporter:	soee <kontakt>
Component:	notifier	Assignee:	Jonathan Thomas <echidnaman>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aleixpol, sgmoore, sitter, valorie.zimmerman
Priority:	NOR
Version First Reported In:	5.3.0
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
URL:	https://youtu.be/6BM5FOY0tXU
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description soee 2015-05-16 13:00:09 UTC

If we have some updates available on our system, we can see an extra icon (green or red - depends of updates) in systray that informs us about new packages. If we install all updates, this icon stays in systray and if we click on it, we can see outdated information about number of available updates.

Reproducible: Always

Steps to Reproduce:
1. Refresh packages list to get some new updates available
2. Notifications icon should show up in systray
3. Install all available updates
4. Notifications icon stays active and if we click on it, we see invalid number of updates available

Actual Results:  
Notifications icon stays active after all updates are installed and shows outdated number of available packages to be updated.

Expected Results:  
After all updates are installed, notifications icon should not be visible.

Comment 1 Scarlett Moore 2015-05-16 13:02:39 UTC

I can confirm this behaviour. It started about the time when the mass spamming of updates was fixed.

Comment 2 Valorie Zimmerman 2015-05-16 20:16:51 UTC

I can also confirm. The stale information seems to stay until updated by the next changes. For instance, yesterday the icon stayed green and reported that I had 6 updates, even after I had downloaded and installed them.

This morning the icon was red, and now it continues to report that there are 3 updates, one of which is a security update. After running the updates, it continues red, still reporting 3 updates available, of which 1 are security updates.

Comment 3 Aleix Pol 2015-05-20 12:18:19 UTC


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