apport enabled after a distribution upgrade from Karmic to Lucid

[Brian Murray]

Binary package hint: update-manager

Similar to bug 465619 after performing a distribution upgrade from Karmic to Lucid on 20100423 I've discovered that apport is still enabled. Searching '/var/log/dist-upgrade/main.log' and other files I can do not find any mention of apport explicitly being disabled but '/etc/default/apport' still has 'enabled=1'. This is despite apport package version 1.13.3-0ubuntu2 which sets 'enabled=0'. Apport should really be disabled.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: update-manager 1:0.134.6
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sun Apr 25 15:32:03 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager

[Brian Murray (brian-murray)]

Looking at '/usr/share/update-manager/DistUpgrade.cfg' - 'EnableApport=no'.

[Michael Vogt (mvo)]

I tried to reproduce this with the auto-upgrade-tester package. A clean karmic -> lucid upgrade has "enabled=0" before the upgrade and "enabled=0" after the upgrade for /etc/default/apport.

Or do I misread the report and you suggest that if it was "enabled=1" in karmic (which is not the default and means that the user changed it) during the upgrade it should become enabled=0 ?

[Brian Murray (brian-murray)]

It looks like I may have set "enabled=1" in karmic before upgrading as I was unable to recreate this using a karmic install with "enabled=0". I'm going to run that test again to confirm.

[Steve Langasek (vorlon)]

As we don't currently have a handle on this, if there *is* a bug here we almost certainly won't have it fixed in time for 10.04; pointing at lucid-updates.

[Brian Murray (brian-murray)]

Performing another upgrade I've discovered that if "enabled=1" is set in Karmic for apport and a distribution upgrade to Lucid is completed apport is still set to "enabled=1". This makes sense to me.

[Michael Vogt (mvo)]

Thanks, if you don't mind I close the bug then. Please reopen if there is any action in update-manager required.