Xorg intermittent segv in XkbSendMap in ProcXkbGetKbdByName

[dcam]

I see an X server bombout...detail below...it seems like the trigger for this is running VMware player V2 with a VM (eg WinXP) that has vmware tools in it, but it takes a while to reproduce. I can't figure any consistent behaviour to reproduce, just normal use.

My machine also has two keyboard (notebook with external keyboard).

root@vostro:~# gdb -s /usr/lib/debug/usr/bin/Xorg /usr/X11R6/bin/Xorg
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) handle SIGPIPE nostop noprint pass
Signal Stop Print Pass to program Description
SIGPIPE No No Yes Broken pipe
(gdb) attach 7265
...
(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7b686b0 (LWP 7265)]
0xb7c66ec8 in ?? () from /lib/tls/i686/cmov/libc.so.6
(gdb) where
#0 0xb7c66ec8 in ?? () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7c674b6 in free () from /lib/tls/i686/cmov/libc.so.6
#2 0x08135231 in Xfree (ptr=0xa11f1) at ../../os/utils.c:1459
#3 0x0818a191 in XkbSendMap (client=0x9fa2310, xkb=0x9f45890, rep=0xbfc0a6c4)
    at ../../xkb/xkb.c:1409
#4 0x08190eba in ProcXkbGetKbdByName (client=0x9fa2310)
    at ../../xkb/xkb.c:5807
#5 0x08195668 in ProcXkbDispatch (client=0x50d11f0) at ../../xkb/xkb.c:6690
#6 0x0808c89f in Dispatch () at ../../dix/dispatch.c:454
#7 0x08071d1d in main (argc=10, argv=0xbfc0b924, envp=0x50d11f0)
    at ../../dix/main.c:441
(gdb)

This is Ubuntu 8.10, right up to date with latest patches.

root@vostro:~# lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

[Noel (noel-redhat-bugs)]

Description of problem:

If I configure a second monitor (projector) using *either* the Fedora provided nvidia driver *or* the nvidia supported driver, and select a menu in the Fedora provided OpenOffice 3 Impress application (I am trying to do a presentation on dual-monitors), the entire X11 session crashes and restarts.

Please note: the exact same scenario on the same hardware (multi-boot) works flawlessly with Ubuntu 8.10 using the same 177.80 nvidia driver and Ubuntu PPA build of OpenOffice 3, both with and without the new Presenter Mode plugin (Fedora provides the plugin as standard).

This is completely reproducible.

Steps to Reproduce:
1. Connect 2nd display.
2. Configure 2nd display using the appropriate display manager (depending on which driver is in use)
3. Open a presentation in OOo3 Impress, and click the Slide Show menu to attempt to select Slide Show Settings.

Actual results:

One of two things will happen. Either the menu will work because OOo3 does not realize that you have configured the 2nd display (and Slide Show Settings ... will have the option to select a 2nd display grayed out), or the entire X11 session will terminate, and you'll have to wait for it to restart at the login dialog.

Expected results:

The menu should appear, and you should be able to select that the presentation monitor will be on the 2nd display, so that you can start a slide show using the new Presenter mode.

I'll be happy to provide whatever follow-up information you desire.

ThinkPad T61p 6457-7WU, Fedora 10 with all updates as of today.

[Caolan (caolan-redhat-bugs)]

The *entire* X session exits ?

[Caolan (caolan-redhat-bugs)]

There is a few multihead fixes for OOo we're not carrying in that version which I've since added in, but for the entire session to crash suggests more a more fundamental X level bogusity.

caolanm->mcepl: Can you see this problem ?

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

Reporter, there are two things:

a) if you are switching between non-packaged version of nvidia binary-only driver and nv open source driver (BTW, have you tried nouveau?) there are some things which nvidia driver changes outside of the driver itself. So, please, make sure, that your packages are not changed (rpm -Va; or look for more detailed instructions at https://fedoraproject.org/wiki/Xorg/3rd_Party_Video_Drivers).
b) Please, attach /var/log/Xorg.*.log, /var/log/dmesg, /var/log/messages and /etc/X11/xorg.conf (if there is any) as separate uncompressed attachments to this log.

[Noel (noel-redhat-bugs)]

