On Thu, 10 Nov 2016 15:47:56 +
Daniel Stone wrote:
> If we destroy the text_input (e.g. due to surface deactivation) whilst
> the IM manager (the client holding the input_method_context resource,
> usually weston-keyboard) sends an event, we can hit a segfault in
> text-backend. This is becau
If we destroy the text_input (e.g. due to surface deactivation) whilst
the IM manager (the client holding the input_method_context resource,
usually weston-keyboard) sends an event, we can hit a segfault in
text-backend. This is because we free the text_input structure, but
don't actually clear the
