Bug 355181

Summary: No matter what I do after a successful updates, there is still an icon notification in system tray telling Security updates are available
Product: [Applications] Discover Reporter: Vlastimil Burian <burian.vlastimil2>
Component: Updates (interactive)Assignee: Jonathan Thomas <echidnaman>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol, burian.vlastimil2, sitter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
URL: http://prntscr.com/91i1c0
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Vlastimil Burian 2015-11-11 10:38:19 UTC 
On Kubuntu 15.10 no matter what I do after a successful updates, there is still an icon notification in system tray telling Security updates are available.

I tried `apt-get update`,  `apt-get ugrade`,  `apt-get dist-upgrade`, no updates found. I re-checked for updates clicking on Update in system tray.  It says The software on this computer is up to date. But there still is the icon in system tray telling Security updates are available.

Reproducible: Always

Steps to Reproduce:
I have no idea on how to reproduce it, so far I didn't restart computer, so this might solve it. But it is not telling me, it needs to restart.

Actual Results:  
Security updates are available.

Expected Results:  
No updates are available.

Screenshot
http://prntscr.com/91i1c0
Comment 1 Vlastimil Burian 2015-11-12 19:49:02 UTC 
I haven't yet restarted the machine, will wait for your response

vlastimil@vb-nb-kubuntu:~$ uptime
 20:44:42 up 2 days, 13:21

after today's updated I have in the tray the following, it is accumulating
http://prntscr.com/921qs7
Comment 2 Aleix Pol 2015-11-13 00:10:57 UTC 
Here's the problem. We're waiting for these paths to change, whenever they are, the notifier is refreshed:
/var/lib/apt/lists/
/var/lib/apt/lists/partial/
/var/lib/update-notifier/updates-available
/var/lib/update-notifier/dpkg-run-stamp

For some reason, it never happened.
Comment 3 Aleix Pol 2015-11-13 00:16:09 UTC 

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