> The *entire* X session exits ?

As in X restarts, and I have to log back in, yes.

> There is a few multihead fixes for OOo we're not carrying in that
> version which I've since added in

Where can I find those? I update from rawhide daily.

> if you are switching between non-packaged version of nvidia
> binary-only driver and nv open source driver ...

First of all, I installed the binary only AFTER reproducing this error in the first place. Second, I uninstalled the binary, rebooted, and checked to make sure that Xorg.0.log had no references to any nvidia provided code. That said ...

> please, make sure, that your packages are not changed (rpm -Va)

OK (but, again, I reproduced this BEFORE ever installing the nvidia driver)

> Please, attach /var/log/Xorg.*.log, /var/log/dmesg,
> /var/log/messages and /etc/X11/xorg.conf

Should be able to do that sometime this week.

[Noel (noel-redhat-bugs)]

Created attachment 323070
/var/log/dmesg

[Noel (noel-redhat-bugs)]

Created attachment 323071
/var/log/messages

[Noel (noel-redhat-bugs)]

Created attachment 323072
/var/log/Xorg.0.log

[Noel (noel-redhat-bugs)]

Created attachment 323073
/var/log/Xorg.0.log.old

[Noel (noel-redhat-bugs)]

Created attachment 323074
/var/log/Xorg.1.log

[Noel (noel-redhat-bugs)]

Created attachment 323075
/var/log/Xorg.1.log.old

[Noel (noel-redhat-bugs)]

Comment on attachment 323074
/var/log/Xorg.1.log

From when I was uninstalling the nvidia drivers.

[Noel (noel-redhat-bugs)]

Comment on attachment 323075
/var/log/Xorg.1.log.old

From when I was uninstalling the nvidia drivers.

[Noel (noel-redhat-bugs)]

> b) Please, attach /var/log/Xorg.*.log, /var/log/dmesg, /var/log/messages and
> /etc/X11/xorg.conf (if there is any) as separate uncompressed attachments to
> this log.

# ls -l messages dmesg Xorg.*
-rw-r--r-- 1 root root 50071 2008-11-10 08:26 dmesg
-rw------- 1 root root 238629 2008-11-10 08:48 messages
-rw-r--r-- 1 root root 162748 2008-11-10 08:37 Xorg.0.log
-rw-r--r-- 1 root root 226796 2008-11-10 08:34 Xorg.0.log.old
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.1.log
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.1.log.old
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.2.log
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.2.log.old
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.3.log
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.3.log.old
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.4.log
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.4.log.old
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.5.log
-rw-r--r-- 1 root root 4842 2008-11-05 22:24 Xorg.5.log.old

I attached /var/log/{dmesg, messages, Xorg.0.log*}. Everything from today is in the Xorg.0.* files; older ones date back to when I uninstalled the nvidia driver, and made sure to force a reinstall of the stock code as outlined in the documents you had referenced. There is no xorg.conf file.

Perhaps you are looking for this:

Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e7746]
1: /usr/bin/Xorg(xf86SigHandler+0x39) [0x47d3a9]
2: /lib64/libc.so.6 [0x3a38a33100]
3: /usr/bin/Xorg(XkbStringText+0x1c) [0x566b7c]
4: /usr/bin/Xorg(XkbWriteXKBGeometry+0x15a) [0x5581fa]
5: /usr/bin/Xorg(XkbWriteXKBKeymapForNames+0x5bb) [0x55777b]
6: /usr/bin/Xorg(XkbDDXLoadKeymapByNames+0x18a) [0x56171a]
7: /usr/bin/Xorg(ProcXkbGetKbdByName+0x3ab) [0x53f58b]
8: /usr/bin/Xorg(Dispatch+0x364) [0x446894]
9: /usr/bin/Xorg(main+0x45d) [0x42ccdd]
10: /lib64/libc.so.6(__libc_start_main+0xe6) [0x3a38a1e546]
11: /usr/bin/Xorg [0x42c0b9]

Fatal server error:
Caught signal 11. Server aborting

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

Peter, isn't there something you want to tell us? :)

[Peter (peter-redhat-bugs)]

wow.

what's the output of setxkbmap -print before the crash happens?

