Comment 3 for bug 963533

I remember seeing a chroot in that state but I assumed I created that mess by manually running "dpkg -i" on some locally built .deb.

I'd guess running "sudo dpkg --purge opencryptoki libopencryptoki0 && sudo apt-get install opencryptoki" should fix your problem in a relatively sane way.

I'd still be interested to hear about upgrade conditions from lucid => precise or oneiric => precise that would trigger that state, if that's reproducible, then we definitely need to fix the dependencies to avoid this.