https://bugs.freedesktop.org/show_bug.cgi?id=81819
Priority: medium
Bug ID: 81819
Assignee: [email protected]
Summary: Xwayland crashes when seat adds a capability and sends
some input event
QA Contact: [email protected]
Severity: normal
Classification: Unclassified
OS: All
Reporter: [email protected]
Hardware: Other
Status: NEW
Version: unspecified
Component: XWayland
Product: Wayland
When Xwayland is started while the seat has limited capabilities (i.e. only
pointer) and then later on more capabilities are added, any events sent from
those new devices cause a crash.
This seems to be because in xwayland-input.c:add_device where the devices are
created, xwayland adds them with AddInputDevice, but does not activate or
enable them (with ActivateDevice and EnableDevice), so
miPointerDeviceInitialize is never called on these devices.
The devices with the capabilities present when Xwayland starts do not have this
problem because they are activated and enabled in InitAndStartDevices.
I think adding a call to ActivateDevice, followed by a call to EnableDevice at
the end of add_device should be enough (and it does solve the problem), but I
am not familiar enough with the X server architecture to know if this is the
right solution.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Wayland-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
