Bug 364638 - Discover shows false information about updates state
Summary: Discover shows false information about updates state
Status: RESOLVED DUPLICATE of bug 366196
Alias: None
Product: Discover
Classification: Applications
Component: Updates (interactive) (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-22 16:28 UTC by apache
Modified: 2016-07-28 10:48 UTC (History)
1 user (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 apache 2016-06-22 16:28:11 UTC
When I opened Discover today not from panel widget indicator but from menu I had this button on upper panel telling me that there were no updates but when I used option check for updates it appeared that there were some updates. My suggestion is: when the program is opened, the button should show information "check for updates" and when clicked and repositories checked only then the information on button should change to "No updates" or "Update". This would make more sense to me. So I suggest one button changing its state and indicating the real state. After update is made the information should be as it is now that updated successfully but the button should come back to "Check for updates". Showing that there are no updates just because the program has not check it yet is not showing the real state.

An example of such situation:
https://bugsfiles.kde.org/attachment.cgi?id=99642

Reproducible: Always
Comment 1 Thomas Pfeiffer 2016-06-30 11:51:13 UTC
You are right, it should only show that there are no updates right after there was a check which resulted in no updates being available.
Comment 2 Aleix Pol 2016-07-01 14:03:17 UTC
Under which platform are you testing this?
Comment 3 apache 2016-07-01 15:25:48 UTC
Me? KDE Neon developer edition stable (Plasma 5.6.5)
Comment 4 Aleix Pol 2016-07-28 10:48:11 UTC

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