Theme änd keyböärd läyöüt göing cräzy

[Florian Schweikert]

Binary package hint: xorg

After coding a while with eclipse, gnome-theme changes (except windowborder) to the (ugly) default theme and AltGr key is reversed. opening the gnome-theme config gui sometimes change it back for a while (exept icons)

i use following Xmodmap:
keycode 108 = Mode_switch
keycode 38 = a A adiaeresis Adiaeresis
keycode 30 = u U udiaeresis Udiaeresis
keycode 32 = o O odiaeresis Odiaeresis
keycode 39 = s S ssharp
keycode 13 = 4 dollar EuroSign
keycode 12 = 3 0xa3 section

so writing a text is pain while this bug is present. (put something heavy on the altgr key from the notebook is not a permanent solution :D)

There are two uk-layout keyboards, one in my notebook a usb one.
notebook is connected to 23" tft through vga (internal disabled).

problem occured 3 or 4 times the last days (since i started to code with eclipse a lot), firefox,empathy and skype also running.
i don't had much time for debugging, but problems only occured when connected to external monitor(and keyboard/mouse).

i use ubuntu 10.10 since the beta version, with compiz, system is up to date.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
Architecture: i386
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DisplayPort.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DisplayPort.3:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: Off
 modes: 1440x900
 edid-base64: AP///////wBMo0JUAAAAAAASAQOQIRV4Cof1lFdPjCcnUFQAAAABAQEBAQEBAQEBAQEBAQEBMCqgGFKEDDBAIDMAS88QAAAaKBygGFKEDDBAIDMAS88QAAAaAAAA/gBYUDk3MYExNTRCVAogAAAAAAAMEBcbNmmp/wIBCiAgAPs=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAEcoQBvjVgARAUAQNoMx14Ku6Vo1RMmSYPUFSzDABxT4EAgYCVANHAAQEBAQEBAjqAGHE4LUBYLEUA/h8RAAAeAAAA/QA4Sx5TEQAKICAgICAgAAAA/ABBY2VyIFQyMzFICiAgAAAA/wBMTjQwVzAwNjQzMDAKADc=
Date: Sun Oct 24 18:13:57 2010
DkmsStatus:
 virtualbox-ose, 3.2.8, 2.6.36-999-generic, i686: built
 virtualbox-ose, 3.2.8, 2.6.35-22-generic-pae, i686: installed
GdmLog:
 Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: sudo: 3 incorrect password attempts
  try again.
GdmLog1:
 Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: GNOME_SUDO_PASSGNOME_SUDO_PASSSorry, try again.
 sudo: 3 incorrect password attempts
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
MachineType: Dell Inc. Latitude E6500
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=36940223-a60d-413a-89ce-e9cee2b04aa1 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: xorg
Symptom: display
dmi.bios.date: 05/06/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A22
dmi.board.name: 0NY667
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA22:bd05/06/2010:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic-pae

[ 8153.393556] show_signal_msg: 15 callbacks suppressed
[ 8153.393560] gnome-settings-[2359]: segfault at 17c ip b7110e21 sp bf8aa1c8 error 4 in libc-2.12.1.so[b70a0000+157000]

[Matthew (matthew-redhat-bugs)]

Description of problem:

I've been using "keycode 135 = Mode_switch" in my ~/.xmodmap for years, to change my "menu" key into something useful.

Starting sometime fairly recently (not sure exactly; sorry) occasionally (no repeatable case, but happens regularly enough to be annoying), the mode_switch gets stuck in on, such that pressing the key and a letter gives its normal version rather than its mode_switch version. (It's as if the equivalent of caps-lock for mode_switch is on.)

There doesn't seem to be any cure but hitting mode_switch a bunch of times and other random typing -- eventually it goes off again.

Version-Release number of selected component (if applicable):

Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev because it's convenient -- could be a lot of things, I suppose.

[Bug (bug-redhat-bugs)]

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Matěj (matj-redhat-bugs)]

(In reply to comment #0)
> Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev because
> it's convenient -- could be a lot of things, I suppose.

Let's try to blame Xserver itself :) (it doesn't matter that much because issues of input go to Peter anyway).

Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

[Matthew (matthew-redhat-bugs)]

Created attachment 378349
dmesg output

[Matthew (matthew-redhat-bugs)]

Created attachment 378350
Xorg.0.log

[Matthew (matthew-redhat-bugs)]

Attached requested logs. This is on my Rawhide box.

It also happens on my F12 system at home, which has a different radeon card and generally different hardware overall. I can attach that if you think it might be helpful.

I think *maybe* the problem is related to the key _next_ to this one; I've defined that to be Multi_key, and it may be related to hitting that accidentally in some way. I still can't reproduce _on purpose_ though. (But it does happen once every couple of days.)

[Matthew (matthew-redhat-bugs)]

Created attachment 378354
xmodmap

