From: Gottox <Gottox@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Revert intel-media-driver
Date: Sat, 19 Feb 2022 12:18:31 +0100 [thread overview]
Message-ID: <20220219111831.-d0ogtoxloBxSvHhdv9OY9mmFaZhMPQKDmCsI0dkkxQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35433@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
There's a merged pull request on the void-packages repository
Revert intel-media-driver
https://github.com/void-linux/void-packages/pull/35433
Description:
- Revert "intel-media-driver: update to 22.1.1"
- Revert "intel-gmmlib: update to 22.0.1"
This works around a problem with firefox which crashes with the following message:
```
libva info: VA-API version 1.13.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_13
readlink -errno 13
```
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-02-19 11:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 8:39 [PR PATCH] " Gottox
2022-02-06 10:40 ` daerich
2022-02-08 20:54 ` sug0
2022-02-08 20:57 ` Vistaus
2022-02-10 13:18 ` daerich
2022-02-10 13:20 ` daerich
2022-02-10 13:30 ` [PR REVIEW] " daerich
2022-02-10 13:32 ` daerich
2022-02-10 13:40 ` daerich
2022-02-11 5:09 ` cinerea0
2022-02-11 10:36 ` Vistaus
2022-02-11 10:36 ` Vistaus
2022-02-11 11:08 ` [PR PATCH] [Closed]: " Gottox
2022-02-11 11:08 ` Gottox
2022-02-17 12:52 ` steinex
2022-02-17 12:57 ` steinex
2022-02-18 8:58 ` Gottox
2022-02-18 8:58 ` Gottox
2022-02-18 9:19 ` [PR PATCH] [Updated] " Gottox
2022-02-18 9:30 ` Gottox
2022-02-19 0:29 ` cinerea0
2022-02-19 11:18 ` Gottox [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220219111831.-d0ogtoxloBxSvHhdv9OY9mmFaZhMPQKDmCsI0dkkxQ@z \
--to=gottox@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).