[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
Please don't use this bug as a dumping ground for problems with cryptsetup in karmic. There are other bug reports tracking the issues you've described; this is a bug report from a user reporting that X starts before the passphrase prompt for /home is presented. ** Summary changed: - Upgrade to Karmic completely broke password prompt for cryptdisks at boot + gdm starts before passphrase is entered for /home -- gdm starts before passphrase is entered for /home https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
I need to withdraw my last comment: The problem is *NOT* fixed. Sometimes (nondeterministically) it still breaks. The problem seems to be related to the concurrent starting of the init.d scripts and some inherent race condition there. -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
I've had the same problem - it appears to have been fixed since today. The system was rendered completely unbootable, forcing me to pass a init=/bin/bash to the grub kernel line and do a apt-get dist-upgrade from there. Now it appers to work - it did so before, however, and then broke again with no appearent reason. I already posted my problem on Usenet with MID <7p6r9dfp3...@mid.dfncis.de> in alt.os.linux.ubuntu under the subject "Karmic LUKS Cryptofs trouble" on 2009-12-20 15:38. I will repost it here: 8<8<8<8<8<8<8<8<8<8<8<8<8<8<8< Hello group, I'm having the same problem with two computers running Karmic. It both has to do with the startup of LUKS devices. Sometimes (every 2nd time or so) it happens that appearently two services (cryptsetup and some other) are started at the same time, racing for terminal input. As usually one character goes to cryptsetup and the other goes to whatever, it is almost impossible to enter a password. I know this because sometimes (again, nondeterministically) I am prompted to enter my root-password to get a shell. When the shell opens I see exactly which characters are echoed (every 2nd one). This means, to get a ps ax I have to type "p?s? ?a?x?" where "?" can be any character (it goes to the other program, I guess cryptsetup in this case or maybe askpass). This is annoying as hell and I don't know why it happens. I'm guessing something about parallel init.d is screwed up there. Is there a way to disable it? Here's the output I'm getting: http://bildrian.de/n/b/87049ab6a0a55306.jpg Anyone knows what could be the problem? Regards, Johannes -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
I can confirm I'm having this problem also. I upgraded from Jaunty to Karmic on 12/18, and haven't found a solution over the weekend. My crypto setup follows the howto here: https://help.ubuntu.com/community/EncryptedFilesystemHowto3 My /etc/crypttab: cryptoswap /dev/sda6 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,hash=sha256,swap cryptotmp /dev/sda5 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,hash=sha256,tmp cryptohom /dev/sda1 none luks Relevant fstab entries: /dev/mapper/cryptohome /home ext4 relatime,errors=rmount-ro 0 2 /dev/mapper/cryptotmp /tmp ext2 defaults 0 2 /dev/mapper/cryptoswap none swap sw 0 0 Some output from booting: - fsck from util-linux-ng 2.16 fsck.ext2: Device or resource busy while trying to open /dev/mapper/cryptotmp Filesystem mounted or opened exclusively by another program? mountall: fsck /tmp [1171] terminated with status 8 mountall: General fsck error General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will temrinate this shell and re-try. Enter passphrase to unlock the disk /dev/sda1 (cryptohome): After this, no input is echoed until I press ctrl-D, which spits out terminal interactions of whatever I'd typed (like my passphrase), which were presumably happening in the background. Other times, it looks like this: init: upstart-udev-bridge main process (545) terminated with status 1 init: upstart-udev-bridge main process ended, respawning modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.31-16-generic/kernel/drivers/crypto/padlock-sha.ko): No such device init: upstart-udev-bridge main process (1054) terminated with status 1 init: upstart-udev-bridge main process ended, respawning Enter passphrase to unluck the disk /dev/sda1 (cryptohome): One or more of the mounts listed in the /etc/fstab cannot yet be mounted: (ESC for recovery shell) /home: waiting for /dev/mapper/cryptohome These two different errors error show up intermingled with the passphrase prompt. Using ctrl-alt-F1 to go to another terminal doesn't do much good here, it just has a message that it's waiting for boot. I removed crypttab and the crypto entries in fstab, and I can boot normally, though I had to chmod 777 /tmp. I can mount /dev/sda1 using cryptsetup luksOpen as normal once booted up. -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
Tom, > 1. X-Windows login prompt appears even before the passphrase for my encrypted /home can be entered Which version of the 'mountall' package did you have in place? From mountall 0.2.1 on, uploaded on Oct 9, the 'filesystem' signal should not be emitted until /home is mounted; and the kdm upstart job waits for this signal. Is this problem still reproducible for you in the final release of Ubuntu 9.10? ** Changed in: cryptsetup (Ubuntu) Status: Confirmed => Incomplete -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
My setup is exactly like the Ubuntu EncryptedFilesystemHowto: https://help.ubuntu.com/community/EncryptedFilesystemHowto I'm using LUKS, and /etc/crypttab with the following line: safehome /dev/sdb4 none luks,cipher=aes-xts-plain -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
Are you doing this via /etc/crypttab ? is LUKS used? Are you perhaps using custom script that calls cryptsetup by hand? or just crypttab -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
> Are you 100% sure the correct password is rejected? Positive. As said, once every n-th time the same password is accepted OK. I've even checked if my keyboard has bouncy keys etc. > What if you try to mount the disc manually? Manual mounting (after using cryptsetup luksOpen) works OK as expected. > What encryption are you using aes-xts-plain -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
Are you 100% sure the correct password is rejected? Because then this is a bit other bug then I seen. I use luks on this box, and since auto-executed cryptsetup-using script that i written does nothing when executed from init.d, I have to run the script (so - run cryptsetups luksOpen) manually - and then it works. What if you try to mount the disc manually? What encryption are you using -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
Same here. This is a serious problem. Seems like one of us users has to do something about this or the situation won't change. Is there any documentation other than guessing which initramfs/init /upstart-scripts are involved? -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475293] Re: Upgrade to Karmic completely broke password prompt for cryptdisks at boot
I have the same problem using Kubuntu Karmic alternate CD. I can encrypt a partition during install, but on reboot at the prompt for password for encrypted partition, entering password and enter does nothing. Pressing enter a second time results in failure. I tried enter first, then password, then enter. Nothing. Enter again, rejection of the correct password. Next attempt requires enter key eight times before rejection. Something is seriously wrong with this. -- Upgrade to Karmic completely broke password prompt for cryptdisks at boot https://bugs.launchpad.net/bugs/475293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
