Properly handle destroying a Keyboard resource
Summary: On client side the newer wl_keyboard_release is used which is a destructor call. On server side the shared destroy callback is used and it's ensured that KWayland doesn't crash if called into the KeyboardInterface between unbound and destroyed. Test Plan: Test case extended to cover the condition of an unbound KeyboardInterface. Reviewers: #plasma_on_wayland Subscribers: plasma-devel Tags: #plasma_on_wayland Differential Revision: https://phabricator.kde.org/D2036
parent
34df9d8b
Please register or sign in to comment