Bug 360098 - Discover says updates available when there aren't
Summary: Discover says updates available when there aren't
Status: RESOLVED DUPLICATE of bug 347602
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-04 23:43 UTC by gurpal2000
Modified: 2016-03-17 00:31 UTC (History)
2 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 gurpal2000 2016-03-04 23:43:06 UTC
Using netrunner 17. The discover tray icon has a little red cross next to it. When i click it it says there are updates available. When Update is clicked, Discover loads, a spinner is seen followed by a big Green tick saying the software on this computer is up to date.

sudo update/upgrade says there are no updates pending.

Summary: Inconsistent information by Discover and the tray icon

Reproducible: Always

Steps to Reproduce:
1.The discover tray icon has a little red cross next to it.
2.When i click it it says there are updates available
3.When Update is clicked, Discover loads, a spinner is seen followed by a big Green tick saying the software on this computer is up to date.

Actual Results:  
No change to packages. Tray icon remains in the same state.

Expected Results:  
Either packages should start updating or the tray icon and Discover should say "nothing to update"
Comment 1 Aleix Pol 2016-03-16 14:48:12 UTC
Hi,
Does this always happen or just after upgrading? It's probably related to 347602.
Comment 2 gurpal2000 2016-03-16 14:54:10 UTC
I just done an upgrade now using it, but the red cross remains.
Comment 3 Aleix Pol 2016-03-16 15:25:56 UTC
What happens if you reboot Plasma/the system?
Comment 4 gurpal2000 2016-03-17 00:28:47 UTC
If i reboot, then the icon turns green and correctly reflect the state.
Comment 5 Aleix Pol 2016-03-17 00:31:28 UTC

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