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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963533 Title: opencryptoki version churn has broken some systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/963533/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