I must add that the ability to type hearts and flowers was added at the request of my 4-year-old daughter. Just sayin'.

[Chris (chris-redhat-bugs)]

--
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

[Matthew (matthew-redhat-bugs)]

This is still happening, by the way. And I removed the definition for Multi_key, so that's _not_ it.

[Matthew (matthew-redhat-bugs)]

This is still happening. It is very annoying. I attached the requested information -- see above. Anything else I can do to help get this resolved?

I know this is far from critical path, but it's a very annoying regression.

[Matthew (matthew-redhat-bugs)]

✶°† ™♥i★ i★ ★™ill ♥a☠☠€ñiñℊ wi™♥ ¢urr€ñ™ raw♥i°€• ✓€ry aññ°yiñℊ• Añy ★uℊℊ€★™i°ñ★⁄ Añy ★uℊℊ€★™i°ñ★ a™ all⁄

[Peter (peter-redhat-bugs)]

some beautiful hearts in there though ;)

please run "xkbcomp -xkb $DISPLAY -" when the problem doesn't occur and after it occurs. Does the diff show anything? If so, then we have some corruption in the server. Attach the file here please too, I want to have a look at the layout.

what does xev show once the problem occurs for key presses?

[Matthew (matthew-redhat-bugs)]

Of course, after that last message, it didn't happen for a while. But now it is. I'll post the xkbcomp output after it clears up; here's the xev output for pressing the s key:

KeyPress event, serial 34, synthetic NO, window 0x2e00001,
    root 0xfb, subw 0x0, time 2996500443, (158,13), root:(283,306),
    state 0x2010, keycode 39 (keysym 0x1002605, U2605), same_screen YES,
    XLookupString gives 3 bytes: (e2 98 85) "★"
    XmbLookupString gives 3 bytes: (e2 98 85) "★"
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x2e00001,
    root 0xfb, subw 0x0, time 2996500539, (158,13), root:(283,306),
    state 0x2010, keycode 39 (keysym 0x1002605, U2605), same_screen YES,
    XLookupString gives 3 bytes: (e2 98 85) "★"
    XFilterEvent returns: False

(A bit later)

Okay, yeah, back to normal now. xkbcomp output is unchanged. I'll attach that.

[Matthew (matthew-redhat-bugs)]

Created attachment 410301
xkbcomp -xkb $DISPLAY -

[Matthew (matthew-redhat-bugs)]

Just happened to me again on my newly-reinstalled (fresh; not upgrade) F13 laptop. (Same .xmodmap file.)

Graphics card in this one is "Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7", so I think we can rule out ATI as the problem.

[Pavel (pavel-redhat-bugs)]

You may try to reproduce bug holding down the Mode_switch key, so it starts to "repeat" mode switching regardless of setting for autorepeat option (xset -r).
During this, "state" field in xev cycles +0000 +2000 +4000 (with numlock active it leads to 0x10 0x2010 0x4010 states). If you depress it in correct time, all keys and combinations work well again.
Normal behaviour of M_s key seen as +2000 in active state (pressed), +0000 inactive (depressed).

[Sebastian (sebastian-redhat-bugs)]

Created attachment 452610
xmodmap to reproduce probla

With the attached modmap you can easily reproduce this problem. It uses the space bar as a modifier. Note: You might hate this layout, prepare your own xmodmap on a different console to switch back!

Steps to reproduce:

1. xmodmap .Xmodmap
2. press down 'f' key (do not release it). 'f' appears multiple times
3. press down space bar (do not release it). 'f' stops appearing
4. release 'f' key
5. release space bar
6. you now have a 70% chance that your keyboard is out of sync: Press 'f' key and '(' appears

These instructions work almost always for me to get the keyboard out of sync. Note that you can use the same steps to get in in sync again.
The bug seems easier to reproduce with an idle cpu.

Thanks if you can fix this issue.

[Matthew (matthew-redhat-bugs)]

Thanks Sebastian. That works for me as a test case too, although maybe somewhat less than 70%. Enough that someone who has an idea how to track this down in the actual code should be able to reproduce.

I'm moving this to rawhide now so it doesn't get lost with "ancient" Fedora 13 bugs.

[Florian Schweikert (kelvan)]

