From b784987ae82128acf1b75b3a8bce043b7b9527fe Mon Sep 17 00:00:00 2001 From: Isaac Freund Date: Thu, 25 Aug 2022 17:30:34 +0200 Subject: ext-session-lock: add note on client termination See https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/262 Signed-off-by: Isaac Freund --- staging/ext-session-lock/ext-session-lock-v1.xml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/staging/ext-session-lock/ext-session-lock-v1.xml b/staging/ext-session-lock/ext-session-lock-v1.xml index 5b292cd..3339f4a 100644 --- a/staging/ext-session-lock/ext-session-lock-v1.xml +++ b/staging/ext-session-lock/ext-session-lock-v1.xml @@ -187,6 +187,14 @@ It is a protocol error to make this request if the locked event has not been sent. In that case, the lock object may only be destroyed using the destroy request. + + Note that a correct client that wishes to exit directly after unlocking + the session must use the wl_display.sync request to ensure the server + receives and processes the unlock_and_destroy request. Otherwise + there is no guarantee that the server has unlocked the session due + to the asynchronous nature of the Wayland protocol. For example, + the server might terminate the client with a protocol error before + it processes the unlock_and_destroy request. -- cgit v1.2.3