A GTK patch for one confirmed producer of these future timestamps is available:
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/10132 The underlying GTK issue is: https://gitlab.gnome.org/GNOME/gtk/-/work_items/8307 `GdkDragClass.drop_performed` expects a timestamp argument, while the corresponding drop-performed signal is declared and emitted with zero parameters. On X11, the handler therefore reads an indeterminate value and sends it as the `XdndDrop` timestamp. Can be produced by e.g. Nautilus. GTK MR 10132 corrects the handler signatures and preserves the actual button-event timestamp for X11. This should prevent GTK 4 drag-and-drop from generating this particular poisoned timestamp. It does not eliminate the need for Mutter to reject future `_NET_ACTIVE_WINDOW` timestamps, since any X11 client could still send one and trigger the active-window/input-focus desynchronization. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2107678 Title: Wrong keyboard focus after switching window in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2107678/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
