[Bug 1385089] Re: keyboard sometimes doesn't respond at login
diehard67
1385089 at bugs.launchpad.net
Sat Oct 25 01:01:17 UTC 2014
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
--
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
More information about the foundations-bugs
mailing list