Bug 438834

Summary: Discover Notifier Icon incorrectly shows up with "Updates Available" notification.
Product: [Applications] Discover Reporter: Sebastian Gauna <gaunas>
Component: NotifierAssignee: Aleix Pol <aleixpol>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns, h3zvqfca, terranceb
Priority: NOR    
Version: 5.22.1   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sebastian Gauna 2021-06-17 22:59:37 UTC
SUMMARY
Discover Notifier shows the "Updates Available" icon in the System Tray but there are actually no updates.

STEPS TO REPRODUCE
Just start the system and the tray icon appears.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.22 User Edition
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION 
It doesn't matter if you go to Discover and click "Check for Updates" (which shows no updates), or if you right click the system tray icon and select "Refresh" (which does nothing), or if you do a pkcon refresh && pkcon update (wich shows no updates available), there is no way to make the icon dissapear unless you explicitly right click on it an select "QUIT"

I don't think that it has something to do with this problem but know that I uninstalled snap, anyway this problem started very recently and I uninstalled snap long time ago.
Comment 1 Terrance Brown 2021-06-17 23:08:24 UTC
*** Bug 438826 has been marked as a duplicate of this bug. ***
Comment 2 Terrance Brown 2021-06-17 23:11:29 UTC
I can confirm. Brand-new installation of KDE Neon still shows the update notification on startup despite being fully updated. I've also run pkcon to double-check, and there are indeed no outstanding updated.

My Arch laptop running Plasma also has the same issue.
Comment 3 Sebastian Gauna 2021-06-17 23:13:55 UTC
My KDE Neon is not a brand new installation, I don't remember exactly but It's been several months since I've installed it.
Comment 4 Patrick Silva 2021-06-18 00:36:36 UTC

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