Public bug reported:
Binary package hint: xorg
On my Lenovo T500 running Lucid, if I do the following:
1. start up 'xev'
2. Lock screen
3. unlock screen
Then 100% of the time, pressing any keys on the keyboard does not seem to have
any effect. No info is printed in 'xev'. 'Crtl-alt-tab' does not work either.
crtl-alt-F1 does work, but crtl-alt-f7 does not fix the problem.
The only thing that seems to fix it is to click on another window. That
somehow seems to unfreeze x keyboard events.
This problem happen in any application: xev, xterm, google chrome, etc.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
Date: Sat Jul 17 12:41:22 2010
DkmsStatus: Error: [Errno 2] No such file or directory
MachineType: LENOVO 2242CTO
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=UUID=65dfa6ff-b1dd-4f30-a094-f6e44c46b4cc ro quiet splash
xforcevesa crashkernel=384M-2G:64M,2G-:128M
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 10/02/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET79WW (3.09 )
dmi.board.name: 2242CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr6FET79WW(3.09):bd10/02/2009:svnLENOVO:pn2242CTO:pvrThinkPadT500:rvnLENOVO:rn2242CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2242CTO
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-23-generic
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug freeze i386 lucid
--
No X keyboard events upon unlocking screen
https://bugs.launchpad.net/bugs/606741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
