Bug 2270321 - VAAPI flags in chromium.conf are out of date
Summary: VAAPI flags in chromium.conf are out of date
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-19 16:46 UTC by secureblue
Modified: 2024-03-29 00:19 UTC (History)
4 users (show)

Fixed In Version: chromium-123.0.6312.58-2.fc39 chromium-123.0.6312.58-2.fc38 chromium-123.0.6312.86-1.fc40
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-27 01:26:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description secureblue 2024-03-19 16:46:47 UTC
VAAPI support was modified as of 122: https://chromium-review.googlesource.com/c/chromium/src/+/3646633

As such, per https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/gpu/vaapi.md#verify-vaapi, chromium.conf should have this:

```
# system wide chromium flags
CHROMIUM_FLAGS=""
CHROMIUM_FLAGS+=" --use-gl=angle --use-angle=gl --enable-features=VaapiVideoEncoder,VaapiVideoDecodeLinuxGL"
```

Reproducible: Always

Comment 1 Fedora Update System 2024-03-25 15:45:41 UTC
FEDORA-2024-f92215b177 (chromium-123.0.6312.58-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f92215b177

Comment 2 Fedora Update System 2024-03-25 15:45:47 UTC
FEDORA-2024-8c3da7e7be (chromium-123.0.6312.58-2.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8c3da7e7be

Comment 3 Fedora Update System 2024-03-25 15:45:52 UTC
FEDORA-2024-4ad2447841 (chromium-123.0.6312.58-2.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ad2447841

Comment 4 Fedora Update System 2024-03-26 01:12:01 UTC
FEDORA-2024-4ad2447841 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4ad2447841`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ad2447841

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2024-03-26 01:20:52 UTC
FEDORA-2024-f92215b177 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-f92215b177`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f92215b177

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-03-26 01:51:41 UTC
FEDORA-2024-8c3da7e7be has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-8c3da7e7be`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8c3da7e7be

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-03-27 01:26:40 UTC
FEDORA-2024-4ad2447841 (chromium-123.0.6312.58-2.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2024-03-27 01:37:15 UTC
FEDORA-2024-8c3da7e7be (chromium-123.0.6312.58-2.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2024-03-29 00:19:43 UTC
FEDORA-2024-85531c965e (chromium-123.0.6312.86-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.