Control characters and caps lock and other control characters don't work in X in Hardy Development

[Matthew Franz]

For the last 2-3 weeks in Hardy I have been having seeming random keyboard mapping issues where SHIFT and CTRL no longer seem to work after a few hours/minutes. CAPS LOCK indicator no longer lights up when pressed. Occurs in xterms, gnome-terminal and all X apps. This occurs whether using KDM/GDM (KDE/GNOME) and various window managers: openbox, fluxbox, xfce, etc. Another issue I have seen is that a small number (less than 5%) of sessions through GDM hang after login usually with GNOME. No issues with OpenBox.

Exiting out and logging in again from GDM/KDM always solves the problem until it happens again.

Hardware: Lenovo T-61
Kernel: 2.6.24-16-generic

Nothing observed in /var/log/messages or dmesg

[Matthew Franz (mdfranz)]

Ran into this problem today for the first time in several weeks in the final release. Once agian, shift, control, etc. don't work also seeing an impact on GTK apps

[ 9452.519373] gksu[21455]: segfault at 00000028 eip b7b55275 esp bf9abcd0 error 4
[ 9461.928032] gksu[21491]: segfault at 00000028 eip b7bc4275 esp bffaa2c0 error 4
[ 9469.761872] gksu[21521]: segfault at 00000028 eip b7b9a275 esp bffd4af0 error 4
[ 9555.933606] grun[21738]: segfault at 00000040 eip b7b90275 esp bfdcbf70 error 4
[ 9556.276512] grun[21739]: segfault at 00000040 eip b7b56275 esp bfe0fd80 error 4
[ 9631.686037] grun[22129]: segfault at 00000040 eip b7bcb275 esp bf8e3050 error 4
[ 9631.939252] grun[22134]: segfault at 00000040 eip b7bf7275 esp bfd9fd10 error 4
[ 9632.134791] grun[22135]: segfault at 00000040 eip b7bf1275 esp bfbd6340 error 4
[ 9632.414273] grun[22136]: segfault at 00000028 eip b7bb0275 esp bfb33aa0 error 4
[ 9640.183804] gedit[22193]: segfault at 0000002a eip b76e7275 esp bff77d10 error 4

[Bryce Harrington (bryce)]

Sounds similar to bug 195982. Do you have vmware installed by chance?

Please attach your /var/log/Xorg.0.log following the failure.

[Matthew Franz (mdfranz)]

You are right, the symptoms look samliiar. I don't think I had VMWare
installed when the symptoms occured. Right now I only have
vmware-server-console installed. I have only had one occurrence since
I reinstalled about 2-3 weeks ago. But the next time it happens I will
attach it.

- mdf

On Tue, Jun 3, 2008 at 8:17 PM, Bryce Harrington
<email address hidden> wrote:
> Sounds similar to bug 195982. Do you have vmware installed by chance?
>
> Please attach your /var/log/Xorg.0.log following the failure.
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>
> --
> Control characters and caps lock and other control characters don't work in X in Hardy Development
> https://bugs.launchpad.net/bugs/221147
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Matthew Franz
http://www.threatmind.net/

[Matthew Franz (mdfranz)]

I was running vmware-server-console (not VMWare server) and had just switched into Full Screen mode earlier -- that should be what all the modeline changes are in the log

root@mfranz-t61:~# vmware-server-console -v
VMware Server Console 1.0.5 build-80187

[Bryce Harrington (bryce)]

Okay, I've marked it a dupe. If it turns out that when that bug is fixed, this issue doesn't go away, we can look into it further.

[Matthew Franz (mdfranz)]

You can close it -- this appears to be a VMWare bug based on this

http://nthrbldyblg.blogspot.com/2008/06/vmware-and-fubar-keyboard-effect.html

running setxkbmap fixes the issue

On Tue, Jul 29, 2008 at 4:14 PM, Bryce Harrington
<email address hidden> wrote:
> *** This bug is a duplicate of bug 195982 ***
> https://bugs.launchpad.net/bugs/195982
>
> Okay, I've marked it a dupe. If it turns out that when that bug is
> fixed, this issue doesn't go away, we can look into it further.
>
> ** This bug has been marked a duplicate of bug 195982
> Shift key (and caps lock) stop working when using VMWare
>
> --
> Control characters and caps lock and other control characters don't work in X in Hardy Development
> https://bugs.launchpad.net/bugs/221147
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Matthew Franz
http://www.threatmind.net/

[Bryce Harrington (bryce)]

Okay; well we can leave it as a dupe for now.

[penalvch (penalvch)]

Matthew Franz, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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.11-rc5

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Launchpad Janitor (janitor)]

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