package policykit-1 0.96-2 failed to install/upgrade:

[Dave Madsen]

Binary package hint: policykit-1

Much failure during this Karmic -> Lucid upgrade, this is only a taste. I kept getting the message that apport was quitting because there were too many bug reports.

The disk the system is on is sdb, not "a"; don't know if that's an issue or not. Rebooted in recover and said to recover packages, and it continued. I don't know (haven't checked yet) if policykit was later installed.

FYI, this is the third system that I've upgraded to Lucid. All have failed with varying problems. Two of the machines have booting problems with the kernel. Lucid seems to suck. Plus it has the damn window controls on the left. If we're gonna be a Mac, then we'd better be a helluva more reliable, no? Yes, I know you don't have enough information to debug all the problems I've seen. But that doesn't mean I haven't seen them, eh? ---dcm

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: policykit-1 0.96-2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sun Jun 13 20:18:12 2010
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: policykit-1
Title: package policykit-1 0.96-2 failed to install/upgrade:

[James Westby (james-w)]

Hi,

It appears that /proc somehow got unmounted during your upgrade. There is no
clue as to why that would happen in the logs, and it would be very unusual.

It's very unlikely to be the fault of this package. If you have any clue as to what would
have caused that then we can reassign, but I don't know how to diagnose the fault at
this point.

Thanks,

James

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 554718, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.