Comment 4 for bug 89676

I just had the same situation.

I happend when one package during the upgrade failed to configure. Update-manager returned to its screen and reported one available update in the header without showing anything in the treeview. After closing/reopening update-manager it reported (correctly) that there is a borken package.