Hi Jonas, I just tried to reproduce this issue, but couldn't.
I added an initscript, containing just the splashy_update getpass call you described. This results in a proper prompt, in which I can enter a password, after which booting continues as normal. This can mean a few things: 1) You have very particular setup that triggers this bug. Since you tried on two different systems IIRC, this might not be so likely. 2) Having a crypt setup triggers this bug. Perhaps some kernel option? Or the cryptsetup init script (or did you disable that while testing the splashy_update-only init script?) 3) The order in the boot sequence triggers this bug. I tried using a new initscript and added it using "update-rc.d testplashy defaults", which places it rather late in the boot sequence. Did you do this as well? In any case, it would be useful if you could do some more debugging to find out what exactly triggers this bug, since I don't really know where to begin to reproduce this. If you get any closer, I would be glad to test any hypothesis you have on the cause of it (just ask me on IRC). Gr. Matthijs
signature.asc
Description: Digital signature