Can you trigger the crash by running setxkbmap -layout us, or another combination of setxkbmap -layout .. -option ... etc?

The reason I ask is that setxkbmap also uses ProcXkbGetKbdByName so maybe we can find a good testcase here.

[Adam (adam-redhat-bugs)]

atropine:/tmp% eu-addr2line -e xorg-x11-server-debuginfo-1.5.2-12.fc10.x86_64/usr/lib/debug/usr/bin/Xorg.debug
0x566b7c
/usr/src/debug/xorg-server-1.5.2/xkb/xkbtext.c:526

Which is the for loop at the top of XkbStringText. Which, uh. Not really sure how that could fault...

[Noel (noel-redhat-bugs)]

*** IMPORTANT *** See the bottom of this report for critical information.

> what's the output of setxkbmap -print before the crash happens?

$ setxkbmap -print
xkb_keymap {
 xkb_keycodes { include "evdev+aliases(qwerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+us+inet(evdev)" };
 xkb_geometry { include "pc(pc104)" };
};

> Can you trigger the crash by running setxkbmap -layout us

[noel@noel-fedora10 ~]$ setxkbmap -layout us
[noel@noel-fedora10 ~]$

So, no.

> or another combination of setxkbmap -layout .. -option ... etc

Give me something concrete to try, and I'll be happy to do so. :-)

*** HOWEVER *** we now have a new and different problem: AFTER TODAY'S UPDATES from rawhide, Impress no longer realizes that I have multiple monitors! If I go into the Slide Show, anyway, Impress splits the slides across the expanded, virtual, display. Impress does not go full-screen incorrectly, it just handles the Slide Show incorrectly. I have tried rebooting with the second display connected and with it disconnected. I have tried toggling it off and back on. So far, I cannot get Impress to recognize that the second display exists.

I will attach the current Xorg.0.log to show today's situation. Once we get THAT fixed, we can get back to this problem. Do you want for me to open a new bug report?

[Noel (noel-redhat-bugs)]

Created attachment 323283
/var/log/Xorg.0.log

Two monitors configured, but Impress Slide Show Settings don't know about multiple monitors.

[Bug (bug-redhat-bugs)]

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

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

[Noel (noel-redhat-bugs)]

OK, we are back to reproducing this defect.

As noted in Bug 474719, we must use the nvidia driver because for whatever reason, OOov3 on Fedora 10 no longer recognizes multiple monitors when using nv or when using nvidia in Twinview mode (as noted in Bug 474719, I also tried the nouveau driver, but nouveau refuses to do anything other than mirror the displays). The only way to get Impress to recognize multiple monitors on Fedora 10 appears to be using nvidia with separate X screens.

I am attaching my xorg.conf file and the Xorg log file.

[Noel (noel-redhat-bugs)]

Created attachment 325879
xorg.conf for Fedora 10 using Xinerama

[Noel (noel-redhat-bugs)]

Created attachment 325892
Shows the Xorg session crash

This is the crash with the Fedora 10 generated xorg.conf using nvidia and Xinerama and lacking the "Files" section (see comments in bug report).

[Noel (noel-redhat-bugs)]

OK, I finally have it working. I had to use the nvidia driver -- nv and nouveau are not working -- with xinerama disabled.

It is very easy to crash X on Fedora 10, as noted in the logs, even with Fedora 10 generated xorg.conf files. And it is not consistent in that the same section whose absence causes it to crash causes it not to crash depending on what else is in xorg.conf. I have not tried to do an exhaustive test, just noted differences in content and behavior. I've tried the xorg.conf file that was initially laid down by the RPM, as well as those generated by nvidia-settings on Fedora 10 (discounting those that I pulled over from Ubuntu when I was having a problem with nvidia-settings on Fedora).

Ideally, Bug 474719 will be resolved, and we won't have to deal with some of the xorg.conf issues.

[Nigel (nigel-redhat-bugs)]

