Ubuntu
usplash package

Usplash no longer changes vts correctly.

Bug #56319 reported by Thom May on 2006-08-14

This bug report is a duplicate of: Bug #62751: Upstart doesn't activate luks volumes (also non luks) in cryptsetup. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	usplash (Ubuntu)	New	Undecided	Unassigned

Bug Description

I have a dm-crypt /home. In dapper, the cryptdisks startup was correctly able to move off usplash onto a vt to prompt for the passphrase. In edgy, this no longer occurrs - the screen remains on usplash, and trying to change vts manually results in my monitor giving out of range errors and turning off, thus killing the boot process entirely.

Revision history for this message

Matthew Garrett (mjg59) wrote on 2006-09-27:

Is this still the case?

Revision history for this message

jott (ottjochen) wrote on 2006-10-09:

I have the same problem: I have a cryptdisk with dm-crypt/LUKS (just /home and swap, not root).
Before upgrading to edgy, all worked correctly. Now, something is wrong with reading the passphrase, but the problem does not seem to be usplash:
I removed the usplash-package, but the problem remains.

While booting, the following messages appear:

No cryptroot configured, skipping.

[some fsck output]

* Starting early crypto disks...
Enter LUKS passphrase: Command failed: Error reading passphrase
[ ok ]
* Starting remaining crypto disks
Enter LUKS passphrase: Command failed: Error reading passphrase
[ ok ]