FS#41398 - [xorg-server] doesn't load mouse keyboard (xorg-sesrver 1.16)
Attached to Project:
Arch Linux
Opened by Stefan O. (hybrid) - Wednesday, 30 July 2014, 14:40 GMT
Last edited by Laurent Carlier (lordheavy) - Monday, 04 August 2014, 07:54 GMT
Opened by Stefan O. (hybrid) - Wednesday, 30 July 2014, 14:40 GMT
Last edited by Laurent Carlier (lordheavy) - Monday, 04 August 2014, 07:54 GMT
|
Details
Description:
After the upgrade to xorg-server 1.16 xorg ignores mouse and keyboard completely. Can't do anything, can't switch to tty either. System doesn't freeze though, I can ssh into it and kill x. On tty both mouse and keyboard work. Downgrading to xorg-server 1.15 and xf86-input-evdev-2.9.0-1 (since -2 conflicts with xorg-server<1.16) works as desired. Multiple reports on the forums on this issue (https://bbs.archlinux.org/viewtopic.php?id=184971, https://bbs.archlinux.org/viewtopic.php?id=184969). My mouse and keyboard are both regular usb devices, nothing special. If you need more information, please let me know. Additional info: * package version(s) working configuration: xorg-server-1.15.2-1 xf86-input-evdev-2.9.0-1 xorg-server-common-1.16.0-5 not working configuration xorg-server-1.16.0-5 xf86-input-evdev-2.9.0-2 * config and/or log files etc. Xorg.log is attached Steps to reproduce: Install xorg-server 1.16.0-5 and xf86-evdev 2.9.0-2. 
Xorg.0.log.old
(17.2 KiB)
|
This task depends upon
Closed by Laurent Carlier (lordheavy)
Monday, 04 August 2014, 07:54 GMT
Reason for closing: Not a bug
Additional comments about closing: already covered by the news item and post-install message
Monday, 04 August 2014, 07:54 GMT
Reason for closing: Not a bug
Additional comments about closing: already covered by the news item and post-install message
exec xinit /home/rick/.rwm -- :0 -ac -retro
to:
if [ -z "$XDG_VTNR" ]; then
exec xinit /home/rick/.rwm -- :0 -ac -retro
else
exec xinit /home/rick/.rwm -- :0 -ac -retro vt$XDG_VTNR
fi
(which I copied from /etc/X11/xinit/xserverrc )
and now it works fine.
a) How can I then spawn x on vt7? I deliberately want it there.
b) The others affected by that behaviour may not be starting x the way I did. So there may be more to this.
When starting X from a text console leaves X with no input devices, although there are systemd-logind labeled messages from the X server (in its own format - WTF?) in the Xorg.log file enumerating the existing input devices correctly. X just does not initialize the actual drivers after this. No error messages either.
The situation is different when I start kdm at boot. This leaves a working X server and the input device drivers are initialized by X after they have been been mentioned in the systemd-logind labeled X server messagaes.
Please look into the "X as user"/systemd integration changes that were introduced into arch with xorg server 1.16. I strongly suspect these to be responsible, although I do not have the time to dig into this issue more. Maybe add the option to disable/revert those changes?
[angelo@utilite ~]$ cat .xstartupscript
if [ -z "$XDG_VTNR" ]; then
exec xinit /usr/bin/lxsession -- :0 -ac -retro
else
exec xinit /usr/bin/lxsession -- :0 -ac -retro vt$XDG_VTNR
fi