From 3e4c5a6261770bced301b5e74233e7866166ea5b Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Sun, 1 Jun 2025 21:35:14 +0200 Subject: clean up repository --- gitlab/issues_text/target_missing/host_missing/accel_missing/2676 | 7 ------- 1 file changed, 7 deletions(-) delete mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/2676 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/2676') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2676 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2676 deleted file mode 100644 index 0155be972..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/2676 +++ /dev/null @@ -1,7 +0,0 @@ -GTK+ UI has serious problems on macOS hosts -Description of problem: -The GTK+ UI simply does not work on macOS at this stage. One major reason is that there does not appear to be any regular polling of the (macOS) UI event loop. The Cocoa back-end for GTK [sets a custom event polling function in GLib's event handler](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/macos/gdkmacoseventsource.c?ref_type=heads#L1089) but Qemu never actually calls GLib/GTK's event polling. - -Thanks to @bonzini for discovering this as part of a [discussion on a patch generalising runloop event handling on macOS](https://patchew.org/QEMU/20241113142343.40832-1-phil@philjordan.eu/20241113142343.40832-2-phil@philjordan.eu/#CABgObfat1JwiBFNKHK6wwMkW5kgaqZfKJa=rW._5F9VvEdMWJR75A@mail.gmail.com). - -There is also a reasonable chance that QEMU might not reliably call GTK+ functions from the main thread (thread 0), which causes problems when GTK then calls through to the native Cocoa APIs which must be called from thread 0. -- cgit 1.4.1