update-manager crashes on upgrade from 12.04 -> 12.10 Beta 2

Bug #1058052 reported by Mike Pasche
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

e:error, pkgProblemResolver::Resolve generated breaks

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.14.9
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Fri Sep 28 07:08:27 2012
GsettingsChanges:
 com.ubuntu.update-manager first-run false
 com.ubuntu.update-manager launch-time 1348830448
 com.ubuntu.update-manager show-details true
 com.ubuntu.update-manager window-height 530
 com.ubuntu.update-manager window-width 600
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: Upgraded to precise on 2012-09-28 (0 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
VarLogDistupgradeTermlog:

Revision history for this message
Mike Pasche (mike-d-pasche) wrote :
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

In VarLogDistupgradeMainlog.txt:

2012-09-27 23:32:16,618 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.'

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

In VarLogDistupgradeAptlog.txt(repeated messages targeting libglib and glib-networking):

Investigating (9) libglib2.0-0 [ amd64 ] < 2.32.3-0ubuntu1 -> 2.34.0-1ubuntu1 > ( libs )
Broken libglib2.0-0:amd64 Breaks on glib-networking [ amd64 ] < 2.32.1-1ubuntu2 -> 2.34.0-0ubuntu1 > ( libs ) (< 2.33.12)
  Considering glib-networking:amd64 156 as a solution to libglib2.0-0:amd64 2838
  Upgrading glib-networking:amd64 due to Breaks field in libglib2.0-0:amd64
Investigating (9) glib-networking [ amd64 ] < 2.32.1-1ubuntu2 -> 2.34.0-0ubuntu1 > ( libs )
Broken glib-networking:amd64 Depends on glib-networking-services [ amd64 ] < 2.32.1-1ubuntu2 -> 2.34.0-0ubuntu1 > ( libs ) (>= 2.34.0-0ubuntu1)
  Considering glib-networking-services:amd64 18 as a solution to glib-networking:amd64 156
  Holding Back glib-networking:amd64 rather than change glib-networking-services:amd64

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Hi Mike,

have you give

update-manager -d

a run from terminal ?

tags: added: quantal
Changed in update-manager (Ubuntu):
status: New → Confirmed
affects: update-manager (Ubuntu) → ubuntu-release-upgrader (Ubuntu)
Revision history for this message
Mike Pasche (mike-d-pasche) wrote : Re: [Bug 1058052] Re: update-manager crashes on upgrade from 12.04 -> 12.10 Beta 2

Yes, I used "update-manager -d" and it crashed during the upgrade from
12.04 to 12.10. I don't know what caused the problem, but I suspect it
was because a month ago when I was using 12.04 I manually upgraded my
Linux-headers to 3.4 because I have a newer Thinkpad that kept freezing
up. So when I upgraded to 12.10 using "update-manager -d" it crashed.

Anyway, in the meantime I did a complete clean install of 12.04, and then I
ran "update-manager -d" and it upgraded to 12.10 just fine.

Thanks.

Mike

On Sat, Oct 6, 2012 at 5:31 AM, melchiaros <email address hidden> wrote:

> Hi Mike,
>
> have you give
>
> update-manager -d
>
> a run from terminal ?
>
> ** Tags added: quantal
>
> ** Changed in: update-manager (Ubuntu)
> Status: New => Confirmed
>
> ** Package changed: update-manager (Ubuntu) => ubuntu-release-upgrader
> (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1058052
>
> Title:
> update-manager crashes on upgrade from 12.04 -> 12.10 Beta 2
>
> Status in “ubuntu-release-upgrader” package in Ubuntu:
> Confirmed
>
> Bug description:
>
> e:error, pkgProblemResolver::Resolve generated breaks
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: update-manager 1:0.156.14.9
> ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
> Uname: Linux 3.2.0-30-generic x86_64
> ApportVersion: 2.0.1-0ubuntu13
> Architecture: amd64
> Date: Fri Sep 28 07:08:27 2012
> GsettingsChanges:
> com.ubuntu.update-manager first-run false
> com.ubuntu.update-manager launch-time 1348830448
> com.ubuntu.update-manager show-details true
> com.ubuntu.update-manager window-height 530
> com.ubuntu.update-manager window-width 600
> InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
> (20120823.1)
> PackageArchitecture: all
> ProcEnviron:
> LANGUAGE=en_US:en
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: update-manager
> UpgradeStatus: Upgraded to precise on 2012-09-28 (0 days ago)
> VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13]
> Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
> VarLogDistupgradeTermlog:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1058052/+subscriptions
>

Revision history for this message
Mike Pasche (mike-d-pasche) wrote :

Yes, I used "update-manager -d" and it crashed during the upgrade from 12.04 to 12.10.

(Ignore my previous comment -- I think this bug happened after my clean install of 12.04, while I was upgrading 12.04 -> 12.10 and not on the initial failed attempt.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Thank you for the answer and the hint with the kernel-headers. But AFAIK glib is as library separated from the headers.

The glib you have had on your Ubuntu 12.04 system were 2.32.x which is in genuin Precise and the upgrade try to get to 2.34.x for Quantal. So, it is to expect that this error may affect more people after official release of Quantal.

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

This seems to have been caused by a temporary inconsistent state of the repositories during the development process of Quantal.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers