If you read my post #53, it should solve your problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767498
Title:
package apport 1.20.1-0ubuntu3 failed to install/upgrade: subprocess
installed
If you use sudo start apport force_start=1 after it tells you that it
failed to start and then reinstall it, it shouldn't error out. The new
packages are available, but you have to download them manually using a
web browser.
--
You received this bug notification because you are a member of
That bug also shows up on version (1.20.1-0ubuntu3).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767498
Title:
package apport 1.20.1-0ubuntu3 failed to install/upgrade: subprocess
installed
That bug, I think, is part of this one as it shows up after apport fails
to start without forcing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767498
Title:
package apport 1.20.1-0ubuntu3 failed
If you open /etc/default/apport with gedit, you will see enabled=0.
Change this to enabled=1 and try installing apport again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767498
Title:
package
This bug can occur if you close out the Ubuntu Software Center window
before it has a chance to get the appname or pkgname.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/743386
Title:
Public bug reported:
Binary package hint: aptdaemon
This happened after aptdaemon failed to get a lock on the cache.
Most likely a result after a similar process doesn't release the lock.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.41+bzr614-0ubuntu2
** Description changed:
Binary package hint: aptdaemon
- This happened after aptdaemon failed to get a lock on a certain item.
- Not sure what it was.
+ This happened after aptdaemon failed to get a lock on the cache.
+ Most likely a result after a similar process doesn't release the lock.
