Trusty sometimes boots with inactive keyboard .....

Bug #1264543 reported by Barry Drake
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Expired
Medium
Unassigned
xorg-server (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Every third or fourth boot, the keyboard is not found although it is accessible by grub2 and by pressing <CTRL>+<ALT>+F2 and withing the terminal. Logout and login from the terminal followed by <CTRL>+<ALT>+F7 to reaccess X does not bring back the keyboard. My current workaround is to use suspend and then reactivate. This always finds the keyboard after which all is normal. The problem began after an update to something (I'm not sure what as the problem is spasmodic). It was first noticed some two or three weeks ago.

WORKAROUND: Works in Lubuntu 14.04.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-input-all 1:7.7+1ubuntu7
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.12.7-0ubuntu3
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
CurrentDmesg:
 [ 26.884218] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
 [ 550.563790] audit_printk_skb: 138 callbacks suppressed
 [ 550.563794] type=1400 audit(1388145574.597:67): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2772 comm="apparmor_parser"
 [ 550.563802] type=1400 audit(1388145574.597:68): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser"
 [ 550.564387] type=1400 audit(1388145574.597:69): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser"
Date: Fri Dec 27 16:23:05 2013
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Device [1849:9901]
InstallationDate: Installed on 2013-10-21 (67 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=b0a5ccea-5d55-4be4-838d-195afa498cc5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/03/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: FM2A55M-VG3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd05/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.libdrm2: libdrm2 2.4.50-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1
xserver.bootTime: Fri Dec 27 11:50:49 2013
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Logitech Optical USB Mouse MOUSE, id 8
 input AT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.5-1ubuntu2
xserver.video_driver: radeon

Revision history for this message
Barry Drake (b-drake) wrote :
Revision history for this message
Barry Drake (b-drake) wrote :

I get no problem when booting into Saucy which I have as a dual-boot installation.

penalvch (penalvch)
tags: added: bios-outdated-1.60
tags: added: regression-release
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Barry Drake (b-drake) wrote :

Thanks for that. I have reflashed the bios to version 1.6 release date 07/11/2013 and will wait to see if the problem is fixed. As the problem is spasmodic, I will wait a week or so before saying that it is no longer there.

Revision history for this message
Barry Drake (b-drake) wrote :

Sorry I didn't read the instruction to update the bios before reporting a hardware bug of this kind. I can confirm that nothing has changed. The information requested is:
barry@trusty:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for barry:
P1.60
07/11/2013

I've attached the current dmsg Please ask if you require anything else.

Revision history for this message
penalvch (penalvch) wrote :

Barry Drake, thank you for updating your BIOS. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-1.60
removed: bios-outdated-1.60
Changed in xorg (Ubuntu):
importance: Low → Medium
affects: xorg (Ubuntu) → linux (Ubuntu)
tags: added: needs-bisect needs-upstream-testing
Revision history for this message
Barry Drake (b-drake) wrote :

Have installed kernel 3.13.0-031300rc7-generic_3.13.0-031300rc7.201401041835_i386 and will boot from this until the problem shows (or is fixed). Will report back soon.

Revision history for this message
Barry Drake (b-drake) wrote :

I can confirm that the bug is still present under:
Linux trusty 3.13.0-031300rc7-generic #201401041835 SMP Sat Jan 4 23:46:54 UTC 2014 i686 athlon i686 GNU/Linux

Before I mark this bug as suggested, could I mention that if I open a terminal by using <CTRL>+<ALT>+F2 at the login screen when the keyboard is not working, I can type into the terminal using the keyboard with no problem. Does this suggest that it may be a bug in the gnome input keyboard package rather than in the kernel?

Revision history for this message
penalvch (penalvch) wrote :

Barry Drake, thank you for testing the requested kernel. Just to clarify, if you switch desktop environments (for example to Xubuntu via http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/60659/downloads ) is this issue still reproducible?

Revision history for this message
Barry Drake (b-drake) wrote :

I have downloaded the daily build iso of Xubuntu i386 and will install it to a spare hard-drive tomorrow to continue testing. Will report back as soon as I get a result.

Revision history for this message
Barry Drake (b-drake) wrote :

I finished up installing Lubuntu 14.04 testing on a spare hard drive.
uname -a
Linux lubuntu 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 athlon i686 GNU/Linux

So far, I have booted into it a fair number of times with no keyboard problems. It is only one day, but I am fairly sure the problem does not exist in that build.

Revision history for this message
penalvch (penalvch) wrote :

Barry Drake, thank you for performing the requested test. Given this is correlated to the desktop environment one uses, this would appear not to be a kernel issue, but something to do with userspace. I'll send to xorg (Ubuntu) for them to have a look.

description: updated
Changed in linux (Ubuntu):
importance: Medium → Low
affects: linux (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
Barry Drake (b-drake) wrote :

I had a problem earlier today and wiped the drive with Trusty installed. I have re-installed and fully updated but no longer see this fault. Pleas hold until I can see any further problems.

Revision history for this message
Barry Drake (b-drake) wrote :

Problem came back after a large update that included a number of xorg packages ... So the bug is still there as far as I can see at the current build. I'm happy to carry out further tests.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Changed in unity (Ubuntu):
importance: Undecided → Medium
Changed in xorg-server (Ubuntu):
importance: Low → Medium
summary: - Trusty boots spasmodically with inactive keyboard .....
+ Trusty sometimes boots with inactive keyboard .....
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

tseliot seems to be affected too, restarting lightdm fixes it. The xorg.log doesn't show any changes between the broken and working run, which is why I suspect it's a greeter bug, not a xorg-server bug.

affects: unity (Ubuntu) → lightdm (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

Robert, have you seen this?

Changed in lightdm (Ubuntu):
assignee: nobody → Robert Ancell (robert-ancell)
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Hit this today for the first time.
Reboot resulted in the same condition, had to do a shutdown and cold boot.
The power button also did not work (to show the boot options)

Revision history for this message
Barry Drake (b-drake) wrote :

Next time, try going into suspend if you can. This always works for me. Failing that, try <ctrl>+<alt>+F2 to bring up a terminal. Log in (your user name and password) and do 'sudo shutdown -h to shut down properly.

Revision history for this message
Barry Drake (b-drake) wrote :

Another workaround seems to be:
Open a terminal from the login screen using <ctrl>+<alt>+F2 followed by username and password. Then do:
sudo stop lightdm
sudo lightdm

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Is this a duplicate of bug 1255558?

Revision history for this message
Alberto Milone (albertomilone) wrote :

It looks like a duplicate

Revision history for this message
LCID Fire (lcid-fire) wrote :

A workaround for now is to set gdm as the default login shell.

Revision history for this message
Barry Drake (b-drake) wrote :

I've put that in and am trying it. Thanks. For the record, gdm is not istalled in Trusty, so you need to do sudo apt-get install gdm
In my case, I was given the option to make gdm the default during installation. If not, you need to edit /etc/X11/default-display-manager after installing gdm

Changed in lightdm (Ubuntu):
assignee: Robert Ancell (robert-ancell) → nobody
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Changed in lightdm (Ubuntu):
status: Confirmed → Incomplete
Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.]

Changed in lightdm (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.