[pkg-cryptsetup-devel] Bug#694499: breaks when used together with cryptsetup

Jelmer Vernooij jelmer at debian.org
Tue Nov 27 13:12:37 UTC 2012

On Mon, Nov 26, 2012 at 11:51:16PM -0800, Steve Langasek wrote:
> On Tue, Nov 27, 2012 at 01:04:05AM +0100, Jelmer Vernooij wrote:
> > (not sure whether this is a bug in the upstart files in cryptsetup or
> > upstart)
> > When using upstart together with cryptsetup, upstart hangs waiting for
> > startpar right after boot. I also get an error on the console
> > from initctl complaining that DEVNAME is not a valid level.
> This is a bug in cryptsetup.  The cryptsetup package ships upstart jobs
> under names that match the names of the pre-existing init scripts.  The
> problem is that the upstart jobs and init scripts *are not equivalent*.  The
> upstart job /etc/init/cryptdisks-early.conf creates one job instance per
> crypto device.  This means that it does *not* generate the event necessary
> to tell startpar that dependencies on /etc/init.d/cryptdisks-early are
> satisfied, and so startpar, which knows about the upstart job, hangs
> indefinitely waiting for a non-instance cryptdisks-early event which will
> never occur.
> I've attached a patch which corrects this, as well as correcting a shutdown
> hang with cryptsetup.  Jonas, could you please apply this to cryptsetup in
> unstable?
That was a prompt fix! Thanks.

FWIW, I can confirm this fixes the issue for me.



More information about the pkg-cryptsetup-devel mailing list