http://brainstorm.ubuntu.com/item/11690/
I'd love to see an automatic repair of an interrupted dpkg, but I also know that'd take much longer to implement.

In the meantime, the message given to users should be to run

sudo dpkg --configure -a

instead of what they currently get, which is to run

dpkg --configure -a

Of course, when they run dpkg --configure -a, they also get an error message saying they aren't root so can't run the command, which is silly, since Ubuntu doesn't enable the root account by default, and the user just ends up confused.

]]> en-us Thu, 31 Jul 2008 15:01:09 +0000 Thu, 19 Feb 2009 00:26:48 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/11690/ just do a "sudo -s"

But the idea is good, to be more transparent.]]> Thu, 31 Jul 2008 15:39:37 +0000
sudo dpkg --configure -a should take care of the problem.

If someone desperately needs a persistent root login, she should use sudo -i instead of sudo -s]]> Thu, 31 Jul 2008 19:52:37 +0000
I've had to reinstall Ubuntu because of this issue. ]]> Fri, 01 Aug 2008 03:11:30 +0000 It sets the correct environment for the root user.
So no files in the user's home folder become owned by root.]]> Sun, 03 Aug 2008 11:37:59 +0000
Make it something really short or a button, click-able link or whatever for God's sake.]]> Tue, 05 Aug 2008 16:17:52 +0000 sudo dpkg --configure -a' from a terminal to correct the problem."

(And add a button or something to Synaptic and Update manager that runs `gksu dpkg --configure -a` when they fail)]]> Thu, 19 Feb 2009 00:26:48 +0000