After updating updating from media-libs/gmmlib-22.0.2 to media-libs/gmmlib-22.0.3 mpv start crash on vaapi. Issue fixed by emerge -1 x11-libs/libva-intel-media-driver-22.1.0 Reproducible: Always [cplayer] (+) Subs --sid=1 --slang=eng (*) 'English subs' (ass) [vo/gpu] Probing for best GPU context. [vo/gpu/opengl] Initializing GPU context 'wayland' [vo/gpu/opengl] Initializing GPU context 'x11egl' [vo/gpu/x11] X11 opening display: :0 [vo/gpu/x11] Display 0 (eDP-1): [0, 0, 3840, 2160] @ 59.996625 FPS [vo/gpu/x11] Current display FPS: 59.996625 [vo/gpu/opengl] EGL_VERSION=1.5 [vo/gpu/opengl] EGL_VENDOR=Mesa Project [vo/gpu/opengl] EGL_CLIENT_APIS=OpenGL OpenGL_ES [vo/gpu/opengl] Trying to create Desktop OpenGL context. [vo/gpu/opengl] Choosing visual EGL config 0x15, visual ID 0x21 [vo/gpu/opengl] GL_VERSION='4.6 (Core Profile) Mesa 21.3.5' [vo/gpu/opengl] Detected desktop OpenGL 4.6. [vo/gpu/opengl] GL_VENDOR='Intel' [vo/gpu/opengl] GL_RENDERER='Mesa Intel(R) HD Graphics 620 (KBL GT2)' [vo/gpu/opengl] GL_SHADING_LANGUAGE_VERSION='4.60' [vo/gpu] Testing FBO format rgba16f [vo/gpu] Using FBO format rgba16f. [vo/gpu] No advanced processing required. Enabling dumb mode. [vo/gpu] Assuming 59.996625 FPS for display sync. [vd] Container reported FPS: 23.976024 [vd] Codec list: [vd] h264 - H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 [vd] h264_v4l2m2m (h264) - V4L2 mem2mem H.264 decoder wrapper [vd] h264_cuvid (h264) - Nvidia CUVID H264 decoder [vd] Opening decoder h264 [vd] Looking at hwdec h264-vaapi... [vo/gpu] Loading hwdec driver 'vaapi-egl' [vo/gpu/vaapi-egl] using VAAPI EGL interop [vo/gpu/vaapi-egl] Trying to open a x11 VA display... Segmentation fault (core dumped)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b403912e3097ee8cfa139d364f184db39fab3993 commit b403912e3097ee8cfa139d364f184db39fab3993 Author: Conrad Kostecki <conikost@gentoo.org> AuthorDate: 2022-03-07 19:45:01 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2022-03-07 19:45:01 +0000 x11-libs/libva-intel-media-driver: force revbump Closes: https://bugs.gentoo.org/834634 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> ...dia-driver-22.1.0.ebuild => libva-intel-media-driver-22.1.0-r1.ebuild} | 0 1 file changed, 0 insertions(+), 0 deletions(-)
I think it is not the best fix. Just revbump may not update everywhere. If someone locked gmmlib version, updated libva-intel-media-driver, and then unlocked gmmlib, it would be the same problem again. The better fix would be the new subslot for gmmlib.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=03291e3303596b36a1c1d595450a8ccc7afdce79 commit 03291e3303596b36a1c1d595450a8ccc7afdce79 Author: Karlson2k (Evgeny Grin) <k2k@narod.ru> AuthorDate: 2022-03-08 16:04:16 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-03-08 18:38:19 +0000 media-libs/gmmlib: added new subslot While gmmlib version 2.0.3 has not introduced new so-name, it is required to rebuild dependent packages as otherwise they are crashing. Closes: https://bugs.gentoo.org/834634 Closes: https://bugs.gentoo.org/834785 Bug: https://bugs.gentoo.org/834734 Signed-off-by: Karlson2k (Evgeny Grin) <k2k@narod.ru> Closes: https://github.com/gentoo/gentoo/pull/24453 Signed-off-by: Sam James <sam@gentoo.org> media-libs/gmmlib/{gmmlib-22.0.3.ebuild => gmmlib-22.0.3-r1.ebuild} | 5 ++++- media-libs/gmmlib/gmmlib-9999.ebuild | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-)
