On Fri, 2010-03-19 at 00:50 +0000, Luke wrote: > A quick test boot (I'm in a park on batteries) showed no sign of the > keypress bug with the new plymouth, smoothly took every character. I > will let you know if the problem resurfaces, but the odds that this > boot would have been this clean with the last version would have been > less than 1 in 10. > This would make sense to me.
Since you're using encrypted filesystems, you must have cryptsetup installed, so Plymouth is starting from the initramfs. Plymouth will set its TTY up to be in "raw mode", and make it the active VT on the console. Upstart starts later, to bring up the full system; and some code existed in there (the last thing done only because sysvinit did) to reset the console with "sane" settings. This put the console back into "cooked mode", ie. Plymouth's active VT. Since Plymouth is now receiving cooked key codes not raw key codes, it's not what it expects; and thus we have the bug where keypresses are missed or mis-interpreted. Later on, this same problem would cause X to crash on the Enter key. So it should be fixed as a result of that fix, we not only fixed bits in Plymouth but dropped that code from Upstart too. I'll mark it fixed now, but please do reopen if you have the issue again, and we'll walk through the code and see what else is going screwy. status fixreleased Scott -- Scott James Remnant [email protected] ** Changed in: plymouth (Ubuntu) Status: Incomplete => Fix Released -- missed passphrase keypress bug is back on MSI Wind U100 https://bugs.launchpad.net/bugs/537793 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
