[Bug 1385089] Re: keyboard sometimes doesn't respond at login

[diehard67]

I got logs from good and bad boots under different configurations.

I have a bad boot with all my hacks in place
a bad one with all my hacks disabled and debug logging for plymouth
the same after putting the computer to sleep and waking it up again.
and a good boot strangely this was under default debug configuration

and the i915 stuff is to tune the gpu for better performance and power
efficiency, I don't think it had any effect as I still had the problem
after removing them.

unfortunate I don't think those logs are gonna be much help, is there a
way to get lightdm and x to be more detailed in there logs or to get log
entries somewhere when process start and stop, that is when executives
are run and when they die in order.

is there a way to get information on the input devices from a command
line, I can ssh in after booting so if I could see the state of the
keyboard from the system it might shed some light or maybe a way to work
around it.

I know if I plug in an external keyboard it works but the internal one
doesn't till the computer is put to sleep and woke back up again, I
loged in with a usb keyboard once, thought the internal one might start
working once the computer was loged in but nope, didn't work.

** Attachment added: "file full of logs from my sisters computer"
   https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1385089/+attachment/4245932/+files/logs.tar.bz2

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1385089

Title:
  keyboard sometimes doesn't respond at login

Status in “plymouth” package in Ubuntu:
  Incomplete

Bug description:
  I have tried diferant display managers (kdm nd lightdm) both are
  effected sometims whn my sister turns on her netbook she can't type in
  her password untill she puts th cmpute to sleep and wakes it up again,
  this seems to be randome, from what I have been able to fine from
  googling all over the place plymouth is to blame for this, seems to be
  if it is still running when whateverdm starts you will not bable to
  type.

  on my own laptop I have had the same problem and was able to fix it by
  adding a sleep 2 before exec lightdm in /etc/init/lightdm.conf

  my sisters netbook needed  more then that, he delay got to 6 seconds
  long and still wasn't reliable, I had to modify /etc/default/grub to
  ass text after splash then put service lightdm restart in rc.local so
  she could login most of the time.

  she has had the problem in 14.04 and now in 14.10, I have had it sense
  13.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 24 01:43:10 2014
  InstallationDate: Installed on 2014-04-30 (176 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1385089/+subscriptions