Comment 17 for bug 442941

I've finally found a reliable method that I can use to reproduce this bug in isolation (so I might at long last be able to do something about it!):

 1) Install a Natty desktop system (and checkpoint the virtual machine at this point)
 2) Start update-manager
 3) Uncheck everything except libpam0g and tzdata
 4) Run the upgrade

I'm going over a system call trace with a fine-toothed comb now. I'm pretty sure it's not the fault of any of the packages being installed. It looks as though there may be something wrong with aptdaemon's debconf proxy (the other end of the socket doesn't seem to be connected to anything), but it could also be a bug in how update-manager is talking to aptdaemon.