Bug 463147

Thanks for the bug report.  We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) 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.

What does setxkbmap -print gives you?

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.

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

Thanks in advance.

Created attachment 317361 [details]
xorg.conf

Created attachment 317362 [details]
Xorg.1.log with backtrace

Output from 'setxkbmap -print':

xkb_keymap {
	xkb_keycodes  { include "xfree86+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(pc105)"	};
	xkb_geometry  { include "pc(pc105)"	};
};


It seems the exact key COMPOSE is mapped to does not matter - the server also crashed when I tried to map COMPOSE to other keys.

Created attachment 317367 [details]
Xorg.0.log with no /etc/X11/xorg.conf

With this (non-) configuration, the X server recognizes neither the internal nor the external USB keyboard.  The machine is a Lenovo Thinkpad X61t.

(In reply to comment #5)
> With this (non-) configuration, the X server recognizes neither the internal
> nor the external USB keyboard.  The machine is a Lenovo Thinkpad X61t.

That's a bug that is fixed in xorg-x11-server-1.5.0-2.fc9.

I can't reproduce the crash here though. Just to narrow it down - can you please remove the wacom-related entries from your xorg.conf and test again. If that doesn't help, please install xorg-x11-server-debuginfo and post the (hopefully more detailed) backtrace.

(In reply to comment #6)

> I can't reproduce the crash here though. Just to narrow it down - can you
> please remove the wacom-related entries from your xorg.conf and test again. If
> that doesn't help, please install xorg-x11-server-debuginfo and post the
> (hopefully more detailed) backtrace.

Thanks for taking the time with this!  I've tried a configuration without the wacom-related entries, and compose works fine in this case.  As soon as I switch on one of the wacom devices in xorg.conf, the Xserver crashes when I try to map compose to something.

changing to linuxwacom - maybe Aristeu has seen that before.
Looks like incomplete xkb initialisation, which should probably be fixed in both the driver and the server.

I finally managed to run gdb remotely and obtain a stack trace for this crash:

Program received signal SIGSEGV, Segmentation fault.
0x0000000000541086 in _XkbSetNames (client=0x1449f10, dev=0x1332740, stuff=0x141c450) at xkb.c:4166
4166	            edev.ledID=		dev->kbdfeed->ctrl.id;
(gdb) where
#0  0x0000000000541086 in _XkbSetNames (client=0x1449f10, dev=0x1332740, stuff=0x141c450) at xkb.c:4166
#1  0x0000000000541454 in ProcXkbSetNames (client=0x1449f10) at xkb.c:4282
#2  0x0000000000446734 in Dispatch () at dispatch.c:454
#3  0x000000000042cb7d in main (argc=8, argv=0x7fff56e7d638, envp=<value optimized out>) at main.c:441


Currently installed versions are

xorg-x11-drv-evdev.x86_64                  2.0.8-1.fc9 
xorg-x11-server-Xorg.x86_64                1.5.2-3.fc9

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.