On 2023-02-12 15:55:14 +0300, Vladimir Stavrinov wrote: > On Sun, Feb 12, 2023 at 11:48 AM Sebastian Ramacher > <sramac...@debian.org> wrote: > > > > > Please install the relevant -dbgsym packages and reproduce the crash > > Give me an exact list of such packages. I can't find anything > appropriate neither vlc nore libva relevant.
See https://wiki.debian.org/HowToGetABacktrace how to get debug symbols by installing -dbgsym packages our using debuginfod. That page has all the information to produe a backtrace. > > under gdb. We need a backtrace to identifiy the package that is at > > fault. > > As I've already stated above this package is libva. Here is a list of > dependent packages version installation of which solve this problem: > > libva2_2.16.0-1_amd64.deb > libva-dev_2.16.0-1_amd64.deb > libva-drm2_2.16.0-1_amd64.deb > libva-glx2_2.16.0-1_amd64.deb > libva-wayland2_2.16.0-1_amd64.deb > libva-x11-2_2.16.0-1_amd64.deb > > i.e with these packages being installed vlc doesn't crash. After > upgrading the system causing upgrading libva as well the problem > emerged again. I don't want to pin the libva version, so we need to > solve this problem in a regular way. > > P.S. I wonder why You can't reproduce this bug yourself. The only you > need for this is recent sid distribution or if to be accurate libva-* > packages of 2.17.0-1 version. Or do You mean vlc doesn't crash in such > an environment in your installation? If so it would be strange. The libva upgrade may have triggered a latent bug in one of the VA-API drivers. But as anything with libva (note that libva just loads the drivers and directly forwards all calls) these bugs depend on drivers and hardware. Cheers -- Sebastian Ramacher
