VLC cant find libvdpau_radeonsi.so when playing video

  • Done
  • quality assurance status badge
Details
2 participants
  • John Kehayias
  • Brendan Tildesley
Owner
unassigned
Submitted by
Brendan Tildesley
Severity
normal
B
B
Brendan Tildesley wrote on 6 Jun 2021 12:22
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
261829148.21236.1622974938782@office.mailbox.org
The file exists at
/gnu/store/mwcgqw9ggi02p8mhzac8cg0x671j7wd1-mesa-20.2.4/lib/vdpau/libvdpau_radeonsi.so
but it doesn't seem to be found (by libva?).
Videos still play. Probably requires a Radeon card to reproduce.
I got confused trying to figure out where exactly its loaded.

libva info: VA-API version 1.10.0
libva info: Trying to open /gnu/store/gvncg7gzdzjx0gvyi4sm02m7qgnsmx5q-mesa-20.2.4/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva info: va_openDriver() returns 0
[00007f6928001f80] glconv_vaapi_x11 gl error: vaDeriveImage: operation failed
[00007f69240ba3a0] main video output error: video output creation failed
[00007f69e8c929f0] main decoder error: failed to create video output
Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory
J
J
John Kehayias wrote on 9 May 2023 06:46
(name . Brendan Tildesley)(address . mail@brendan.scot)(address . 48868@debbugs.gnu.org)
873546qfhm.fsf@protonmail.com
Hi Brendan,

On Sun, Jun 06, 2021 at 12:22 PM, Brendan Tildesley wrote:

Toggle quote (16 lines)
> The file exists at
> /gnu/store/mwcgqw9ggi02p8mhzac8cg0x671j7wd1-mesa-20.2.4/lib/vdpau/libvdpau_radeonsi.so
> but it doesn't seem to be found (by libva?).
> Videos still play. Probably requires a Radeon card to reproduce.
> I got confused trying to figure out where exactly its loaded.
>
> libva info: VA-API version 1.10.0
> libva info: Trying to open /gnu/store/gvncg7gzdzjx0gvyi4sm02m7qgnsmx5q-mesa-20.2.4/lib/dri/radeonsi_drv_video.so
> libva info: Found init function __vaDriverInit_1_10
> libva info: va_openDriver() returns 0
> [00007f6928001f80] glconv_vaapi_x11 gl error: vaDeriveImage: operation failed
> [00007f69240ba3a0] main video output error: video output creation failed
> [00007f69e8c929f0] main decoder error: failed to create video output
> Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory
> Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory

This has been fixed with 02995444dbe9861c32b6e2cdbfb7a7b2affe2c2b
J
J
John Kehayias wrote on 9 May 2023 06:46
(name . Brendan Tildesley)(address . mail@brendan.scot)(address . 48868-done@debbugs.gnu.org)
871qjqqfh1.fsf@protonmail.com
Hi Brendan,

On Sun, Jun 06, 2021 at 12:22 PM, Brendan Tildesley wrote:

Toggle quote (16 lines)
> The file exists at
> /gnu/store/mwcgqw9ggi02p8mhzac8cg0x671j7wd1-mesa-20.2.4/lib/vdpau/libvdpau_radeonsi.so
> but it doesn't seem to be found (by libva?).
> Videos still play. Probably requires a Radeon card to reproduce.
> I got confused trying to figure out where exactly its loaded.
>
> libva info: VA-API version 1.10.0
> libva info: Trying to open /gnu/store/gvncg7gzdzjx0gvyi4sm02m7qgnsmx5q-mesa-20.2.4/lib/dri/radeonsi_drv_video.so
> libva info: Found init function __vaDriverInit_1_10
> libva info: va_openDriver() returns 0
> [00007f6928001f80] glconv_vaapi_x11 gl error: vaDeriveImage: operation failed
> [00007f69240ba3a0] main video output error: video output creation failed
> [00007f69e8c929f0] main decoder error: failed to create video output
> Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory
> Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory

This has been fixed with 02995444dbe9861c32b6e2cdbfb7a7b2affe2c2b
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 48868@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 48868
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch