1 files changed, 0 insertions, 25 deletions

diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/2924.toml b/gitlab/issues/target_missing/host_missing/accel_missing/2924.toml
deleted file mode 100644
index f52e9f6b..00000000
--- a/gitlab/issues/target_missing/host_missing/accel_missing/2924.toml
+++ /dev/null
@@ -1,25 +0,0 @@
-id = 2924
-title = "qemu-user not responding to Ctrl-C from gdb"
-state = "opened"
-created_at = "2025-04-18T13:49:57.464Z"
-closed_at = "n/a"
-labels = ["linux-user"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/2924"
-host-os = "Ubuntu 24.04.2 LTS"
-host-arch = "aarch64"
-qemu-version = "qemu-x86_64 version 9.2.94 (v10.0.0-rc4)"
-guest-os = "N/A"
-guest-arch = "aarch64"
-description = """When attached to qemu-x84_64's gdbserver via gdb, it is not possible to interrupt the binary being emulated. Usually, Ctrl-C will interrupt a running binary from gdb and I believe (though have not tested) it works in qemu-system.
-
-First Ctrl-C will do nothing and second will prompt to stop debugging.
-```
-(gdb) c
-Continuing.
-^C^CThe target is not responding to interrupt requests.
-Stop debugging it? (y or n)
-```"""
-reproduce = """1. Run `./qemu-x86_64 -g 1234 ~/Downloads/base64-x64_64-static` or any static binary that will pause/hang
-2. Connect from gdb `(gdb) target remote :1234`
-3. Ctrl-C in gdb"""
-additional = "n/a"