-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restrict SimpleGlobal bindings to our max API version #406
Conversation
This is a partial fix for the way SimpleGlobal binds to the latest version offered by the server instead of the latest version the client understands, which causes errors (usually leading to crashes) when a server actually uses the later version and sends an event we don't know about.
@wash2 could we make it into patch release on v0.16.x branch? It affects wezterm from what I understood since they haven't updated yet and I'm not sure whether they will. |
The CI failures are not relevant if it matters. |
Should we increment the version to 0.16.1 in this PR? |
@wash2 in the separate. |
Just a minor note -- it seems that the 0.16.1 tag was never pushed to this repo (though that version has been published on crates.io and docs.rs successfully). |
Ok the tag is pushed now |
Cheers, thanks! |
### Changed - Updated smithay-client-toolkit to resolve issue described in Smithay/client-toolkit#406 (#20). https://github.com/AndreasBackx/waycorner/actions/runs/8351084763
This is a partial fix for the way SimpleGlobal binds to the latest version offered by the server instead of the latest version the client understands, which causes errors (usually leading to crashes) when a server actually uses the later version and sends an event we don't know about.
This fixes crashes in a number of clients using SCTK-0.16 on compositors supporting the newest wayland surface APIs (to be precise, any that send a
preferred_buffer_scale
event).