Can't open cryptdisks.functions

Bug #435814 reported by arky on 2009-09-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)

Bug Description

Binary package hint: cryptsetup

Following error on booting.

.: Can't open /lib/cryptsetup/cryptdisks.functions

Perhaps these from lines /etc/init.d/cryptdisks script is the cause.

cryptdisks:if [ -r /lib/cryptsetup/cryptdisks.functions ]; then
cryptdisks: . /lib/cryptsetup/cryptdisks.functions

ProblemType: Bug
Architecture: i386
Date: Thu Sep 24 16:16:22 2009
DistroRelease: Ubuntu 9.10
Package: cryptsetup (not installed)
 PATH=(custom, user)
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SourcePackage: cryptsetup
Uname: Linux 2.6.31-10-generic i686

arky (arky) wrote :
Steve Langasek (vorlon) wrote :

Thank you for taking the time to report this bug and help to improve Ubuntu.

Do you have the cryptsetup package currently installed? Perhaps the package was previously installed but you removed it, leaving behind the upstart job in /etc/init but removing the files in /lib/cryptsetup?

Changed in cryptsetup (Ubuntu):
importance: Undecided → Medium
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cryptsetup - 2:1.1.0~rc2-1ubuntu4

cryptsetup (2:1.1.0~rc2-1ubuntu4) lucid; urgency=low

  [ Steve Langasek ]
  * debian/initramfs/cryptroot-script: if plymouth is present in the
    initramfs, use this directly, bypassing the cryptsetup askpass script;
    but keep support for these other frontends around on a transitional
  * debian/cryptdisks.functions:
    - change interaction to use plymouth directly if present, and if not, to
      fall back to /lib/cryptsetup/askpass as before
    - wrap the call to /lib/cryptsetup/askpass with watershed, to make sure
      we only ever have one of these running at a time; otherwise multiple
      invocations could steal each other's input and/or write over each
      other's output
    - new function, crypttab_start_one_disk, to look for the named source
      device in /etc/crypttab (by device name, UUID, or label) and start it
      if configured to do so
  * debian/cryptdisks-enable.upstart: run the upstart job once for each block
    device, using the new crypttab_start_one_disk function, triggered by udev;
    this doesn't eliminate the possibility of a race with gdm when the
    decrypted volume isn't a 'bootwait' mount point (since gdm kills
    plymouth), but it does eliminate the race between udev and cryptsetup.
    LP: #454898.
  * debian/cryptdisks-enable.upstart: check that the package is installed
    and exit gracefully if it's not. LP: #435814
  * debian/cryptdisk.functions: initially create the device under a temporary
    name and rename it only at the end using 'dmsetup rename', to ensure that
    upstart/mountall doesn't see our device before it's ready to go.
    LP: #475936.

  [ Colin Watson ]
  * Add ext4 support to passdev.
 -- Steve Langasek <email address hidden> Tue, 15 Dec 2009 18:05:45 -0800

Changed in cryptsetup (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments