ptyxis vkAcquireNextImageKHR errors
kind/bug
### Describe the bug
This issue has already been [reported in Bazzite](https://github.com/ublue-os/bazzite/issues/3255), but did not get any traction. I re-based from Bazzite into Bluefin today, and I see this error in Bluefin (up to date with today's packages).
```
ptyxis[9544]: vkAcquireNextImageKHR(): A swapchain no longer matches the surface properties exactly, but can still be used to present to the surface successfully. (VK_SUBOPTIMAL_KHR) (1000001003)
```
### What did you expect to happen?
I understand this is just a warning and doesn't break/block anything, but it's very noisy. It's multiple dozens of messages per hour, depending on what I am doing.
### Output of `bootc status`
```shell
● Booted image: ghcr.io/ublue-os/bluefin-dx:stable
Digest: sha256:edf5ac9edcc1fb152a157b354ae87870b3ea1d7753e5b52ab5cff2f98e3bed28 (amd64)
Version: 44.20260512 (2026-05-12T01:50:35Z)
Rollback image: ghcr.io/ublue-os/bazzite-dx-gnome:stable
Digest: sha256:3c952e270c774836042896d837864151debc84358979d0994af190a665d4e537 (amd64)
Version: 43.20260420 (2026-04-30T04:03:38Z)
```
### Output of `groups`
```shell
netmask wheel dialout docker libvirt
```
### Extra information or context
_No response_
0 条评论