I think it could be caused by HAL, even though I didn't tested it. At the end of the decryption chain the password is piped through stdin to "/usr/lib/hal/scripts/linux/hal-luks-setup-linux" which then calls cryptsetup. The script reads the password by executing "read PASSWORD".
Apparently bash strips any leading or trailing spaces in this case, which would explain the observed behaviour. See also > http://www.mydatabasesupport.com/forums/shell/372688-bash-read-string-preceding-trailing-space-oddity.html A short test script verified this. Replacing the line by "IFS= read PASSWORD" should fix the problem. But as already said, I didn't tested it in conjunction with KDE/HAL/cryptsetup... -- encrypted volumes aren't decrypted if the password is a space https://bugs.launchpad.net/bugs/208801 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
