Comment 3 for bug 1385089

the only changes were to work around this, adding sleep 2 before exec lightdm in /etc/init/lightdm.conf

I know lightdm.conf calls plymouth quit before running lightdm itself but I suspect it is not done quitting when lightdm starts running.

like I said if I tell the kernel to give a text login and start lightdm later in the boot process in rc.local the keyboard works almost every time.

truth be told I have no idea what to look at or how to get more info, if there some way to get plymouth, lightdm, x and the kernel to give me detailed logs during boot?????

I should also mention my sisters netbook is not a particularly fast system
asus eeepc x101ch

1 gb of ram
intel atom n2600 at 1.6 ghz
dual core with hyperthreading

snipit of /etc/default/grub
GRUB_DEFAULT=4
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash text"
GRUB_CMDLINE_LINUX="i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.semaphores=1"

rc.local
#!/bin/sh
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

hdparm -W0 /dev/sd?

/etc/acpi/lid.sh

killall plymouthd

service lightdm restart

exit 0

the upgrade to 14.10 put lightdm.conf back the way it was