update-manager -d -c hung in "fetching is complete"

[Otus]

I tried to upgrade from raring to saucy using update-manager -d -c, but the upgrade hung after reporting "fetching is complete" in the "setting new software channels" step.

I tried to strace the "saucy" processes, but I didn't really know what I was doing. It seemed the parent process was calling poll and the children all waiting on futexes... so maybe some kind of deadlock?

Will try again to see if it is reproducible.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: update-manager 1:0.186.2
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu8.3
Aptdaemon:

Architecture: amd64
Date: Thu Oct 17 17:08:08 2013
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'1382018876'
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'315'
 b'com.ubuntu.update-manager' b'window-width' b'484'
InstallationDate: Installed on 2012-11-10 (341 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: Upgraded to raring on 2013-10-17 (0 days ago)
---
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
CrashDB: ubuntu
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2012-11-10 (341 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
NonfreeKernelModules: fglrx
Package: ubuntu-release-upgrader (not installed)
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Tags: raring dist-upgrade
Uname: Linux 3.8.0-31-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-10-17 (0 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
VarLogDistupgradeAptlog:
 Log time: 2013-10-17 17:11:46.033303
 Log time: 2013-10-17 17:12:21.013451
 Log time: 2013-10-17 17:43:06.073213
VarLogDistupgradeTermlog:

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1241010

[Otus (jan-varho)]

Ok, second try the process got past that step, but while I was AFK it simply aborted. No error messages in the console.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1241010
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Otus (jan-varho)]

apport information

[Otus (jan-varho)]

apport information

[Otus (jan-varho)]

apport information

[Otus (jan-varho)]

apport information

[Otus (jan-varho)]

apport information

[Otus (jan-varho)]

Not sure it did what it should have... It said package ubuntu-release-upgrader does not exist.

[Brian Murray (brian-murray)]

For some reason the handbrake PPA you have enabled is not being disabled and it does not publish any packages for saucy. If you disable that PPA the upgrade should proceed.

[Otus (jan-varho)]

Yes, disabling that PPA allowed the upgrade to continue.

[Brian Murray (brian-murray)]

Looking at the log file I see this message:

2013-10-17 17:12:25,353 WARNING mirror check skipped, *overriden* via config

This means that one of the following was set on your system:

        # skip mirror check if special environment is set
        # (useful for server admins with internal repos)
        if (self.config.getWithDefault("Sources","AllowThirdParty",False) or
            "RELEASE_UPRADER_ALLOW_THIRD_PARTY" in os.environ):
            logging.warning("mirror check skipped, *overriden* via config")
            mirror_check=False

Had you set RELEASE_UPRADER_ALLOW_THIRD_PARTY in your environment?

[Otus (jan-varho)]

> Had you set RELEASE_UPRADER_ALLOW_THIRD_PARTY in your environment?

Not intentionally, at least.