Peter Hutterer 15460eaed2 systemd-logind: let the logind code decided whether to close an fd ... We can only request one fd per device from systemd-logind. If a fd is re-used by the same device, releasing the fd from one device doesn't mean we can close it. The systemd code knows when it's really released, so let it close the fd. Test case: xorg.conf section for an input device with hotplugging enabled. evdev detects the duplicate and closes the hotplugged device, which closes the fd. The other instance of evdev thinks the fd is still valid so now you're playing a double lottery. First, which client(s) will get the evdev fd? Second, which requests will be picked up by evdev and which ones will be picked up by the client? You'll never know, but the fun is in finding out. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>		2014-05-05 07:26:33 +10:00
..
dmx	dmxConfigCanvasUpdate: Delay dereference until after checking for NULL	2014-04-21 20:54:22 -07:00
kdrive	kdrive: Ignore failure to chown console tty to current user	2014-04-18 16:30:17 -07:00
vfb	Build fbcmap_mi.c once, rather than once for each DDX	2014-03-27 14:34:06 +00:00
xfree86	systemd-logind: let the logind code decided whether to close an fd	2014-05-05 07:26:33 +10:00
xnest	Build fbcmap_mi.c once, rather than once for each DDX	2014-03-27 14:34:06 +00:00
xquartz	XQuartz: Ensure we wait for the server thread to terminate	2014-04-06 05:32:03 -07:00
xwayland	xwayland: Remove left-over ErrorF logging	2014-04-21 11:25:12 -07:00
xwin	Build fbcmap_mi.c once, rather than once for each DDX	2014-03-27 14:34:06 +00:00
Makefile.am	Xwayland DDX	2014-04-03 15:19:22 -07:00