Comment 2 for bug 237602

I've seen something similar, where the upgrade process raised a text prompt (modified file vs. new packaged file). I didn't have the text output shown at the time, so it just failed to install properly. In my case, running "sudo aptitude safe-upgrade" pushed the changes through.

I suggest that this is a wishlist item--adept should have better handling of unexpected events during installation, so that it doesn't leave a mess that can only be sorted out from a command line. Two specific points:
- If a prompt is raised during installation or upgrade, open the text output section to give the user a chance to deal with it, rather than just failing.
- If adept is started when dpkg has been blocked, offer a button to click that will run "dpkg --configure -a"