[mutter] wayland/seat: Don't double-disable input classes



commit ed8275ec33e587c0adac0f9206cd67e1b3034615
Author: Jonas Ã…dahl <jadahl gmail com>
Date:   Thu Oct 13 11:56:06 2022 +0200

    wayland/seat: Don't double-disable input classes
    
    We'd set the capabilities to 'none', meaning all previously enabled
    device classes would be disabled. That means we shouldn't re-disable
    them directly after.
    
    This ensures '..disable()' is only called once for every '..enable()'.
    
    Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2657>

 src/wayland/meta-wayland-seat.c | 3 ---
 1 file changed, 3 deletions(-)
---
diff --git a/src/wayland/meta-wayland-seat.c b/src/wayland/meta-wayland-seat.c
index 80325ece10..4e09769207 100644
--- a/src/wayland/meta-wayland-seat.c
+++ b/src/wayland/meta-wayland-seat.c
@@ -255,11 +255,8 @@ meta_wayland_seat_free (MetaWaylandSeat *seat)
   g_signal_handlers_disconnect_by_data (clutter_seat, seat);
   meta_wayland_seat_set_capabilities (seat, 0);
 
-  meta_wayland_pointer_disable (seat->pointer);
   g_object_unref (seat->pointer);
-  meta_wayland_keyboard_disable (seat->keyboard);
   g_object_unref (seat->keyboard);
-  meta_wayland_touch_disable (seat->touch);
   g_object_unref (seat->touch);
 
   meta_wayland_text_input_destroy (seat->text_input);


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]