From d278372662152e1a6629e08ff70cc12777f0db57 Mon Sep 17 00:00:00 2001
From: tarek-y-ismail <tarek.ismail@canonical.com>
Date: Tue, 14 Jan 2025 08:17:59 +0000
Subject: [PATCH] Don't leak VirtualInputDevice keyboards (#3720)

Every time an app supporting text-input-v3 starts we allocate a
"virtual-keyboard", we should also deallocate it as appropriate.

This was identified while investigating #3710, and is part of the fix
(possibly all the fix - still testing)
---
 src/server/frontend_wayland/text_input_v3.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/server/frontend_wayland/text_input_v3.cpp b/src/server/frontend_wayland/text_input_v3.cpp
index 422024a5f96..7166157365f 100644
--- a/src/server/frontend_wayland/text_input_v3.cpp
+++ b/src/server/frontend_wayland/text_input_v3.cpp
@@ -333,6 +333,7 @@ mf::TextInputV3::TextInputV3(
 mf::TextInputV3::~TextInputV3()
 {
     seat.remove_focus_listener(client, this);
+    ctx->device_registry->remove_device(keyboard_device);
     ctx->text_input_hub->deactivate_handler(handler);
 }