Found this report after getting a very similar stacktrace:

Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812bc5b]
1: /usr/bin/Xorg(xf86SigHandler+0x51) [0x80bcc81]
2: [0x110400]
3: /usr/bin/Xorg(XkbStringText+0x2d) [0x81b0d0d]
4: /usr/bin/Xorg(XkbWriteXKBGeometry+0x1bf) [0x81a10ff]
5: /usr/bin/Xorg(XkbWriteXKBKeymapForNames+0x610) [0x81a0400]
6: /usr/bin/Xorg(XkbDDXLoadKeymapByNames+0x1d7) [0x81ab4c7]
7: /usr/bin/Xorg(ProcXkbGetKbdByName+0x40e) [0x81875be]
8: /usr/bin/Xorg [0x818c808]
9: /usr/bin/Xorg(Dispatch+0x34f) [0x8085e9f]
10: /usr/bin/Xorg(main+0x47d) [0x806b71d]
11: /lib/libc.so.6(__libc_start_main+0xe5) [0xa886d5]
12: /usr/bin/Xorg [0x806ab01]

Have seen it with OO3, but also getting without OO3 anywhere in site. I actually hit it today seemingly when using PackageKit (firefox, went to site which needed a new plugin)

Various apps seem to cause it, not found a reproducible pattern yet.

Language is en_GB, T60p laptop. Similr config to F9 where the issue did not occur.

My video driver is "radeonhd", also with F10, and all xorg* updates from the updates channel as of 11 Dec.

I do use a second screen (although it's not connected now) when at work, so I have a "Virtual 3200 1600" in xorg.conf which appeared to be needed for radeonhd (but not the ati driver)

Also found similar report at https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/297442 for Ubuntu 8.10

Can provide more details if it helps (or raise seperate defect if required)

[Nigel (nigel-redhat-bugs)]

Also seems related to a new report https://bugzilla.redhat.com/show_bug.cgi?id=475746

[Artem (artem-redhat-bugs)]

*** Bug 475746 has been marked as a duplicate of this bug. ***

[Artem (artem-redhat-bugs)]

Agree with Nigel, that it's not related to OO3 impress, however I had OO3 Writer always just opened (did nothing).
P.S. intel video driver with no single external monitor working (just external VGA, LVDS is off) (dual-head stuff is not working properly anyway)

[Noel (noel-redhat-bugs)]

Back to being able to reproduce this, so here is the stack trace:

Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e7a26]
1: /usr/bin/Xorg(xf86SigHandler+0x39) [0x47a679]
2: /lib64/libc.so.6 [0x39a0832f90]
3: /usr/bin/Xorg(XkbStringText+0x1c) [0x56711c]
4: /usr/bin/Xorg(XkbWriteXKBGeometry+0x191) [0x5587d1]
5: /usr/bin/Xorg(XkbWriteXKBKeymapForNames+0x5bb) [0x557d1b]
6: /usr/bin/Xorg(XkbDDXLoadKeymapByNames+0x18a) [0x561cba]
7: /usr/bin/Xorg(ProcXkbGetKbdByName+0x3ab) [0x53fb2b]
8: /usr/bin/Xorg(Dispatch+0x364) [0x4468d4]
9: /usr/bin/Xorg(main+0x45d) [0x42cd1d]
10: /lib64/libc.so.6(__libc_start_main+0xe6) [0x39a081e576]
11: /usr/bin/Xorg [0x42c0f9]

Fatal server error:
Caught signal 11. Server aborting

[Peter (peter-redhat-bugs)]

Reassigning to me, this seems to be uninitialised memory or so in xkb. A scratch build for testing is available (see below) which should avoid the issue.

http://koji.fedoraproject.org/scratch/whot/task_1041247/

To narrow this down further:
if you run xkbcomp -xkb :0 -, is anyone affected by this bug NOT getting a BadAlloc error? Anyone NOT on x86_64?

[Noel (noel-redhat-bugs)]

Peter, I have fully updated Fedora 10 from updates-testing, including OO3, and no longer see this problem.

[Rogutės (roguts-redhat-bugs)]

The bug title is misleading, but I guess my bug is the same. I'm not using Fedora/Redhat, but since this bug is in xkb (and, actually, similarly looking xkb bugs are all over the bugtrackers), I hope I can contribute with a comment or two.

I can now easily reproduce it by letting this run for a minute:
  while;do setxkbmap -layout us;sleep 1;done
and using X normally (running firefox/terminal/openoffice).
Noel's backtrace has more symbols, thus I am not attaching mine, but it seems to die on ProcXkbGetKbdByName.