there is now a bigger bug, often when activate/deactivate vga-fullhd-monitor the complete system freezes, going to shell or restart xserver with shortcut (i've reactivated it) doesn't work. after the theme-bug occurs i tried started theme-config -> freeze.
I've a few freezes a day, making the system completely useless

[holtzermann17 (holtzermann17)]

I reported a similar issue here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/673851

[Florian Schweikert (kelvan)]

So bug still there, and there are also complete crashes of the xserver now.
For the moment ubuntu 10.10 is just useless for me :(
Even windows is more stable than this.

I would use 10.04.1 but the external display support there is also unusable. (fullhd ext monitor shows whole desktop but cuts windows at the bottom, when internal disply has smaller resolution).

[Matthew (matthew-redhat-bugs)]

Still here. ★iℊ♥•

[Joe (joe-redhat-bugs)]

I'm not sure what the protocol is, but I seem to have the same bug in Red Hat Enterprise Linux Server Release 6.0.

For the record I'll note that there is a similar bug reported in Ubuntu 10.04 and 10.10,
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/665956

[Matthew Miller (mattdm)]

We have the same bug over in Fedora. See https://bugzilla.redhat.com/show_bug.cgi?id=537708

[Matthew (matthew-redhat-bugs)]

Thanks. I've cloned this into RHEL6 bug 664484, and also left a brief note on that Ubuntu bug.

[Joe (joe-redhat-bugs)]

I noticed that in Ubuntu 10.04, plugging in a second USB keyboard resets xmodmap back to its default state (removing both the modmap configurations and, apparently, the modmap-related bug). I wonder if that's true in Fedora as well.

[Peter (peter-redhat-bugs)]

problem is caused by autorepeat of the menu key when Mode_Switch is assigned to it. in XKB terms, Mode_Switch is a group switch to the next level that's reverted back to the original when the key is released.

with autorepeat, the group starts flipping between 0 and 1 for each repeat event. the last key release then toggles the state back, so depending on when you release it may leave the group at 1 (the key appears stuck). can be reproduced or undone by triggering key repeat on the key but because timing is involved, it's not 100% predictable.

not sure of a fix yet.

[Fedora (fedora-redhat-bugs)]

xorg-x11-server-1.9.3-4.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/xorg-x11-server-1.9.3-4.fc14

[Matthew (matthew-redhat-bugs)]

(In reply to comment #23)
> xorg-x11-server-1.9.3-4.fc14 has been submitted as an update for Fedora 14.
> https://admin.fedoraproject.org/updates/xorg-x11-server-1.9.3-4.fc14

I take it you found a fix. Awesome.

Is this going into rawhide as well?

[Peter (peter-redhat-bugs)]

rawhide build got submitted yesterday

http://koji.fedoraproject.org/koji/buildinfo?buildID=213931

[Matthew (matthew-redhat-bugs)]

Thanks. But now I get:

$ xmodmap -e 'add mod2 = Mode_switch'
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 118 (X_SetModifierMapping)
  Value in failed request: 0x17
  Serial number of failed request: 11
  Current serial number in output stream: 11

[Fedora (fedora-redhat-bugs)]

xorg-x11-server-1.9.3-4.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with
 su -c 'yum --enablerepo=updates-testing update xorg-x11-server'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/xorg-x11-server-1.9.3-4.fc14

[Peter (peter-redhat-bugs)]

try xmodmap -p. If your modmap is the same as mine, Mode_Switch is also assigned to Mod5 and needs to be removed from that first.

$ xmodmap -e "add mod2 = Mode_switch"

X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 118 (X_SetModifierMapping)
  Value in failed request: 0x17
  Serial number of failed request: 11
  Current serial number in output stream: 11

$ xmodmap -e "remove mod5 = Mode_switch"
$ xmodmap -e "add mod2 = Mode_switch"

[Fedora (fedora-redhat-bugs)]

xorg-x11-server-1.9.3-4.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.

[Matthew (matthew-redhat-bugs)]

(In reply to comment #28)
> try xmodmap -p. If your modmap is the same as mine, Mode_Switch is also
> assigned to Mod5 and needs to be removed from that first.
>
> $ xmodmap -e "add mod2 = Mode_switch"
>
> X Error of failed request: BadValue (integer parameter out of range for
> operation)
> Major opcode of failed request: 118 (X_SetModifierMapping)
> Value in failed request: 0x17
> Serial number of failed request: 11
> Current serial number in output stream: 11
>
> $ xmodmap -e "remove mod5 = Mode_switch"
> $ xmodmap -e "add mod2 = Mode_switch"

Making this change made the xmodmap not give any errors.

But now I'm not getting alternate characters in gnome-terminal. Hmmm. Works in Xfce terminal, or right here. ♪♫ So I think that's a separate bug.

[bugbot (bugbot)]

Hey Florian,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

[Izidor Matušov (izidor)]

The same bug happens to me on Ubuntu 12.04 with very similar Xmodmap configuration. I would be glad to provide additional information.

[Izidor Matušov (izidor)]

A workaround for Ubuntu 12.04: Remove and the plug in your external keyboard again. It's annoying but still better than logging out and in, or restarting computer.

[penalvch (penalvch)]

Florian Schweikert, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, 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 xorg-server REPLACE-WITH-BUG-NUMBER

Please note, given you already have done this in a prior release, performing this on a release prior to Trusty would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[penalvch (penalvch)]

OR using EOL release, and no response since 2014.