Cryptsetup uses watershed, but dependecy missing

Bug #568564 reported by Sebastian
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: cryptsetup

In /lib/cryptsetup/cryptsetup.functions script "watershed" is called. Script will fail if watershed is not installed. Dependency on watershed is missing.

cryptsetup: Version: 2:1.1.0~rc2-1ubuntu13
Description: Ubuntu lucid (development branch)

Tags: lucid
Revision history for this message
Steve Langasek (vorlon) wrote :

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

watershed is only called if plymouth is not installed or not running. Since cryptsetup now depends on plymouth, this should not happen. So we don't need to depend on both plymouth and watershed.

Changed in cryptsetup (Ubuntu):
status: New → Won't Fix
Revision history for this message
Sebastian (zimmermann) wrote :

Hhhm, shouldn't then the use of watershed completely be removed from the package? I can only report that in my setup the script fails because cryptsetup calls watershed when the plymouth daemon is not running. Removing watershed from the KEYSCRIPT and instead calling askpass directly solves the problem.

Revision history for this message
Steve Langasek (vorlon) wrote :

Well, no, what we *really* want to do is drop the non-plymouth fallback path entirely, but leaving the code in for now means a potentially smaller delta from Debian.

The real question is, why is this being called on your system when the plymouth daemon isn't running?

Revision history for this message
Luigi Bai (lpb+launchpad) wrote :

I don't use plymouth and have no plans to use it. Please make sure the non-plymouth fallback works for cryptdisk_start.

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.