Distribution Upgrade "Error authenticating some packages"

[Barnsta (Barnendu Goswami)]

Binary package hint: update-manager

Adept found 152 updates.....failed to apply them (because of libportaudio).
Then offered/noticed update for "Distribution Upgrade" - but then failed with the above titled error.
This took place under Kubuntu 7.10

[Michael Vogt (mvo)]

Thanks for your bugreport.

Could you please hit the "check" or "reload" button before running the upgrade and see if that fixes the issue?

[Barnsta (Barnendu Goswami) (barnendu-goswami)]

Managed to get out of the loop/cycle, by:

1. restarting system
2. killing "adept_notifier" and "adept_update" (sent SIGQUIT)
3. refreshing/reloading in Adept
4. applied updates
5. quit/cancelled distribution upgrade
6. restarted system
7. wasn't offered distribution upgrade after that?

I know it's a bit of an M$ style workaround - almost sure that if I knew Ubuntu a little better, could probably restart a few services and get around the restart.

Interestingly; when I ran adept-upgrade from konsole, I got this:
{
mylogin@mypcname:~/Documents$ sudo adept_updater
[sudo] password for mylogin:
kapture::PkgSystem::PkgSystem()
Error: "/var/tmp/kdecache-mylogin" is owned by uid 1000 instead of uid 0.
debconf
adduser
sysklogd
snort-mysql
oinkmaster
kdecore (KProcess): WARNING: _attachPty() 36
UpgradeWizard::checkForDistUpgrade
Error: "/tmp/kde-mylogin" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-mylogin" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-mylogin" is owned by uid 1000 instead of uid 0.
debconf
adduser
sysklogd
snort-mysql
oinkmaster
mylogin@mypcname:~/Documents$
}

I'm not sure if this is expected behaviour - but I've seen similar errors on another system installed from the same version of the Kubuntu 7.10 live dvd.

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this report because you reported this bug a while ago and there is no recent duplicate nor user mentioning having the issue on Intrepid. If this is still an issue, don't hesitate to reopen the report. Thanks again!