Bug 360141 - muon software mirror update fails, no matter what mirror I choose
Summary: muon software mirror update fails, no matter what mirror I choose
Status: RESOLVED DOWNSTREAM
Alias: None
Product: muon
Classification: Unmaintained
Component: muon (other bugs)
Version First Reported In: 5.4.2
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-05 20:27 UTC by Mark Rudeseal
Modified: 2016-03-16 14:39 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Rudeseal 2016-03-05 20:27:33 UTC
tried to check for updates in both muon updater and muon package manager. during the sources check, it stops and reports failed. I tried different mirror sources and even reinstalling Kubuntu 15:10 and still the error persists

Reproducible: Always
Comment 1 Aleix Pol 2016-03-07 10:37:37 UTC
Does apt-get work just fine there? This seems like a weird error.
Comment 2 Mark Rudeseal 2016-03-10 00:37:52 UTC
error discontinues if I uncheck google from ppa.
Comment 3 Aleix Pol 2016-03-10 18:45:09 UTC
Then the problem is the PPA? Or with apt-get it works?
Comment 4 Mark Rudeseal 2016-03-14 00:21:23 UTC
no. google would not update by using the PPA.  I believe since linux updated the key signature recently now with google chrome checked as check for updates is now functioning correctly.  It apparently was a key signature
Comment 5 Mark Rudeseal 2016-03-14 00:22:03 UTC
no. google would not update by using the PPA.  I believe since linux updated the key signature recently now with google chrome checked as check for updates is now functioning correctly.  It apparently was a key signature
Comment 6 Mark Rudeseal 2016-03-14 00:24:11 UTC
no, apt-get, nor package updates was not working..it is now by the way on all possible ways to update
.
Comment 7 Aleix Pol 2016-03-16 14:39:49 UTC
If apt-get doesn't work, it can't be an issue in Discover.

Please contact your distribution in order to figure out what's the issue.