Comment 3 for bug 465619

The fix proposed here is acknowledged to be a workaround for a bug in the code; getWithDefault() doesn't interpret "EnableApport=no" as false, but as the text string 'no', and there are a number of points in the code where it's assumed that the opposite of 'yes' is False. However, none of these are as high-impact as the apport handling, since none of the others are set to 'no' by default in the config file.

There is also an additional cleanup step needed once the fixed update-manager is available, to go back and correct the /etc/default/apport file of any users that have had it mangled on upgrade. Brian points out that we should be able to reliably detect this case by finding the "release-upgrader version '0.126.6'" and "DEBUG enabling apport" lines in /var/log/dist-upgrade/main.log, so this can be cleaned up out-of-band after update-manager has been fixed, and we can take our time to make sure we get this right and avoid accidentally disabling apport for any users who have explicitly enabled it.