From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Brendan Tildesley <mail@brendan.scot>
Cc: 48868-done@debbugs.gnu.org
Subject: bug#48868: VLC cant find libvdpau_radeonsi.so when playing video
Date: Tue, 09 May 2023 04:46:38 +0000 [thread overview]
Message-ID: <871qjqqfh1.fsf@protonmail.com> (raw)
In-Reply-To: <261829148.21236.1622974938782@office.mailbox.org>
Hi Brendan,
On Sun, Jun 06, 2021 at 12:22 PM, Brendan Tildesley wrote:
> 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
prev parent reply other threads:[~2023-05-09 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 10:22 bug#48868: VLC cant find libvdpau_radeonsi.so when playing video Brendan Tildesley
2023-05-09 4:46 ` John Kehayias via Bug reports for GNU Guix
2023-05-09 4:46 ` John Kehayias via Bug reports for GNU Guix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qjqqfh1.fsf@protonmail.com \
--to=bug-guix@gnu.org \
--cc=48868-done@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=mail@brendan.scot \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).