chromium: Upgrade to 150.0.7871.128 (wrynose)

[zboszor]

Release notes:
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_049796704.html

Build and patch changes:
------------------------

Added patches:

None

Removed patches:

None

Modified patches:

None

License changes:
----------------

None

Test dependencies:
------------------

* URI: git://git.openembedded.org/openembedded-core
  - branch: wrynose
  - revision: c2746a4a165fd99c2d1aafed17533555787f37ce

* URI: git://git.openembedded.org/meta-openembedded
  - layers: meta-oe
  - branch: wrynose
  - revision: d97b5602d7f64422c94b7311466cda7f6b1962d5

* URI: git://git.yoctoproject.org/meta-intel
  - branch: master
  - revision: 0edb84a9e6a6f14b7647ab2b8c7a690741c67984

* URI: https://github.com/agherzan/meta-raspberrypi
  - branch: wrynose
  - revision: f62c67921474370829d24a4fa01ef88543f3906b

@MaxIhlenfeldt My wrynose builds have finished.

[thorstenl312]

Hello,

I have tried building this version of chromium and ran into this error:
../../media/gpu/sandbox/hardware_video_decoding_sandbox_hook_linux.cc:150:9: error: use of undeclared identifier 'ERROR' 150 | LOG(ERROR) << "dlopen(radeonsi_dri.so) failed with error: " << dlerror(); | ^~~~~ 1 error generated.

Here is a patch to fix the error:
0014-add-missing-logging-header.patch

Looks like this also fixes #1003

Let me know if this is valid on your end.

[zboszor]

Hello,

I have tried building this version of chromium and ran into this error: ../../media/gpu/sandbox/hardware_video_decoding_sandbox_hook_linux.cc:150:9: error: use of undeclared identifier 'ERROR' 150 | LOG(ERROR) << "dlopen(radeonsi_dri.so) failed with error: " << dlerror(); | ^~~~~ 1 error generated.

Here is a patch to fix the error: 0014-add-missing-logging-header.patch

Looks like this also fixes #1003

Let me know if this is valid on your end.

Thanks, I will add this patch. My build indeed has the same change in a bbappend as in #1003 :

PACKAGECONFIG:append = " use-vaapi"
PACKAGECONFIG:remove = " use-v4l2"

[zboszor]

@thorstenl312 @MaxIhlenfeldt With the above attached patch added, the build succeeded for the default configuration, i.e. PACKAGECONFIG = " ... use-v4l2 ...