After I updated my kernel I can't no longer run the X-server, it still works on the old kernel. I have tested: linux-1.6.17-gentoo2 with xorg-server-1.1.0 -> crash linux-1.6.17-gentoo2 with xorg-server-1.1.1 -> crach linux-1.6.16-ck11 with xorg-server-1.1.0 -> runs linux-1.6.16-ck11 with xorg-server-1.1.1 -> runs linux-1.6.16.24 (vanilla) with xorg-server-1.1.1 -> runs linux-1.6.17.4 (vanilla) with xorg-server-1.1.1 -> runs
Created attachment 6223 [details] Xorg.0.log - X11 logfile
Created attachment 6224 [details] xorg.conf - X11 configuration file NOTE: Not all sections in the config file are used, pleace check the ServerLayout section to see what other sections are used.
yes, the kernel apparently changed around your input devices, so the device you've specified as a pointer, no longer exists, or is no longer a pointer.
This is a bug in X, X shuld not crach and reproduce a stacktrace in this case (it should never crach)
I have a similar problem if I dont specify a device but a Name. It crashes with the same trace. It crashes because inputInfo.pointer->valuator is NULL.. My logitech MX3100 keyboard+mouse wireless combo thingy creates has two devices, event0 which is just the regular keyboard and event1 which is the 12 button mx1000 mouse and the "multimedia keys" from the keyboard.. If I create two InputDevices and load both of them from ServerLayout it works (obviously I have to put the Device Option to force each of the sections to load the right one)... Can't evdev just open more than one device?
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
No update for over two years, closing as WONTFIX. Please reopen if this is still an issue with the current release.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.