Testing current git for full xorg tree with Fedora 8 and kernel 2.6.26.6-49.fc8 from distro. As far as I know, distro does not support evdev. When running the then-current git from a month ago, the X server started up with /etc/X11/xorg.conf from distro, but keyboard and mouse did not work. By suggestion of the log file, the AllowEmptyInput keyword was added to the configuration file, and the X server started up without further problems. With current git as of 2008/11/24 11:00 GMT -5 , xserver tree built from it crashes inmediately with a segfault after using the previously-working configuration file. When removing the AllowEmptyInput keyword, X server starts up again, but again mouse and keyboard are unresponsive. Steps to reproduce: - System uses PS/2 keyboard and mouse - Use distro without evdev support (Fedora 8 in my case) - Prepare xorg.conf with AllowEmptyInput keyword - Attempt to start up xserver from current git Expected results: xserver should start normally Actual results: Screen flickers for a moment, then goes back to command line. Log file shows segfault.
Created attachment 20576 [details] Configuration file used for Xorg Configuration file from system. Compiled tree is in /home/alex/xserver .
Created attachment 20577 [details] Xorg.0.log after X server crashes This is the log file from the xserver right after the crash. Please note the segfault at the end.
Created attachment 20578 [details] Xorg.0.log of previous (working) git tree This is the log file of the working build.
Created attachment 20579 [details] Heads of each git tree used in build Generated with: for i in app/* data/* doc/* driver/* drm font/* lib/* mesa pixman proto/* util/* xcb/* xserver ; do CWD=`pwd`; echo $i >> salida-git-log.txt ; cd "$i"; git-log -1 </dev/null >> /home/alex/checkouts/xserver/git/salida-git-log.txt ; cd $CWD ; done
I merged the wrong patch, patch reverted and the correct one pushed as ec1d08442f69353cb0e73ac4eaf0346ebb975594. Thanks for reporting.
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.