If the compositor sends events to us while the main thread is blocked
the socket notifier in the events thread would keep sending out the
activated() signal, but no events would actually be read until the
main thread starts to run again. That causes the event thread to keep
queueing new events, and so allocating memory, potentially forever.
This patch fixes the issue in maybe a bit radical way, that is by removing
the event thread. The socket notifier now runs in the main thread so it
will block if the events are not being read.
Nowadays there is no real reason to keep the event thread around, as every
thread that needs to receive wayland events can dispatch them on its own,
we don't need a central dispatcher thread anymore.

Change-Id: Ib7885e4b038b82719d78d193f465618a72cbe6af
Reviewed-by: Pier Luigi Fiorini <[email protected]>

client: Remove the event thread

[spec] Improve spec files parametrization. Contributes to MER#1443



See merge request !2

…Fixes JB#34185

Check the surface hasn't been deleted before initiating the ping so
that an invalid resource isn't dereferenced when printing a warning
after the operation inevitably fails.

Change-Id: I205def680971e50e59d761f16128cd4019234037

[wayland] Fix crash when pinging a surface with an invalid resource. Fixes JB#34185

Check the surface hasn't been deleted before initiating the ping so
that an invalid resource isn't dereferenced when printing a warning
after the operation inevitably fails.

Change-Id: I205def680971e50e59d761f16128cd4019234037

See merge request !3

A ulong timestamp with millisecond resolution overflows after about
49 hours meaning a direct comparison between timestamps is only
valid until that wrap point is reached.

Given the timestamps originate in the compositor when the data source
object is created it is difficult to see what information they provide
which isn't implicit in the order of execution of calls to the function
the check is in, making removing the check the safest course of action.

Change-Id: I1b1d4458b913d54028e5e58d7eb3f217cc5b8186

[qtwayland] Fix copying to the clipboard failing.  Fixes JB#32781

A ulong timestamp with millisecond resolution overflows after a little
under 9 hours meaning a direct comparison between timestamps is only
valid in the first 9 hours the compositor has been running.

Given the timestamps originate in the compositor when the data source
object is created it is difficult to see what information they provide
which isn't implicit in the order of execution of calls to the function
the check is in, making removing the check the safest course of action.

Change-Id: I1b1d4458b913d54028e5e58d7eb3f217cc5b8186

See merge request !5

…s cleared. Contributes to JB#33931

Clear should mean clear.  When a client drops its data source drop the
retained data and notify other clients in the same way as if the client
simply set different data.

Change-Id: Iaff5d0905d788fb990de6f78f06d1d0654285e19

[wayland] Clear the retained clipboard data when a client clipboard is cleared. Contributes to JB#33931

Clear should mean clear.  When a client drops its data source drop the
retained data and notify other clients in the same way as if the client
simply set different data.

Change-Id: Iaff5d0905d788fb990de6f78f06d1d0654285e19

See merge request !4