Additionaly, X log includes this (and a memory map):
[xkb] BOGUS LENGTH in write keyboard desc, expected 5548, got 5564
*** glibc detected *** /usr/bin/X: double free or corruption (!prev): 0x09a62df8 ***

I have reproduced it with xorg-server 1.5.3 and 1.6.0 RC1.

Peter:
I am running x86 and have no xorg.conf and no custom HAL policies, and after starting X, `xkbcomp -xkb :0 -` yields the BadAlloc error, but the error disappears after running setxkbmap.

[Nigel (nigel-redhat-bugs)]

Is the scratch xkb build still available?

I'm unable to get to http://koji.fedoraproject.org/scratch/whot/task_1041247/

I am getting this bug frequently.

x86 (PAE kernel)

bash-3.2$ xkbcomp -xkb :0
Warning: Could not load keyboard geometry for :0
                  BadAlloc (insufficient resources for operation)
                  Resulting keymap file will not describe geometry
Error: Cannot open "server-0.xkb" to write keyboard description
                  Exiting
bash-3.2$

[Nigel (nigel-redhat-bugs)]

In comment #30, Noel mentioned he'd applied all updates-testing updates to F10 and no longer saw the issue.

I too have all updates-testing updates, but sadly *do* still see the issue :-(

I've not tried rawhide. Generally I'd probably pop it on sometime between beta and preview. I know alpha is soon.. a little reluctant to go down that route, but if there's any indication it might be fixed there then I would give it a whirl.

ANy thoughts in terms of
 - xserver config
 - OOO3 config

that might remove/reduce the risk of the problem occuring (other than not using Ooo3+dual screens)
?

[Peter (peter-redhat-bugs)]

*** Bug 479122 has been marked as a duplicate of this bug. ***

[Peter (peter-redhat-bugs)]

Updating bug title.

[Milos (milos-redhat-bugs)]

With current F10 X.org server (xorg-x11-server-Xorg-1.5.3-11.fc10.x86_64) I see lot of following errors:

(EE) Error loading keymap /var/lib/xkb/server-0.xkm

around of detecting my Trust mouse (see the bug marked as duplicate in comment #34) -- btw you marked the bug as duplicate, but isn't the main problem of that bug, that the mouse is identified as a keyboard?

[Nigel (nigel-redhat-bugs)]

Changed 2 things about 5 days ago -- and no crashes since

1. In keyboard preferences *deselected* option "Seperate layout for each window"
2. Disabled screensaver

I've susbsequently applied F11 alpha/rawhide and will likely reintroduce the above settings to see if the issue comes back, but good news so far.

[Peter (peter-redhat-bugs)]

(In reply to comment #36)
> around of detecting my Trust mouse (see the bug marked as duplicate in comment
> #34) -- btw you marked the bug as duplicate, but isn't the main problem of that
> bug, that the mouse is identified as a keyboard?

No, a lot of mice these days are keyboards too.

[Kevin (kevin-redhat-bugs)]

Created attachment 331592
backtrace from gdb hooked to X after crash

I can recreate this at will, however it involves a USB Belkin KVM switch.

I can recreate on x86_64 and i386. This is a backtrace from gdb hooked up to X which I captured this morning.

System setup:
x86_64 F10 machine with it's own monitor and all updates
i386 F10 machine with it's own monitor and all updates
USB Mouse & Keyboard hooked to Belkin USB KVM 2-port switch to control which machine has Mouse & Keyboard control

Steps to reproduce:
1. Log into both machines
2. Open OpenOffice (any one will do)
3. Use KVM switch to change keyboard / mouse ownership to other machine
4. If crash doesn't occur, switch back and it will crash.

I can reproduce 95% of the time. I can reproduce on either machine (i386 or x86_64). Both systems have NVIDIA Quadros, but different models requiring different nvidia drivers -- but I have the latest for each.

[Milos (milos-redhat-bugs)]

...the xorg-x11-server-Xorg-1.5.3-11 has *not* disabled writing the geometry, I guess? Today after more than month without any problems when living with the build you pointed in [1], I've been hit again, probably because of the recent update to -11:

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7b66]
1: /usr/bin/X(xf86SigHandler+0x39) [0x47a679]
2: /lib64/libc.so.6 [0x3d7aa32f90]
3: /usr/bin/X(XkbWriteXKBGeometry+0x14c) [0x55880c]
4: /usr/bin/X(XkbWriteXKBKeymapForNames+0x5bb) [0x557d9b]
5: /usr/bin/X(XkbDDXLoadKeymapByNames+0x18a) [0x561d3a]
6: /usr/bin/X(ProcXkbGetKbdByName+0x3ab) [0x53fbab]
7: /usr/bin/X(Dispatch+0x364) [0x4468d4]
8: /usr/bin/X(main+0x45d) [0x42cd1d]
9: /lib64/libc.so.6(__libc_start_main+0xe6) [0x3d7aa1e576]
10: /usr/bin/X [0x42c0f9]

Unfortunately the link to the koji build from [1] shows nothing now and I also couldn't find the RPMs from the given Koji task -- could you please post your packages with disabled geometry writing somewhere for the meantime:)? Thanks in advance.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=479122#c5

[Peter (peter-redhat-bugs)]

Upstream bug: http://bugs.freedesktop.org/show_bug.cgi?id=20081

I think I may have found the issue. Can you please try the following package:
http://koji.fedoraproject.org/scratch/whot/task_1123333/

If it doesn't work, here's the same patch as in Comment #29 on top of 1.5.3-11:
http://koji.fedoraproject.org/scratch/whot/task_1122850/

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

*** Bug 483272 has been marked as a duplicate of this bug. ***

[Peter (peter-redhat-bugs)]

For some reason bodhi didn't add the comment. This bug has been fixed in xorg-x11-server-1.5.3-13.fc10 and is available from the testing repository.

https://admin.fedoraproject.org/updates/F10/FEDORA-2009-1763

[Fedora (fedora-redhat-bugs)]

xorg-x11-server-1.5.3-13.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.

[dcam (david-pastornet)]

The external keyboard is a PS2 plug keyboard connected to the computer with a USB to PS2 adaptor. dmesg for it shows this:

[43384.916476] usb 7-5.2: new low speed USB device using ehci_hcd and address 8
[43385.016916] usb 7-5.2: configuration #1 chosen from 1 choice
[43385.024289] input: HID 04d9:1400 as /devices/pci0000:00/0000:00:1d.7/usb7/7-5/7-5.2/7-5.2:1.0/input/input16
[43385.072270] input,hidraw2: USB HID v1.10 Keyboard [HID 04d9:1400] on usb-0000:00:1d.7-5.2
[43385.085077] input: HID 04d9:1400 as /devices/pci0000:00/0000:00:1d.7/usb7/7-5/7-5.2/7-5.2:1.1/input/input17
[43385.138036] input,hidraw3: USB HID v1.10 Mouse [HID 04d9:1400] on usb-0000:00:1d.7-5.2

This could be related...I also had a situation today where my two keyboards were accepting input on an alternating basis. One keyboard would accept one character only, subsequent keystrokes would do nothing until a character was typed on the other keyboard, and vice-versa. I restarted the X server and the problem went away.

[Timo Aaltonen (tjaalton)]

You need to try to reproduce it on 9.04.

[dcam (david-pastornet)]

This is a critical system for my work and 9.04 is still alpha-ware, though I do have some free partition space that could suit.

You can see that there are two keyboard character devices (13,68) and (13,65), but the (13,68) gets two named entries - that's fine...

root@vostro:~# find /dev/input -name "*kbd" -exec ls -alL {} \;
crw-rw---- 1 root root 13, 68 2009-02-26 20:50 /dev/input/by-path/pci-0000:00:1d.7-usb-0:5.2:1.0-event-kbd
crw-rw---- 1 root root 13, 65 2009-02-26 20:31 /dev/input/by-path/platform-i8042-serio-0-event-kbd
crw-rw---- 1 root root 13, 68 2009-02-26 20:50 /dev/input/by-id/usb-04d9_1400-event-kbd

I'm trying to see whether putting some explicit keyboard configs into /etc/X11/xorg.conf as follows helps to make this problem go away:

In the ServerLayout section:
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Keyboard1" "SendCoreEvents"

Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "Name" "Built-in Keyboard"
    #can't use this device option, as using it produces garbage characters for some unknown reason
    #Option "Device" "/dev/input/by-path/platform-i8042-serio-0-event-kbd"
    Option "XkbModel" "pc105"
    Option "XkbRules" "xorg"
    Option "XkbLayout" "us"
EndSection

Section "InputDevice"
    Identifier "Keyboard1"
    Driver "kbd"
    Option "Name" "External Keyboard"
    Option "Device" "/dev/input/by-id/usb-04d9_1400-event-kbd"
    Option "XkbModel" "pc105"
    Option "XkbRules" "xorg"
    Option "XkbLayout" "us"
EndSection

[dcam (david-pastornet)]

Didn't help.... just got another X bombout.

The /var/log/Xorg.0.log says:

BOGUS LENGTH in write keyboard desc, expected 5704, got 5720

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xb7fc2400]
2: /lib/tls/i686/cmov/libc.so.6(cfree+0x96) [0xb7c1e4b6]
3: /usr/X11R6/bin/X(Xfree+0x21) [0x8135231]
4: /usr/X11R6/bin/X [0x818a191]
5: /usr/X11R6/bin/X(ProcXkbGetKbdByName+0xeaa) [0x8190eba]
6: /usr/X11R6/bin/X [0x8195668]
7: /usr/X11R6/bin/X(Dispatch+0x34f) [0x808c89f]
8: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bc3685]
10: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.

[Bryce Harrington (bryce)]

Please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions.

Like Timo says, our development focus is Jaunty. But if you can collect a good enough backtrace, maybe we can figure out on our end if the issue still exists in the jaunty code.

[Bryce Harrington (bryce)]

There was a pretty significant Xkb string bug that caused segfaults that has since been fixed in jaunty. I'll hazard to bet that fix covers this crash too, and am going to close the bug. If I'm wrong, do please reopen the bug (but we'll need that full backtrace too).

[Tomas Janousek (lis)]

This looks very similar to https://bugs.freedesktop.org/show_bug.cgi?id=21464

[dcam (david-pastornet)]

This problem is NOT fixed in Jaunty.

root@vostro:~# lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

Here's an entry from Xorg.0.log under Jaunty:

[xkb] BOGUS LENGTH in write keyboard desc, expected 5408, got 5424

Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7f24400]
3: /lib/tls/i686/cmov/libc.so.6(cfree+0x96) [0xb7b4c5b6]
4: /usr/X11R6/bin/X(Xfree+0x21) [0x8139021]
5: /usr/X11R6/bin/X [0x8194661]
6: /usr/X11R6/bin/X(ProcXkbGetKbdByName+0xec3) [0x819b403]
7: /usr/X11R6/bin/X [0x819fc38]
8: /usr/X11R6/bin/X(Dispatch+0x33f) [0x808d57f]
9: /usr/X11R6/bin/X(main+0x3bd) [0x80722ed]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7af1775]
11: /usr/X11R6/bin/X [0x80717a1]

[dcam (david-pastornet)]

A patch has just been released that claims to fix this...see http://bugs.freedesktop.org/show_bug.cgi?id=21464

[dcam (david-pastornet)]

If anyone can't wait (like me), I've built an Xorg binary for Ubuntu Jaunty that incorporates the patch provided above, and also restores the AllowDeactivateGrabs functionality as per https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/338489
Binary is at http://www.aaa.net.au/campbell/Xorg.tar.bz2 and is a drop-in replacement for /usr/bin/Xorg but do back up your original. If installing you'll likely need to stop the gdm service, then restart it after you're done.

[dcam (david-pastornet)]

As per http://bugs.freedesktop.org/show_bug.cgi?id=21464 the patch is now in Xorg 1.6.1.902.

Once the new X server becomes part of Ubuntu, then this problem should go away.

In the meantime, I've been using the custom Xorg binary as in the previous comment for some time now and have not seen a crash at all with it. I'm convinced the patch solves the problem.

[Bryce Harrington (bryce)]

According to the upstream bug report, this should now be fixed in the version of xserver we have in Karmic, so I'm closing it as fixed. If this is incorrect please feel free to reopen with additional details.