Bug 326658 - Muon Updater says the system is up-to-date even if there are updates available
Summary: Muon Updater says the system is up-to-date even if there are updates available
Status: RESOLVED DUPLICATE of bug 326367
Alias: None
Product: Discover
Classification: Applications
Component: Updates (interactive) (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-26 00:12 UTC by Nick
Modified: 2016-03-02 13:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
muon-updater (59.21 KB, image/png)
2013-10-26 00:13 UTC, Nick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nick 2013-10-26 00:12:01 UTC
When I get a notification about updates I click on the icon and muon-updater opens but it says the system is up-to-date when it's really not. The install updates button can still be clicked and updates will be installed but it's really annoying because I can't see what packages are available for update and could be confusing for some users.

Reproducible: Always

Steps to Reproduce:
1. Wait for updates to be available
2. Click on the notification icon to open muon-updater
Actual Results:  
It says the system is already up-to-date

Expected Results:  
It should say there are updates available and list what packages are updatable
Comment 1 Nick 2013-10-26 00:13:48 UTC
Created attachment 83121 [details]
muon-updater
Comment 2 Nick 2013-10-26 00:14:25 UTC
Forgot to mention this is on Kubuntu 13.10 with KDE 4.11.2
Comment 3 Nick 2013-10-27 23:33:40 UTC
This problem is actually worse on my laptop as the install updates button is grayed out unlike the instance described above. This pretty much makes installing updates impossible unless you know how to do it through muon or apt-get.
Comment 4 Nick 2013-10-30 19:19:31 UTC
Ubuntu backported 2.1.0. Problem still exists.
Comment 5 Jekyll Wu 2013-11-01 08:02:20 UTC

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