Comment 28 for bug 290252

I'm affected by this problem too - happens every now and then (but this morning already 3 times). I'm running (uname -a):
Linux beowulf 2.6.27-12-generic #1 SMP Thu Feb 5 09:26:35 UTC 2009 i686 GNU/Linux

After the crash, I can see in Xorg.0.log.old the backtrace:

0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xb7f90400]
2: /usr/X11R6/bin/X(XkbWriteXKBGeometry+0x181) [0x81a9ed1]
3: /usr/X11R6/bin/X(XkbWriteXKBKeymapForNames+0x610) [0x81a9210]
4: /usr/X11R6/bin/X(XkbDDXLoadKeymapByNames+0x1d7) [0x81b41c7]
5: /usr/X11R6/bin/X(ProcXkbGetKbdByName+0x40e) [0x819041e]
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) [0xb7b96685]
10: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.

I'm attaching my .xsession_errors as well.

Doing quick googles, I see at least a couple bugs that seem to deal with the same problem:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/297442
http://bugs.freedesktop.org/show_bug.cgi?id=20081

But I don't understand what the resolutions really mean as I'm not all that Linux savvy. All I really want to know is: is it fixed somewhere and where/how do I pick up the fix? Or do I have to wait for the next Ubuntu release?