Bug 76066 - Server-managed FD: Input ignored
Summary: Server-managed FD: Input ignored
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-12 10:02 UTC by Andreas Reis
Modified: 2015-07-16 22:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Xorg.0.log of working 1.15.0 (39.33 KB, text/plain)
2014-03-12 10:06 UTC, Andreas Reis 		no flags Details
Xorg.0.log of broken git (31.65 KB, text/plain)
2014-03-12 10:07 UTC, Andreas Reis 		no flags Details
Arch Linux's default 10-evdev.conf (1.12 KB, text/plain)
2014-03-12 10:08 UTC, Andreas Reis 		no flags Details
View All

Description Andreas Reis 2014-03-12 10:02:31 UTC 
Since the switch to server-managed FD support the xserver doesn't accept input anymore for me, neither that of my mouse nor that of the keyboard.

I'm using the standard Arch Linux config with only a few minor changes. Before the initial "xf86Xinput: Modify API for server-managed fd support" commit, input still worked fine.

I've updated systemd, xf86-video-intel, xf86-input-evdev, inputproto and a few other dependencies to their most recent git versions at the time of writing.

Notes:

* Logitech G700s, "046d:c07c Logitech, Inc."
* Cherry Cymotion, "046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230"
* xserver is started after login through mingetty with "xinit -- /usr/bin/X -verbose 0 -deferglyphs 16 -quiet -nolisten tcp vt07"
Comment 1 Andreas Reis 2014-03-12 10:06:57 UTC 
Created attachment 95647 [details]
Xorg.0.log of working 1.15.0
Comment 2 Andreas Reis 2014-03-12 10:07:54 UTC 
Created attachment 95648 [details]
Xorg.0.log of broken git
Comment 3 Andreas Reis 2014-03-12 10:08:48 UTC 
Created attachment 95649 [details]
Arch Linux's default 10-evdev.conf

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.