https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #11 from David Edmundson <k...@davidedmundson.co.uk> ---
Relevant mesa code:
wsi_common_x11.c: 659
```
x11_surface_get_capabilities(VkIcdSurfaceBase *icd_surface,
struct wsi_device *wsi_device,
VkSurfaceCapabilitiesKHR *caps)
{
xcb_connection_t *conn = x11_surface_get_connection(icd_surface);
xcb_window_t window = x11_surface_get_window(icd_surface);
xcb_get_geometry_cookie_t geom_cookie;
xcb_generic_error_t *err;
xcb_get_geometry_reply_t *geom;
unsigned visual_depth;
geom_cookie = xcb_get_geometry(conn, window);
/* This does a round-trip. This is why we do get_geometry first and
* wait to read the reply until after we have a visual.
*/
xcb_visualtype_t *visual =
get_visualtype_for_window(conn, window, &visual_depth);
if (!visual)
return VK_ERROR_SURFACE_LOST_KHR;
geom = xcb_get_geometry_reply(conn, geom_cookie, &err);
if (geom) {
VkExtent2D extent = { geom->width, geom->height };
caps->currentExtent = extent;
caps->minImageExtent = extent;
caps->maxImageExtent = extent;
}
```
it's just using the regular window geometry, so that can't really be wrong.
I strongly suspect our window is configured to the 1280x721size; at which point
it's partly client side problems for not handling that correctly. Turning a
harmless though non-ideal quirk into a user-breakage.
We could aim for a mesa fix there to use the similar min and max that wayland
would use.
As for why kwin is configuring a window differently to requested, I'll expand
our relevant unit test and try to hit it. It'll probably be the annoying resize
increments. If you can `xprop` a window that's known to be annoying that would
help me.
--
You are receiving this mail because:
You are watching all bug changes.
