On Tue, 12 Mar 2024 09:50:51 +0100 (CET)
PICCA Frederic-Emmanuel
<
frederic-emmanuel.picca@synchrotron-soleil.fr> wrote:
Hello, I am affected by this error in the autopkgtest of silx[1]
487s autopkgtest [22:01:24]: test gui: [-----------------------
489s MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) 489s glx: failed to create drisw
screen 489s failed to load driver: zink
493s autopkgtest [22:01:30]: test gui: -----------------------]
Someone know how to avoid this issue
the test command is here[2].
thanks for your help
[1]
https://ci.debian.net/packages/s/silx/testing/amd64/43836118/#S12
[2] https://salsa.debian.org/science-team/silx/-/blob/master/debian/tests/gui?ref_type=heads
This affected a pkg of mine as well, and seems to be caused by a
regression in mesa [1]. Long story short, they print messages to
stderr when certain graphics hardware cannot be initialised, even
when that is completely expected (because said hardware simply isn't
present).
For the autopkgtest, you can either wait it out or (temporarily!)
tolerate output on stderr.
[1]
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10293
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmXwIEwACgkQQoMEoXSN zHq2bg/9FRVrECcKDPZweR0FOf0Pbm6mHxELVFr8BILx/S8RHfN4VVtf9YdF2+B6 taaT/iEGtTSIkLX8STmyV/PGZxCw70fbGcNhTcvzdfG8utfyfUhPNpxJ8xI2+9lY gat39m+pRCS/4c50xSx6ar0WLjn1d0KwoKcWJB6QseSYjS/SJu3MgJ9sy9Oljynz NgYq/Dnkq65PYbo1gb6Ki4AWpIo+eNbprglVGN4s5SCdLfR/Z8ovT1FRNd2Mi8G8 e/8dvXjJH45CwY/a778U8cdz6pIic6nmdGSG8HMcx1cn6pMM1NX52+4qmfTpuLgt 8evaMMFrN5R4mk4MIMufpAUoigt5iMXzsH3vdgRUYSIwbR9O2KUYLjdFkBFIS+be tpn+Ee1ZW0KyjDsuyUxhtG9nyQ7hYnpjvdZDP85J98U8CYcFF9QnKXUTbngPQtPe bMFP0THPXXexvCGQR+kXaLy/K+DiW2GMIfwNG3z/Y69xMLMlsJ28Tjti3y/+WMZk pOls+XS60ak5SLMpKADg7FVlS1gbTTzrH4qfp9rp9HD3Gx8CwXvTNhlWO2gQnqov /JWm8vem8YvZNlY0+aScw7zowYfuJuGRxs8hmrnzj5K7ndr5+TxcVSp2AA6d6dFo oQO7FtchmkNGpcKQ9D9xN0TSvutJBNDnJ3ksunKyEBWVf3W1njo=
=XLb0
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)