Boyan Ding 1ba4fde101 xwayland: Activate and enable device on first capability reporting ... Commit 2172714c changed behavior of capability handling, but it only solved part of the problem. If Xwayland is launched without a capability (e.g. no pointer device is connected when Xwayland was spinned up), and later that capability comes, the device added will not be automatically initialized. This patch initializes the device when the capability is reported for the first time, thus avoiding the problem. Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=81819 Signed-off-by: Boyan Ding <stu_dby@126.com> Reviewed-by: Daniel Stone <daniels@collabora.com>		2015-09-21 08:48:47 +02:00
..
.gitignore	Xwayland DDX	2014-04-03 15:19:22 -07:00
drm.xml	xwayland: Add glamor and DRI3 support	2014-06-24 15:09:55 -07:00
Makefile.am	xwayland: Add dependency on glamor libs	2015-03-24 12:01:38 -07:00
xwayland-cursor.c	xwayland: call through to miPointerWarpCursor on warp_cursor	2015-09-18 14:55:00 +02:00
xwayland-cvt.c	Xwayland DDX	2014-04-03 15:19:22 -07:00
xwayland-glamor.c	glamor: add support for allocating linear buffers (v2)	2015-06-30 12:17:55 +10:00
xwayland-input.c	xwayland: Activate and enable device on first capability reporting	2015-09-21 08:48:47 +02:00
xwayland-output.c	xwayland: Don't (double) destroy RANDR resources in CloseScreen	2015-08-12 08:53:38 -07:00
xwayland-shm.c	xwayland: keep temp files out of the client mask	2015-06-25 14:11:35 +02:00
xwayland.c	xwayland: Remove related touchpoints when unrealizing windows	2015-09-18 14:55:00 +02:00
xwayland.h	xwayland: Remove related touchpoints when unrealizing windows	2015-09-18 14:55:00 +02:00