This should be fixed for 2.1.1, if that's not the case, please re-open then.

*** Bug 326523 has been marked as a duplicate of this bug. ***

*** Bug 326367 has been marked as a duplicate of this bug. ***

*** Bug 326176 has been marked as a duplicate of this bug. ***

*** Bug 326171 has been marked as a duplicate of this bug. ***

Please, provide details about the problem causing the issue and the fix, so that it can be backported to distros. Unexperienced users (who cannot use console based tools) are likely to miss all their security updates because of this bug.

On November 5, 2013 04:01:19 PM you wrote:
> https://bugs.kde.org/show_bug.cgi?id=326256
> 
> Sergio <sergio.callegari@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |sergio.callegari@gmail.com
> 
> --- Comment #6 from Sergio <sergio.callegari@gmail.com> ---
> Please, provide details about the problem causing the issue and the fix, so
> that it can be backported to distros. Unexperienced users (who cannot use
> console based tools) are likely to miss all their security updates because 
of
> this bug.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
============================================
Thanks for your reply - Have quit using the upgrade - constantly getting too 
many problems. Have reverted to 12.10 & will wait for the upgrade to be 
completed.

(In reply to comment #6)
> Please, provide details about the problem causing the issue and the fix, so
> that it can be backported to distros.

Ditto. I'd like to know the current status of the fix (i.e. v 2.1.1) - is it coded & tested, released for distribution, available in a PPA, what?

Thanks
Rick

It has already been released and will be available to you as an update soon, I know the Kubuntu package was submitted already.

Unfortunately the current situation with Muon is complicated by an undocumented soname bump, so we need to figure out the least invasive way to fix that before we upload 2.1.1.

Muon updater works now for me since the update which was delivered on 2013-11-19.

(In reply to comment #11)

Agree, update to 2.1.1 just came through, Muon Updater now workig fine :-)

For me too. :) Thanks.

All this confusing Programer Jargon. Cant you just give us a string to run in the terminal? SInce the updater does not work at all? 

It just searches and searches with no updates displayed, or access to the "Install Updates" button(greyed out).


Please and Thank-you...

Muon Updater now working fine! The latest updates fixed it I presume.
Thanks for your help.

Created attachment 88407 [details]
attachment-25445-0.html

THANK U... 0/:-}
On Aug 20, 2014 9:50 AM, <bumpysax@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=326256
>
> --- Comment #15 from bumpysax@gmail.com ---
> Muon Updater now working fine! The latest updates fixed it I presume.
> Thanks for your help.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

Can this bug be reopened, please.

This is happening again (kubuntu 64 bit 14.04, muon 2.20 on kde framework 4.13.3).

when muon-updater is fired up, it briefly shows the packages to be updated (just a flash), then erases the display shows a progress indicator and sits there for ever.

strace reveals some good > 10 processes opened in the process and then one of them waiting for something that is temporarily unavailable. Forever.

Since package management and the effective provision of security fixes is the very point of a distribution, this is taking a lot away from kubuntu.

As an addendum. In /some/ occasions logging out of kde, logging in again, relaunching muon-updater gives the followin behavior.

- muon windows opens with all the updates
- screen is erased immediately after
- muon waits for about 1m with progress bar
- list of packages appears again.

This does not change things a lot, though. People see a white page, do not wait, close it, do not update packages, do not apply security fixes.

Launching muon from the command line gives following warning

/usr/bin/python3: can't find '__main__' module in ''

do not know if this is important, though.

I am seeing exactly the same behavior as Sergio described again. For me it was also fixed for a while, but the problem came back. (Kubuntu 14.04 KDE 3.13.3)