Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package wayland-protocols for
openSUSE:Factory checked in at 2026-11-01 22:22:51
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/wayland-protocols (Old)
and /work/SRC/openSUSE:Factory/.wayland-protocols.new.1255 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "wayland-protocols"
Sun Nov 1 22:22:51 2026 rev:51 rq:1393870 version:1.50
Changes:
--------
--- /work/SRC/openSUSE:Factory/wayland-protocols/wayland-protocols.changes
2026-06-09 14:21:25.311365460 +0200
+++
/work/SRC/openSUSE:Factory/.wayland-protocols.new.1255/wayland-protocols.changes
2026-11-01 22:23:31.810274624 +0100
@@ -1,0 +2,18 @@
+Fri Oct 30 05:08:48 UTC 2026 - Bjørn Lie <[email protected]>
+
+- Update to version 1.50:
+ * stable/linux-dmabuf: Spell out rules around format_table events
+ * xx-zones: Clarify that the the item position always includes
+ its frame
+ * xx-hotkey-v1: global hotkey protocol
+ * xx-image-capture-color-management-v1: new protocol
+ * staging/color-management: fix a link to the book
+ * presentation-time: add flags to differentiate variable and
+ fixed refresh rates
+ * meson: Don't build enum headers in strict mode
+- Drop conditional gcc11 and gcc11-c++ BuildRequires: No longer
+ applies for any current supported version of openSUSE.
+- Replace keyring with Daniel Stone key from
+ https://gitlab.freedesktop.org/daniels.gpg
+
+-------------------------------------------------------------------
Old:
----
wayland-protocols-1.49.tar.xz
wayland-protocols-1.49.tar.xz.sig
New:
----
wayland-protocols-1.50.tar.xz
wayland-protocols-1.50.tar.xz.sig
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ wayland-protocols.spec ++++++
--- /var/tmp/diff_new_pack.56humR/_old 2026-11-01 22:23:32.785315021 +0100
+++ /var/tmp/diff_new_pack.56humR/_new 2026-11-01 22:23:32.787315104 +0100
@@ -18,7 +18,7 @@
Name: wayland-protocols
-Version: 1.49
+Version: 1.50
Release: 0
Summary: Wayland protocols that add functionality not available in the
core protocol
License: MIT
@@ -27,13 +27,9 @@
Source:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/%{version}/downloads/%{name}-%{version}.tar.xz
Source2:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/%{version}/downloads/%{name}-%{version}.tar.xz.sig
Source3: %{name}.keyring
-%if 0%{?suse_version} > 1500
+
BuildRequires: c++_compiler
BuildRequires: c_compiler
-%else
-BuildRequires: gcc11
-BuildRequires: gcc11-c++
-%endif
BuildRequires: meson >= 0.55.0
BuildRequires: pkgconfig
BuildRequires: python3-base
@@ -62,18 +58,10 @@
%autosetup -p1
%build
-%if 0%{?suse_version} <= 1500
-export CC=gcc-11
-export CXX=gcc-11
-%endif
%meson
%meson_build
%install
-%if 0%{?suse_version} <= 1500
-export CC=gcc-11
-export CXX=gcc-11
-%endif
%meson_install
%check
++++++ wayland-protocols-1.49.tar.xz -> wayland-protocols-1.50.tar.xz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.49/GOVERNANCE.md
new/wayland-protocols-1.50/GOVERNANCE.md
--- old/wayland-protocols-1.49/GOVERNANCE.md 2026-06-07 15:06:32.000000000
+0200
+++ new/wayland-protocols-1.50/GOVERNANCE.md 2026-10-29 16:58:31.000000000
+0100
@@ -171,7 +171,7 @@
inactivity by its author, as determined by all of the following being true:
* No changes have been made to the protocol by the author
* No comments have been made to the protocol merge request by the author
- * No mails have been sent to the mailing list persuant to the protocol by
the author
+ * No mails have been sent to the mailing list pursuant to the protocol by
the author
2. A notification of intent to remove shall be given to the author in the
protocol
merge request, and the protocol shall only be removed following a one week
grace period
of continued inactivity.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-cutouts/xx-cutouts-v1.xml
new/wayland-protocols-1.50/experimental/xx-cutouts/xx-cutouts-v1.xml
--- old/wayland-protocols-1.49/experimental/xx-cutouts/xx-cutouts-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/experimental/xx-cutouts/xx-cutouts-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -103,7 +103,7 @@
the same element in different configure sequences.
Typically compositors would only send cutout information when
- the toplevel enters fullscreen or maxmized state (as specified
+ the toplevel enters fullscreen or maximized state (as specified
in the xdg_shell protocol).
The xx_cutouts_v1 object must be destroyed before its
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.49/experimental/xx-hotkey/README
new/wayland-protocols-1.50/experimental/xx-hotkey/README
--- old/wayland-protocols-1.49/experimental/xx-hotkey/README 1970-01-01
01:00:00.000000000 +0100
+++ new/wayland-protocols-1.50/experimental/xx-hotkey/README 2026-10-29
16:58:31.000000000 +0100
@@ -0,0 +1,4 @@
+Global hotkey protocol
+
+Maintainers:
+Aurelien Brabant <[email protected]>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-hotkey/xx-hotkey-v1.xml
new/wayland-protocols-1.50/experimental/xx-hotkey/xx-hotkey-v1.xml
--- old/wayland-protocols-1.49/experimental/xx-hotkey/xx-hotkey-v1.xml
1970-01-01 01:00:00.000000000 +0100
+++ new/wayland-protocols-1.50/experimental/xx-hotkey/xx-hotkey-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -0,0 +1,361 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="xx_hotkey_v1">
+ <copyright>
+ Copyright © 2026 Aurelien Brabant
+
+ Permission is hereby granted, free of charge, to any person obtaining a
+ copy of this software and associated documentation files (the "Software"),
+ to deal in the Software without restriction, including without limitation
+ the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ and/or sell copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following conditions:
+
+ The above copyright notice and this permission notice (including the next
+ paragraph) shall be included in all copies or substantial portions of the
+ Software.
+
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+ THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.
+ </copyright>
+
+ <description summary="client-managed global hotkeys">
+ This protocol lets a client bind, and freely reconfigure, its own global
+ hotkeys: it describes a trigger and the compositor accepts it or rejects it
+ with a reason. A hotkey fires regardless of which surface holds keyboard
+ focus. The compositor remains the arbiter and may deny a commit or revoke a
+ binding at any time, but the client chooses the trigger.
+
+ The key words "must", "must not", "required", "shall", "shall not",
+ "should", "should not", "recommended", "may", and "optional" in this
+ document are to be interpreted as described in IETF RFC 2119.
+
+ A bound hotkey always has exactly the trigger the client committed; the
+ compositor never substitutes one of its own.
+
+ A binding lives only as long as its xx_hotkey_v1 object and the client
+ connection; nothing is persisted by the protocol.
+
+ Whether a trigger is exclusive is compositor policy. A compositor may treat
+ triggers as exclusive and reject a clashing commit with "already_bound", or
+ may grant the same trigger to several bindings, in which case each bound
+ hotkey receives the events. Clients must cope with either.
+
+ Security considerations:
+
+ A global hotkey lets an unfocused client observe that a specific trigger
+ fired. Compositors are the security boundary and should apply policy when
+ deciding whether to accept a commit. As a default, we suggest the following
+ pseudo-code. This is not a wire requirement: every compositor is free to
apply
+ a different policy and can expose settings to allow the user to configure
it.
+
+ fn acceptable(trigger) {
+ if trigger.modifiers contains any of {ctrl, alt, super}:
+ return true # modified triggers are always acceptable
+ match trigger:
+ button(code):
+ return code is an auxiliary button
+ # side, extra, forward, back, task
+ key(keysym):
+ if keysym is a modifier keysym:
+ return true # a lone modifier, see set_key_trigger
+ if keysym is a keypad key:
+ return true # commonly a dedicated macro cluster
+ if keysym is a dead key:
+ return false # no character mapping, but composes text
+ if keysym has a character mapping:
+ return false # letters, digits, punctuation, space, Enter, Tab,
...
+ return true # purely functional: function, media, navigation keys
+ }
+
+ The protocol's one hard guarantee is containment: a compositor must not
+ deliver events for a trigger the client did not successfully bind, and
never
+ forwards the raw input stream.
+
+ Warning! The protocol described in this file is currently in the
+ experimental phase. Backwards incompatible major versions of the protocol
+ are to be expected. Exposing this protocol without an opt-in mechanism is
+ discouraged.
+ </description>
+
+ <interface name="xx_hotkey_manager_v1" version="1">
+ <description summary="global hotkey factory">
+ Identifies the application and creates global hotkeys.
+ </description>
+
+ <enum name="error">
+ <description summary="illegal request sequences">
+ Fatal protocol errors.
+ </description>
+ <entry name="invalid_app_id" value="0"
+ summary="the app id was empty, set more than once, or set after a
hotkey was committed"/>
+ </enum>
+
+ <enum name="modifiers" bitfield="true">
+ <description summary="modifier keys required by a trigger">
+ A bitmask of the modifiers that must be held for the trigger to fire.
+ The match is exact: a trigger does not fire while a modifier outside
+ its mask is held, so Super+Space does not fire on Super+Shift+Space.
+ Bits outside this enum raise the "invalid_trigger" error.
+
+ These are fixed, keymap-independent semantic bits. A compositor matches
+ each bit against the corresponding modifier in its keyboard state as
the
+ keymap defines it; for the xkb_v1 keymap format that is shift ->
+ XKB_MOD_NAME_SHIFT, ctrl -> XKB_MOD_NAME_CTRL, alt -> XKB_MOD_NAME_ALT
+ ("Mod1"), super -> XKB_MOD_NAME_LOGO ("Mod4").
+
+ A client needs neither a wl_keyboard nor a keymap to describe a
trigger.
+
+ Lock modifiers (Caps Lock, Num Lock, Scroll Lock) are never part of a
+ binding and are ignored when matching.
+ </description>
+ <entry name="shift" value="1" summary="the Shift modifier"/>
+ <entry name="ctrl" value="2" summary="the Control modifier"/>
+ <entry name="alt" value="4" summary="the Alt modifier"/>
+ <entry name="super" value="8" summary="the Super/Logo modifier"/>
+ </enum>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the manager">
+ Destroy the manager object. Hotkey objects created through this manager
+ are unaffected and remain valid.
+ </description>
+ </request>
+
+ <request name="set_app_id">
+ <description summary="set the application identifier">
+ Identify the application, for use in compositor policy and user-facing
+ audit interfaces. It applies to every hotkey created by this manager.
+
+ Optional; if sent, it must not be empty, must be sent at most once, and
+ must be sent before the first commit, so that every policy decision
+ sees the same identity.
+
+ Where the application has a desktop entry, app_id should be its desktop
+ file ID as defined by the freedesktop.org Desktop Entry specification,
+ matching the convention used by xdg_toplevel.set_app_id.
+
+ It is advisory and may be spoofed; a compositor that needs a
trustworthy
+ identity should obtain it through the security-context mechanism.
+ </description>
+ <arg name="app_id" type="string"
+ summary="advisory application identifier (should be the desktop
file ID)"/>
+ </request>
+
+ <request name="create_hotkey">
+ <description summary="create a hotkey">
+ Create a new hotkey object. No binding exists and no input events are
+ sent before the first successful commit.
+ </description>
+ <arg name="id" type="new_id" interface="xx_hotkey_v1"
+ summary="the new hotkey object"/>
+ </request>
+ </interface>
+
+ <interface name="xx_hotkey_v1" version="1">
+ <description summary="a single global hotkey">
+ Represents one global hotkey. The object is built up with set_* requests
+ and applied with commit; a trigger is required, everything else is
+ optional. Requests have no effect on the binding until commit is sent.
+
+ Exactly one "bound" or "denied" event is sent per commit, in the order
the
+ commits were issued. While the hotkey is bound, "triggered" and
"released"
+ are sent as the trigger is activated. The compositor may send "revoked"
at
+ any time to withdraw the binding.
+ </description>
+
+ <enum name="error">
+ <description summary="illegal request sequences">
+ Fatal protocol errors. A trigger that is merely unacceptable to the
+ compositor is reported through "denied" and is not an error.
+ </description>
+ <entry name="invalid_trigger" value="0"
+ summary="a null keysym, or unknown modifier bits"/>
+ <entry name="no_trigger" value="1"
+ summary="commit was sent before any trigger was described"/>
+ </enum>
+
+ <enum name="deny_reason">
+ <description summary="why a commit was rejected">
+ A reason code describing why the commit got denied. The object remains
+ valid, any previously established binding is unaffected, and the client
+ may describe a different trigger and commit again.
+
+ A compositor is not obliged to distinguish "already_bound" from
+ "not_permitted" and may report the latter for both.
+ </description>
+ <entry name="already_bound" value="0"
+ summary="held by another hotkey the compositor treats as
exclusive"/>
+ <entry name="not_permitted" value="1"
+ summary="the trigger is disallowed by compositor policy"/>
+ </enum>
+
+ <request name="destroy" type="destructor">
+ <description summary="release the hotkey">
+ Release the binding and destroy the object.
+ Destroying the object with a commit still in flight cancels it.
+ </description>
+ </request>
+
+ <request name="set_description">
+ <description summary="set the human-readable description">
+ Set a human-readable, localized description of what the hotkey does
+ (e.g. "Toggle the launcher"), for display in compositor user interface.
+ Optional.
+ </description>
+ <arg name="description" type="string" summary="localized action
description"/>
+ </request>
+
+ <request name="set_seat">
+ <description summary="restrict the hotkey to one seat">
+ Restrict the hotkey to the given seat, or pass null for all of the
+ client's seats, virtual ones included. Optional; the default is null.
+ If the given seat is removed, the compositor sends "revoked".
+ </description>
+ <arg name="seat" type="object" interface="wl_seat" allow-null="true"
+ summary="target seat, or null for all of the client's seats"/>
+ </request>
+
+ <request name="set_key_trigger">
+ <description summary="trigger on a key">
+ Describe the trigger as a key pressed while the given modifiers are
+ held. Replaces any trigger previously described. Takes effect on the
+ next commit.
+
+ The keysym uses the numbering shared with the keymap delivered over
+ wl_keyboard (for the xkb_v1 keymap format, an XKB_KEY_* value), in its
+ unshifted form (XKB_KEY_b, not XKB_KEY_B). The compositor matches it
+ against the keysym each key produces at its first shift level in any of
+ the user's layout groups, ignoring the effect Shift has on the key, so
+ that Shift is handled through the modifier mask like every other
+ modifier and a binding keeps firing after a layout group switch. A
+ binding whose keysym no group of the current keymap produces stays
+ bound and simply does not fire until the keymap changes again.
+
+ The trigger fires on key press; the compositor does not wait to see
+ whether another key follows. The press and the matching release are
+ consumed and must not be delivered to the focused surface.
+
+ The keysym may be one that contributes to modifier state, such as
+ XKB_KEY_Super_L; whether it does is decided by the seat's keymap. Such
a
+ trigger is a tap: it fires when the key is released, and only if no
+ other key, button or axis event occurred while it was held. A
+ compositor may additionally require that it was held no longer than
+ some interval. The modifier mask is evaluated as the state before the
+ key was pressed, so a lone left Super key is (XKB_KEY_Super_L, 0) and
+ (XKB_KEY_Shift_L, ctrl) is a tap on Shift while Control is held.
+
+ A tap is never consumed: the key must still update modifier state and
+ reach the focused surface, so binding it does not stop it composing
+ other shortcuts. "triggered" and "released" are sent together on
+ release, so a tap cannot drive press-and-hold.
+
+ A null keysym raises the "invalid_trigger" error.
+ </description>
+ <arg name="keysym" type="uint" summary="keysym of the trigger key"/>
+ <arg name="modifiers" type="uint" enum="xx_hotkey_manager_v1.modifiers"
+ summary="bitmask of required modifiers"/>
+ </request>
+
+ <request name="set_button_trigger">
+ <description summary="trigger on a pointer button">
+ Describe the trigger as a pointer button pressed while the given
+ modifiers are held. Replaces any trigger previously described. Takes
+ effect on the next commit.
+
+ The button is a button code in the same space as wl_pointer.button.
+
+ The press and the matching release are consumed and must not be
+ delivered to the surface under the pointer.
+ </description>
+ <arg name="button" type="uint" summary="button code, as in
wl_pointer.button"/>
+ <arg name="modifiers" type="uint" enum="xx_hotkey_manager_v1.modifiers"
+ summary="bitmask of required modifiers"/>
+ </request>
+
+ <request name="commit">
+ <description summary="apply the hotkey">
+ Apply the state built up on this object. The compositor replies with
+ exactly one "bound" or "denied" event per commit, in order.
+
+ Sending commit before a trigger has been described raises the
+ "no_trigger" error.
+
+ Commit may be sent again to apply a changed trigger, description or
+ seat, keeping the binding's identity. Values set with set_* requests
are
+ retained across commits, accepted or denied, and each commit applies
+ all of them; committing with nothing changed is accepted with "bound".
+ An established binding survives a rejected commit: the previous state
+ stays active, so a denied reconfiguration never leaves the user with no
+ hotkey.
+ </description>
+ </request>
+
+ <event name="bound">
+ <description summary="the hotkey is now active">
+ The commit was accepted and the binding is active with the trigger that
+ was committed. "triggered" and "released" events may follow.
+ </description>
+ </event>
+
+ <event name="denied">
+ <description summary="the commit was rejected">
+ The committed trigger was not bound. Any previously established binding
+ remains active with its previous trigger.
+
+ message is an optional, advisory, human-readable explanation in the
+ compositor's locale, intended for verbatim display. It may be empty.
+ Clients must not parse it; all programmatic behavior keys off reason.
+ </description>
+ <arg name="reason" type="uint" enum="deny_reason" summary="why it was
rejected"/>
+ <arg name="message" type="string"
+ summary="optional human-readable detail for display (may be
empty)"/>
+ </event>
+
+ <event name="revoked">
+ <description summary="a previously active hotkey was withdrawn">
+ A binding that was previously "bound" is no longer active. No further
+ input events will be sent for it. The client should destroy this object
+ and must not silently commit the same trigger again; whether to retry
+ is the user's decision.
+
+ message has the same meaning as in the "denied" event.
+ </description>
+ <arg name="message" type="string"
+ summary="optional human-readable detail for display (may be
empty)"/>
+ </event>
+
+ <event name="triggered">
+ <description summary="the hotkey fired">
+ The bound trigger fired. This event is sent once each time it fires;
the
+ compositor does not auto-repeat the hotkey.
+
+ serial is an input serial that counts as a recent user interaction. A
+ client may pass it to xdg_activation_token_v1.set_serial to raise or
+ focus a surface, and a compositor should honor activation carried by
it.
+
+ time is the event timestamp, on the same millisecond clock as
+ wl_pointer and wl_keyboard input events.
+ </description>
+ <arg name="serial" type="uint" summary="input serial for the
activation"/>
+ <arg name="time" type="uint" summary="timestamp in milliseconds"/>
+ </event>
+
+ <event name="released">
+ <description summary="the hotkey was released">
+ The key or button of a previously triggered hotkey was released,
+ regardless of modifier state. This enables press-and-hold uses such as
+ push-to-talk; clients that only act on the initial firing may ignore
+ it.
+
+ serial and time have the same meaning as in the "triggered" event.
+ </description>
+ <arg name="serial" type="uint" summary="input serial for the
activation"/>
+ <arg name="time" type="uint" summary="timestamp in milliseconds"/>
+ </event>
+ </interface>
+</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-image-capture-color-management/README
new/wayland-protocols-1.50/experimental/xx-image-capture-color-management/README
---
old/wayland-protocols-1.49/experimental/xx-image-capture-color-management/README
1970-01-01 01:00:00.000000000 +0100
+++
new/wayland-protocols-1.50/experimental/xx-image-capture-color-management/README
2026-10-29 16:58:31.000000000 +0100
@@ -0,0 +1,4 @@
+Image Copy Capture Color Management protocol
+
+Maintainers:
+Julian Orth <[email protected]> (@mahkoh)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-image-capture-color-management/xx-image-capture-color-management-v1.xml
new/wayland-protocols-1.50/experimental/xx-image-capture-color-management/xx-image-capture-color-management-v1.xml
---
old/wayland-protocols-1.49/experimental/xx-image-capture-color-management/xx-image-capture-color-management-v1.xml
1970-01-01 01:00:00.000000000 +0100
+++
new/wayland-protocols-1.50/experimental/xx-image-capture-color-management/xx-image-capture-color-management-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -0,0 +1,155 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="xx_image_capture_color_management_v1">
+ <copyright>
+ Copyright © 2025-2026 Julian Orth
+
+ Permission is hereby granted, free of charge, to any person obtaining a
+ copy of this software and associated documentation files (the "Software"),
+ to deal in the Software without restriction, including without limitation
+ the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ and/or sell copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following conditions:
+
+ The above copyright notice and this permission notice (including the next
+ paragraph) shall be included in all copies or substantial portions of the
+ Software.
+
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+ THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.
+ </copyright>
+
+ <description summary="image-copy-capture extension to support color
management">
+ This protocol provides extensions to the ext-image-capture-source-v1 and
+ ext-image-copy-capture-v1 protocols to allow clients to capture frames in
+ color spaces other than srgb/gamma22.
+
+ Warning! The protocol described in this file is currently in the
+ experimental phase. Backwards incompatible major versions of the
+ protocol are to be expected. Exposing this protocol without an opt-in
+ mechanism is discouraged.
+ </description>
+
+ <interface name="xx_image_capture_color_manager_v1" version="1">
+ <description summary="global to add color-management support for image
captures">
+ This global allows clients to retrieve information about the preferred
+ image description of a capture source and to define the image description
+ of a capture frame.
+ </description>
+
+ <enum name="error">
+ <entry name="image_description_not_ready" value="1" summary="the image
description is not ready"/>
+ <entry name="already_captured" value="2" summary="capture request has
been sent"/>
+ </enum>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy this object">
+ Destroys the object. This request can be sent at any time by the
+ client.
+ </description>
+ </request>
+
+ <request name="get_capture_source_colors">
+ <description summary="create a color management interface for an
ext_image_capture_source_v1">
+ This creates a new xx_image_capture_source_colors_v1 for a given
+ ext_image_capture_source_v1.
+
+ See xx_image_capture_source_colors_v1 for more details.
+ </description>
+ <arg name="colors" type="new_id"
interface="xx_image_capture_source_colors_v1"/>
+ <arg name="source" type="object"
interface="ext_image_capture_source_v1"/>
+ </request>
+
+ <request name="set_frame_image_description">
+ <description summary="set the image description of a frame">
+ If the frame is successfully captured, it will be encoded according to
+ this image description.
+
+ This request must not be used if the image description is not ready.
+ Otherwise the image_description_not_ready error is emitted.
+
+ This request must not be used if the frame has already been captured.
+ Otherwise the already_captured error is emitted.
+ </description>
+ <arg name="frame" type="object"
interface="ext_image_copy_capture_frame_v1"/>
+ <arg name="image_description" type="object"
interface="wp_image_description_v1"/>
+ </request>
+ </interface>
+
+ <interface name="xx_image_capture_source_colors_v1" version="1">
+ <description summary="capture source color properties">
+ This object describes the color properties of a capture source.
+
+ The xx_image_capture_source_colors_v1 is associated with the compositor
+ object backing the source. Therefore the client destroying the
+ ext_image_capture_source_v1 object has no impact. The object becomes
inert
+ when the compositor object backing the source is destroyed. How the
client
+ can detect this depends on the source.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroys this object">
+ Destroys this object.
+ </description>
+ </request>
+
+ <request name="get_preferred">
+ <description summary="retrieve the preferred description">
+ The preferred image description represents the compositor's preferred
+ color encoding for this capture source at the current time. There might
+ be performance and power advantages, as well as improved color
+ reproduction, if the image description of a capture frame matches the
+ preferred image description.
+
+ This creates a new wp_image_description_reference_v1 object for the
+ currently preferred image description for the capture source. The
client
+ should stop using and destroy the image descriptions created by earlier
+ invocations of this request for the associated capture source. This
+ request is usually sent as a reaction to the
+ xx_image_capture_source_colors_v1.preferred_changed event or when
+ creating a xx_image_capture_source_colors_v1 object if the client is
+ capable of adapting to image descriptions.
+
+ The created wp_image_description_reference_v1 object preserves the
+ preferred image description of the capture source from the time the
+ object was created.
+
+ The resulting image description object allows the
+ wp_image_description_v1.get_information request.
+ </description>
+ <arg name="id" type="new_id"
interface="wp_image_description_reference_v1"
+ summary="the preferred description"/>
+ </request>
+
+ <event name="preferred_changed">
+ <description summary="the preferred image description changed">
+ The preferred image description is the one which likely has the most
+ performance and/or quality benefits for the compositor if used by the
+ client for its capture frames. This event is sent whenever
+ the compositor changes the capture source's preferred image
description.
+
+ This event sends the identity of the new preferred state as the
+ argument, so clients who are aware of the image description already can
+ reuse it. Otherwise, if the client wants to know what the preferred
+ image description is, it shall use the
+ xx_image_capture_source_colors_v1.get_preferred request.
+
+ The preferred image description is not automatically used for anything.
+ It is only a hint, and clients may set any valid image description with
+ xx_image_capture_color_manager_v1.set_frame_image_description, but
there
+ might be performance and color accuracy improvements by providing the
+ capture frame's contents in the preferred image description. Therefore
+ clients that can, should capture frames in the preferred image
+ description.
+ </description>
+ <arg name="identity_hi" type="uint"
+ summary="image description id number (high 32 bits)"/>
+ <arg name="identity_lo" type="uint"
+ summary="image description id number (low 32 bits)"/>
+ </event>
+ </interface>
+</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-input-method/xx-input-method-v2.xml
new/wayland-protocols-1.50/experimental/xx-input-method/xx-input-method-v2.xml
---
old/wayland-protocols-1.49/experimental/xx-input-method/xx-input-method-v2.xml
2026-06-07 15:06:32.000000000 +0200
+++
new/wayland-protocols-1.50/experimental/xx-input-method/xx-input-method-v2.xml
2026-10-29 16:58:31.000000000 +0100
@@ -228,7 +228,7 @@
The text input client now applies requested updates on a
"best-effort" basis.
</description>
</entry>
- <!-- This doesn't need disambiguating. Both protocols are pdated in
lockstep, and the compositor should implement both protocols to the current
version. By the experimental protocols contract, every version bump is breaking
compatibility. -->
+ <!-- This doesn't need disambiguating. Both protocols are updated in
lockstep, and the compositor should implement both protocols to the current
version. By the experimental protocols contract, every version bump is breaking
compatibility. -->
</enum>
<event name="announce_protocol_compat" since="3">
@@ -379,7 +379,7 @@
The cursor and anchor arguments can also take the following special
values:
BEGINNING := 0x8000_0000 = i32::MIN
END := 0x7fff_ffff = i32::MAX
- meaning, respectively, the beginning and the end of of all text in the
input field.
+ meaning, respectively, the beginning and the end of all text in the
input field.
Values set with this event are double-buffered. They must be applied
and reset to initial on the next commit request.
@@ -570,7 +570,7 @@
3. Simplify a lot and remove .configure in favor of relying on .done
entirely
- Rejected because it pulls in .ack_configure after every .done
regardless of surface status. Also underspecifed regarding which popup needs to
be configured.
+ Rejected because it pulls in .ack_configure after every .done
regardless of surface status. Also underspecified regarding which popup needs
to be configured.
-->
</description>
<arg name="width" type="uint" summary="popup width"/>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-session-management/xx-session-management-v1.xml
new/wayland-protocols-1.50/experimental/xx-session-management/xx-session-management-v1.xml
---
old/wayland-protocols-1.49/experimental/xx-session-management/xx-session-management-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++
new/wayland-protocols-1.50/experimental/xx-session-management/xx-session-management-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -110,7 +110,7 @@
use".
If a identifier string represents a session that is currently actively
- in use by the the same client, an 'in_use' error is raised. If some
+ in use by the same client, an 'in_use' error is raised. If some
other client is currently using the same session, the new session will
replace managing the associated state.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-text-input/xx-text-input-v3.xml
new/wayland-protocols-1.50/experimental/xx-text-input/xx-text-input-v3.xml
--- old/wayland-protocols-1.49/experimental/xx-text-input/xx-text-input-v3.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/experimental/xx-text-input/xx-text-input-v3.xml
2026-10-29 16:58:31.000000000 +0100
@@ -171,7 +171,7 @@
<enum name="change_cause">
<description summary="text change reason">
- Reason for the change of surrounding text or cursor posision.
+ Reason for the change of surrounding text or cursor position.
</description>
<entry name="input_method" value="0" summary="input method caused the
change"/>
<entry name="other" value="1" summary="something else than the input
method caused the change"/>
@@ -182,7 +182,7 @@
Tells the compositor why the text surrounding the cursor changed.
Whenever the client detects an external change in text, cursor, or
- anchor posision, it must issue this request to the compositor. This
+ anchor position, it must issue this request to the compositor. This
request is intended to give the input method a chance to update the
preedit text in an appropriate way, e.g. by removing it when the user
starts typing with a keyboard.
@@ -434,7 +434,7 @@
The cursor and anchor arguments can also take the following special
values:
BEGINNING := 0x8000_0000 = i32::MIN
END := 0x7fff_ffff = i32::MAX
- meaning, respectively, the beginning and the end of of all text in the
input field.
+ meaning, respectively, the beginning and the end of all text in the
input field.
Values set with this event are double-buffered. They must be applied
and reset to initial on the next commit request.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/experimental/xx-zones/xx-zones-v1.xml
new/wayland-protocols-1.50/experimental/xx-zones/xx-zones-v1.xml
--- old/wayland-protocols-1.49/experimental/xx-zones/xx-zones-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/experimental/xx-zones/xx-zones-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -136,6 +136,13 @@
a toplevel).
When the reference is destroyed, the compositor must send a 'closed'
event and the zone item becomes inert.
+
+ All item coordinates used by this interface refer to the top-left
+ corner of the item's frame, that is the item surface extended by the
+ extents reported in the 'frame_extents' event. If the item has no
+ frame, they refer to the top-left corner of the item surface. To
+ obtain the position of the surface content, a client adds the left
+ and top frame extents to the item position.
</description>
<request name="destroy" type="destructor">
@@ -180,9 +187,9 @@
</event>
<request name="set_position">
- <description summary="set a preferred item surface position">
- Request a preferred position (x, y) for the specified item
- surface to be placed at, relative to its associated zone.
+ <description summary="set a preferred item position">
+ Request a preferred position (x, y) for the frame of the specified
+ item to be placed at, relative to its associated zone.
This state is double-buffered and is applied on the next
wl_surface.commit of the surface represented by 'item'.
@@ -215,11 +222,15 @@
surface (e.g. clicking & dragging within the window, or resizing
it).
After a call to this request, a 'position' event must be emitted with
the
- item's new actual position.
+ item's new actual position, once the request has been applied. If the
+ item already is at the requested (or sanitized) position, the request
+ is considered successful and a 'position' event must still be emitted.
If the current item has no zone associated with it, a 'position_failed'
- event must be emitted.
- If the compositor did not move the item at all, not even with sanitized
- values, a 'position_failed' event must be emitted as well.
+ event must be emitted instead.
+ If the compositor refused to move the item at all, not even to
sanitized
+ coordinates (e.g. because compositor policy does not allow the item to
+ be moved in its current state), a 'position_failed' event must be
+ emitted as well.
</description>
<arg name="x" type="int" summary="x position relative to zone"/>
<arg name="y" type="int" summary="y position relative to zone"/>
@@ -228,7 +239,7 @@
<event name="position">
<description summary="notify about the position of an item">
This event notifies the client of the current position (x, y) of
- the item relative to its zone.
+ the item's frame relative to its zone.
Coordinates are relative to the zone this item belongs to, and only
valid within it.
Negative coordinates are possible, if the user has moved an item
@@ -247,9 +258,9 @@
<event name="position_failed">
<description summary="a set_position request has failed">
- The compositor was unable to set the position of this item entirely,
- and could not even find sanitized coordinates to place the item at
- instead.
+ The compositor did not apply a 'set_position' request at all, not
+ even with sanitized coordinates, and the item remains at its previous
+ position.
This event will also be emitted if 'set_position' was called while the
item had no zone associated with it.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/include/wayland-protocols/meson.build
new/wayland-protocols-1.50/include/wayland-protocols/meson.build
--- old/wayland-protocols-1.49/include/wayland-protocols/meson.build
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/include/wayland-protocols/meson.build
2026-10-29 16:58:31.000000000 +0100
@@ -7,7 +7,6 @@
input: '../..' / protocol_file,
command: [
prog_scanner,
- '--strict',
'enum-header',
'@INPUT@',
'@OUTPUT@',
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.49/meson.build
new/wayland-protocols-1.50/meson.build
--- old/wayland-protocols-1.49/meson.build 2026-06-07 15:06:32.000000000
+0200
+++ new/wayland-protocols-1.50/meson.build 2026-10-29 16:58:31.000000000
+0100
@@ -1,5 +1,5 @@
project('wayland-protocols',
- version: '1.49',
+ version: '1.50',
meson_version: '>= 0.58.0',
license: 'MIT/Expat',
)
@@ -88,6 +88,13 @@
experimental_protocols = {
'xx-cutouts': {'v1': []},
+ 'xx-hotkey': {'v1': []},
+ 'xx-image-capture-color-management': {'v1': [
+ 'staging/color-management/color-management-v1.xml',
+
'staging/ext-image-capture-source/ext-image-capture-source-v1.xml',
+ 'staging/ext-image-copy-capture/ext-image-copy-capture-v1.xml',
+
'staging/ext-foreign-toplevel-list/ext-foreign-toplevel-list-v1.xml',
+ ]},
'xx-input-method': {'v2': []},
'xx-keyboard-filter': {'v1': [
'experimental/xx-input-method/xx-input-method-v2.xml',
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/stable/linux-dmabuf/feedback.rst
new/wayland-protocols-1.50/stable/linux-dmabuf/feedback.rst
--- old/wayland-protocols-1.49/stable/linux-dmabuf/feedback.rst 2026-06-07
15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/stable/linux-dmabuf/feedback.rst 2026-10-29
16:58:31.000000000 +0100
@@ -97,6 +97,11 @@
should detect when the optimal allocation parameters didn't change (same
device/format/modifier/flags) to avoid needlessly re-allocating their buffers.
+Note that the compositor is free not to re-send the ``format_table`` event for
a
+given surface feedback object if the table contents haven't changed since last
+time. The client needs to keep around the last format table until it destroys
+the surface feedback object.
+
For compositors
---------------
@@ -108,6 +113,10 @@
format/modifier pairs supported by the rendering API. Do not set the
``scanout`` flag in the ``tranche_flags`` event.
+In the following advanced cases, the compositor is free not to re-send the
+``format_table`` event for a given surface feedback object if the table
contents
+haven't changed since last time.
+
Some compositors may support direct scan-out for full-screen surfaces. These
compositors can re-send the feedback parameters when a surface becomes
full-screen or leaves full-screen mode if the client has used the
@@ -164,7 +173,7 @@
compositor could insert an intermediate tranche if it's possible to use a
mem2mem device to convert buffers to be able to use scan-out.
-linux-dmabuf feedback implementation nodes for version 6
+linux-dmabuf feedback implementation notes for version 6
==========================================
With version 6 of the protocol, most of the logic described for version 4 still
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/stable/linux-dmabuf/linux-dmabuf-v1.xml
new/wayland-protocols-1.50/stable/linux-dmabuf/linux-dmabuf-v1.xml
--- old/wayland-protocols-1.49/stable/linux-dmabuf/linux-dmabuf-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/stable/linux-dmabuf/linux-dmabuf-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -348,7 +348,7 @@
zwp_linux_buffer_params_v1 object.
</description>
<arg name="buffer" type="new_id" interface="wl_buffer"
- summary="id for the the newly created wl_buffer"/>
+ summary="id for the newly created wl_buffer"/>
</event>
<event name="failed">
@@ -447,6 +447,11 @@
With version 6 and above, the compositor must always advertise at least
one tranche with the sampling flag set.
+
+ The compositor sends a format_table event at least once for each dmabuf
+ parameters feedback object, before any tranche events. Unless the format
+ table contents change later, the compositor is free not to send another
+ format_table event for the same dmabuf parameters feedback object.
</description>
<request name="destroy" type="destructor">
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/stable/presentation-time/presentation-time.xml
new/wayland-protocols-1.50/stable/presentation-time/presentation-time.xml
--- old/wayland-protocols-1.49/stable/presentation-time/presentation-time.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/stable/presentation-time/presentation-time.xml
2026-10-29 16:58:31.000000000 +0100
@@ -25,7 +25,7 @@
DEALINGS IN THE SOFTWARE.
</copyright>
- <interface name="wp_presentation" version="2">
+ <interface name="wp_presentation" version="3">
<description summary="timed presentation related wl_surface requests">
<!-- Introduction -->
@@ -123,7 +123,7 @@
</interface>
- <interface name="wp_presentation_feedback" version="2">
+ <interface name="wp_presentation_feedback" version="3">
<description summary="presentation time feedback event">
A presentation_feedback object returns an indication that a
wl_surface content update has become visible to the user.
@@ -195,6 +195,29 @@
fullscreen surface and a surface on a hardware overlay.
</description>
</entry>
+ <entry name="fixed_rate" value="0x10" since="3">
+ <description summary="presentation is at a fixed refresh rate">
+ The display hardware is operating at a fixed refresh rate.
+ The presentation was aligned to a multiple of this event's
+ 'refresh' argument.
+ If this is set, the refresh argument must not be 0.
+ </description>
+ </entry>
+ <entry name="variable_rate" value="0x20" since="3">
+ <description summary="presentation is at a variable refresh rate">
+ The display hardware is operating at a variable refresh rate, with
+ updates to this surface consistently determining the display refresh
+ timing. The definition of 'consistent' is compositor policy.
+
+ The content update was displayed as soon as possible after it became
+ ready, but no sooner than 'refresh' nanoseconds after the previous
+ presentation on this surface. In other words, the presentation time
+ was determined by when this surface's content became ready, not by
+ a periodic display refresh or by updates to other surfaces.
+
+ If this is set, the refresh argument must not be 0.
+ </description>
+ </entry>
</enum>
<event name="presented" type="destructor">
@@ -231,6 +254,11 @@
For version 1, if the output does not have a constant refresh rate,
the refresh argument must be zero.
+ If the 'fixed_rate' flag is set, then the refresh argument is
+ the output's constant refresh rate. If the 'variable_rate' flag
+ is set, then the refresh argument is the output's fastest refresh
+ rate.
+
The 64-bit value combined from seq_hi and seq_lo is the value
of the output's vertical retrace counter when the content
update was first scanned out to the display. This value must
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/stable/xdg-shell/xdg-shell.xml
new/wayland-protocols-1.50/stable/xdg-shell/xdg-shell.xml
--- old/wayland-protocols-1.49/stable/xdg-shell/xdg-shell.xml 2026-06-07
15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/stable/xdg-shell/xdg-shell.xml 2026-10-29
16:58:31.000000000 +0100
@@ -83,7 +83,7 @@
While xdg_surface itself is not a role, the corresponding surface may
only be assigned a role extending xdg_surface, such as xdg_toplevel or
xdg_popup. It is illegal to create an xdg_surface for a wl_surface which
- already has anassigned role and this will result in a role error.
+ already has an assigned role and this will result in a role error.
See the documentation of xdg_surface for more details about what an
xdg_surface is and how it is used.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/staging/color-management/color-management-v1.xml
new/wayland-protocols-1.50/staging/color-management/color-management-v1.xml
--- old/wayland-protocols-1.49/staging/color-management/color-management-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/staging/color-management/color-management-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -38,7 +38,7 @@
look like.
For an introduction, see the section "Color management" in the Wayland
- documentation at https://wayland.freedesktop.org/docs/html/ .
+ documentation at https://wayland.freedesktop.org/docs/book/ .
The color properties are represented as an image description object which
is immutable after it has been created. A wl_output always has an
@@ -849,7 +849,7 @@
wl_surface only if the image description is an exact match with the
client content. Particularly if everything else matches, but the target
color volume is greater than what the client needs, the client should
- create its own parameric image description with its exact parameters.
+ create its own parametric image description with its exact parameters.
If the interface version is inadequate for the preferred image
description, meaning that the client does not support all the
@@ -888,7 +888,7 @@
This event sends the identity of the new preferred state as the
argument,
so clients who are aware of the image description already can reuse it.
- Otherwise, if the client client wants to know what the preferred image
+ Otherwise, if the client wants to know what the preferred image
description is, it shall use the get_preferred request.
The preferred image description is not automatically used for anything.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/staging/color-representation/notes.rst
new/wayland-protocols-1.50/staging/color-representation/notes.rst
--- old/wayland-protocols-1.49/staging/color-representation/notes.rst
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/staging/color-representation/notes.rst
2026-10-29 16:58:31.000000000 +0100
@@ -58,7 +58,7 @@
(depending on the ``VideoFullRangeFlag``) to arrive at the YCbCr encoding. An
RGB encoding cannot be inferred from the applicable equations.
-Therefore code point 1 is is compatible only with pixel formats which contain
+Therefore code point 1 is compatible only with pixel formats which contain
the YCbCr color channels.
MatrixCoefficients usage
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/staging/fractional-scale/fractional-scale-v1.xml
new/wayland-protocols-1.50/staging/fractional-scale/fractional-scale-v1.xml
--- old/wayland-protocols-1.49/staging/fractional-scale/fractional-scale-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/staging/fractional-scale/fractional-scale-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -64,7 +64,7 @@
<request name="get_fractional_scale">
<description summary="extend surface interface for scale information">
- Create an add-on object for the the wl_surface to let the compositor
+ Create an add-on object for the wl_surface to let the compositor
request fractional scales. If the given wl_surface already has a
wp_fractional_scale_v1 object associated, the fractional_scale_exists
protocol error is raised.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/staging/xdg-session-management/xdg-session-management-v1.xml
new/wayland-protocols-1.50/staging/xdg-session-management/xdg-session-management-v1.xml
---
old/wayland-protocols-1.49/staging/xdg-session-management/xdg-session-management-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++
new/wayland-protocols-1.50/staging/xdg-session-management/xdg-session-management-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -123,7 +123,7 @@
use".
If an identifier string represents a session that is currently actively
- in use by the the same client, an 'in_use' error is raised. If some
+ in use by the same client, an 'in_use' error is raised. If some
other client is currently using the same session, the new session will
replace managing the associated state.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/wayland-protocols-1.49/tests/meson.build
new/wayland-protocols-1.50/tests/meson.build
--- old/wayland-protocols-1.49/tests/meson.build 2026-06-07
15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/tests/meson.build 2026-10-29
16:58:31.000000000 +0100
@@ -100,9 +100,14 @@
replace_command = protocol_replace_command[protocol_file]
dep_code = []
+ dep_args = []
if protocol_file in protocol_deps
foreach dep : protocol_deps[protocol_file]
dep_code += [protocol_code[dep]]
+ foreach dep_header : [protocol_client_header[dep],
protocol_server_header[dep]]
+ dep_code += [dep_header]
+ dep_args += ['-include', dep_header.full_path()]
+ endforeach
endforeach
endif
@@ -128,7 +133,7 @@
'-std=c99',
'-pedantic',
'-Wall',
- '-Werror' ],
+ '-Werror' ] + dep_args,
install: false,
)
test(test_name, pedantic_test_executable)
@@ -154,7 +159,7 @@
cpp_args: [
'-Wall',
'-Werror',
- ],
+ ] + dep_args,
install: false,
)
test(test_name, cxx_test_executable)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
new/wayland-protocols-1.50/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
---
old/wayland-protocols-1.49/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++
new/wayland-protocols-1.50/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -100,7 +100,7 @@
When the keyboard shortcuts inhibitor is inactive, the client has
no way to forcibly reactivate the keyboard shortcuts inhibitor.
- The user can chose to re-enable a previously deactivated keyboard
+ The user can choose to re-enable a previously deactivated keyboard
shortcuts inhibitor using any mechanism the compositor may offer,
in which case the compositor will send an "active" event to notify
the client.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml
new/wayland-protocols-1.50/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml
---
old/wayland-protocols-1.49/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml
2026-06-07 15:06:32.000000000 +0200
+++
new/wayland-protocols-1.50/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml
2026-10-29 16:58:31.000000000 +0100
@@ -132,7 +132,7 @@
The request creates a new object wp_locked_pointer which is used to
interact with the lock as well as receive updates about its state. See
- the the description of wp_locked_pointer for further information.
+ the description of wp_locked_pointer for further information.
Note that while a pointer is locked, the wl_pointer objects of the
corresponding seat will not emit any wl_pointer.motion events, but
@@ -167,7 +167,7 @@
The request will create a new object wp_confined_pointer which is used
to interact with the confinement as well as receive updates about its
- state. See the the description of wp_confined_pointer for further
+ state. See the description of wp_confined_pointer for further
information.
</description>
<arg name="id" type="new_id" interface="zwp_confined_pointer_v1"/>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/unstable/text-input/text-input-unstable-v3.xml
new/wayland-protocols-1.50/unstable/text-input/text-input-unstable-v3.xml
--- old/wayland-protocols-1.49/unstable/text-input/text-input-unstable-v3.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/unstable/text-input/text-input-unstable-v3.xml
2026-10-29 16:58:31.000000000 +0100
@@ -168,7 +168,7 @@
<enum name="change_cause">
<description summary="text change reason">
- Reason for the change of surrounding text or cursor posision.
+ Reason for the change of surrounding text or cursor position.
</description>
<entry name="input_method" value="0" summary="input method caused the
change"/>
<entry name="other" value="1" summary="something else than the input
method caused the change"/>
@@ -179,7 +179,7 @@
Tells the compositor why the text surrounding the cursor changed.
Whenever the client detects an external change in text, cursor, or
- anchor posision, it must issue this request to the compositor. This
+ anchor position, it must issue this request to the compositor. This
request is intended to give the input method a chance to update the
preedit text in an appropriate way, e.g. by removing it when the user
starts typing with a keyboard.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/wayland-protocols-1.49/unstable/xdg-shell/xdg-shell-unstable-v6.xml
new/wayland-protocols-1.50/unstable/xdg-shell/xdg-shell-unstable-v6.xml
--- old/wayland-protocols-1.49/unstable/xdg-shell/xdg-shell-unstable-v6.xml
2026-06-07 15:06:32.000000000 +0200
+++ new/wayland-protocols-1.50/unstable/xdg-shell/xdg-shell-unstable-v6.xml
2026-10-29 16:58:31.000000000 +0100
@@ -697,7 +697,7 @@
<entry name="maximized" value="1" summary="the surface is maximized">
<description summary="the surface is maximized">
The surface is maximized. The window geometry specified in the
configure
- event must be obeyed by the client. If the window geometry is not
obyed,
+ event must be obeyed by the client. If the window geometry is not
obeyed,
the zxdg_shell_v6.invalid_surface_state error is raised.
</description>
</entry>
++++++ wayland-protocols.keyring ++++++
Binary files /var/tmp/diff_new_pack.56humR/_old and
/var/tmp/diff_new_pack.56humR/_new differ
