DebuggingUpdateManager

Differences between revisions 1 and 10 (spanning 9 versions)
Revision 1 as of 2007-11-12 16:31:48
Size: 2413
Editor: c-71-59-213-167
Comment: First Draft
Revision 10 as of 2008-01-23 13:28:34
Size: 3749
Editor: yttrium
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Update-manager provides two services - the ability to upgrade packages within a release, and the ability to upgrade releases of Ubuntu. When looking at bug reports it is important to keep this in mind and identify wheter it is a problem with a package upgrade or a release upgrade. Update-manager provides two services - the ability to upgrade packages within a release, and the ability to upgrade a release of Ubuntu to the next one. When looking at bug reports it is important to keep this in mind and identify whether it is a problem with a package upgrade or a release upgrade.
Line 9: Line 9:
When filing a bug report regarding a problem with a distribution or release upgrade you should add every file in '/var/log/dist-upgrade/', there should be at least 3, as separate attachments. You should also tag your distribution upgrade bug with the release you are moving from and to - for example 'feisty2gutsy'. When filing a bug report regarding a problem with a distribution or release upgrade at a minimimum you should add every file in '/var/log/dist-upgrade/', there should be at least 3, as separate attachments. You should also tag your distribution upgrade bug with the release you are moving from and to - for example 'feisty2gutsy'.
Line 11: Line 11:
= Debugging procedure = = Bug Tags =

|| Tag || Use case || Link ||
|| `gutsy2hardy` || Bugs related to upgrading from Gutsy Gibbon to Hardy Heron || [https://launchpad.net/ubuntu/+bugs?field.tag=gutsy2hardy link] ||
|| `feisty2gutsy` || Bugs related to upgrading from Feisty Fawn to Gutsy Gibbon || [https://launchpad.net/ubuntu/+bugs?field.tag=feisty2gutsy link] ||
|| `edgy2feisty`|| Bugs related to upgrading from Edgy Eft to Feisty Fawn || [https://launchpad.net/ubuntu/+bugs?field.tag=edgy2feisty link] ||
|| `dapper2edgy`|| Bugs related to upgrades from Dapper Drake to Edgy Eft || [https://launchpad.net/ubuntu/+bugs?field.tag=dapper2edgy link] ||
|| `cdrom-upgrade`|| Bugs related to an upgrade from CD-ROM or DVD media || [https://launchpad.net/ubuntu/+bugs?field.tag=cdrom-upgrade link] ||

The previously described tags are specific to the [:UpdateManager] application, if you need more general tags please visit [:Bugs/Tags] page.

= Debugging Procedures =
Line 20: Line 31:
  * may contain python backtraces   * may contain python back traces
Line 36: Line 47:
|| https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/107188 || Out of memory error on KDE || duplicate, no solution yet ||
Line 42: Line 54:
 * The distribution upgrade will halt if the system has custom, non-Ubuntu, kernel installed.
 * The distribution upgrade will warn the user if there is not enough free space in '/boot' on their system.
 * When running a development release of Ubuntu you will frequently receive messages when trying to run update-manager that it could not calculate the upgrade. This is expected and happens due to the amount of changes occuring in the repository.

 * The distribution upgrade will warn the user if there is not enough free space on any parition (e.g. '/boot') on their system. The space must be freed and the upgrade restarted.

Introduction

Update-manager provides two services - the ability to upgrade packages within a release, and the ability to upgrade a release of Ubuntu to the next one. When looking at bug reports it is important to keep this in mind and identify whether it is a problem with a package upgrade or a release upgrade.

How to file

When filing a bug report regarding a problem with a distribution or release upgrade at a minimimum you should add every file in '/var/log/dist-upgrade/', there should be at least 3, as separate attachments. You should also tag your distribution upgrade bug with the release you are moving from and to - for example 'feisty2gutsy'.

Bug Tags

Tag

Use case

Link

gutsy2hardy

Bugs related to upgrading from Gutsy Gibbon to Hardy Heron

[https://launchpad.net/ubuntu/+bugs?field.tag=gutsy2hardy link]

feisty2gutsy

Bugs related to upgrading from Feisty Fawn to Gutsy Gibbon

[https://launchpad.net/ubuntu/+bugs?field.tag=feisty2gutsy link]

edgy2feisty

Bugs related to upgrading from Edgy Eft to Feisty Fawn

[https://launchpad.net/ubuntu/+bugs?field.tag=edgy2feisty link]

dapper2edgy

Bugs related to upgrades from Dapper Drake to Edgy Eft

[https://launchpad.net/ubuntu/+bugs?field.tag=dapper2edgy link]

cdrom-upgrade

Bugs related to an upgrade from CD-ROM or DVD media

[https://launchpad.net/ubuntu/+bugs?field.tag=cdrom-upgrade link]

The previously described tags are specific to the [:UpdateManager] application, if you need more general tags please visit [:Bugs/Tags] page.

Debugging Procedures

For a distribution upgrade in '/var/log/dist-upgrade/' there are three log files that are helpful in debugging the issue:

  1. 'main.log'
    • contains the version of release upgrade and the lsb-release (version of Ubuntu)
    • contains information on how '/etc/apt/sources.list' was handled and updated
    • contains log information regarding the free space calculation
    • contains an overview of the whole process
    • may contain python back traces
  2. 'apt.log'
    • contains a dump of the package problem resolver
    • it is useful when update-manager says it can not upgrade
    • it is also useful for identifying 3rd party repositories that are problematic
    • it usually reveals information about incorrect dependencies
  3. 'term.log'
    • is a subset of '/var/log/apt/term.log'
    • errors can be found by looking for the string 'dpkg: error'

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/107188

Out of memory error on KDE

duplicate, no solution yet

Closed

Bug#

Description

Action

Non-bugs

  • When running a development release of Ubuntu you will frequently receive messages when trying to run update-manager that it could not calculate the upgrade. This is expected and happens due to the amount of changes occuring in the repository.
  • The distribution upgrade will warn the user if there is not enough free space on any parition (e.g. '/boot') on their system. The space must be freed and the upgrade restarted.

Also see


CategoryBugSquad

DebuggingUpdateManager (last edited 2014-12-07 22:23:09 by penalvch)