package cryptsetup 2:1.4.1-2ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Bug #954810 reported by Anadon
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

updated trial ubuntu

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: cryptsetup 2:1.4.1-2ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.309
Date: Wed Mar 14 04:50:55 2012
ErrorMessage: subprocess new pre-removal script returned error exit status 1
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120313)
SourcePackage: cryptsetup
Title: package cryptsetup 2:1.4.1-2ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: # <target name> <source device> <key file> <options>
fstab:
 overlayfs / overlayfs rw 0 0
 tmpfs /tmp tmpfs nosuid,nodev 0 0
 /dev/sda1 swap swap defaults 0 0

Revision history for this message
Anadon (joshua-r-marshall-1991) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Jean-Louis Dupond (dupondje) wrote :

Autoupdate was prolly running in the background, making dpkg to get locked.

Can you retry? This should work just fine.

Changed in cryptsetup (Ubuntu):
status: New → Invalid
Revision history for this message
MrBl33t (mrbl33t) wrote :

Just happened to me, i was following a guide to remove KDE.

Revision history for this message
Noel Miller (noeldamonmiller) wrote :

I installed opscode chef server, etc. et all
Changed my mind when it looked like there were more dependencies than I expect.
When chef server was purged the question of whether or not to keep cryptsetup was a question and I said "no"
shortly after that I thought that perhaps full disk encryption would break so installed it again
(all of this after an upgrade from the 3.5.0-23 kernel to 3.5.0-25

in short, after a reboot for the upgrade ... FDE choked and didn't ask for the passphrase.
I tried the 3.5.0-24 kernel and that didn't either
then, I booted 3.5.0-23 and it worked again.

not entirely sure what happened.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.