diff options
| author | Isaac Freund <mail@isaacfreund.com> | 2022-08-25 17:30:34 +0200 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2022-09-26 17:14:43 +0000 |
| commit | b784987ae82128acf1b75b3a8bce043b7b9527fe (patch) | |
| tree | b8f7b60a6c6ca69c638ca75ad2579167dd5dfcdd | |
| parent | 53cd10ae7792d2b465e6687a4b3e7f2a65a08c30 (diff) | |
| download | wayland-protocols-b784987ae82128acf1b75b3a8bce043b7b9527fe.tar.gz | |
ext-session-lock: add note on client termination
See https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/262
Signed-off-by: Isaac Freund <mail@isaacfreund.com>
| -rw-r--r-- | staging/ext-session-lock/ext-session-lock-v1.xml | 8 |
1 files changed, 8 insertions, 0 deletions
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. </description> </request> </interface> |