#16889 closed enhancement (fixed)
xorgproto-2022.2
| Reported by: | Douglas R. Reno | Owned by: | Bruce Dubbs |
|---|---|---|---|
| Priority: | normal | Milestone: | 11.2 |
| Component: | BOOK | Version: | git |
| Severity: | medium | Keywords: | |
| Cc: |
Description
New minor version
Change History (4)
comment:1 by , 4 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 4 years ago
comment:3 by , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed at commits
9a576963cf Update to gdk-pixbuf-2.42.9. 277c39037c Update to pango-1.50.9. db2e143aa3 Update to xorgproto-2022.2. 55bad52508 Update to gpgme-1.18.0. 00fa2231ac Update to boost-1.80.0.
comment:4 by , 4 years ago
Some more details from the mailing list announcement:
his release introduces an new "XWAYLAND" extension:
This extension exists to serve one purpose: reliably identifying
Xwayland. Previous attempts at doing so included querying root window
properties, output names or input device names. All these attempts are
somewhat unreliable. Instead, let's use an extension - where that
extension is present we have an Xwayland server.
Clients should never need to do anything but check whether the extension
exists through XQueryExtension/XListExtensions.
The DRI3 protocol was bumped to 1.3 and has a new DRI3SetDRMDeviceInUse request:
This request provides a hint to the server about the device
in use by this window. This is used to provide
DRI3GetSupportedModifiers with a hint of what device to
return modifiers for in the window_modifiers return value.
Using this hint allows for device-specific modifiers to
be returned by DRI3GetSupportedModifiers, for example
when an application is renderoffloaded and eligible for
direct scanout.
The remaining commits are the usual combination of housekeeping and
maintenance.
Note:
See TracTickets
for help on using tickets.

Changes from a diff with the previous version:
The tarball now uses xz compression.