chromium: Upgrade to 150.0.7871.186 (wrynose)

[zboszor]

Release notes:

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

150.0.7871.181:
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0256605430.html

150.0.7871.186:
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_01320465736.html

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

Added patches:

* 0014-add-missing-logging-header.patch
  It fixes the build for use-v4l2
  See https://github.com/OSSystems/meta-browser/issues/1003
  Patch taken as is from https://github.com/OSSystems/meta-browser/pull/1015#issuecomment-5026644146

Removed patches:

None

Modified patches:

None

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

None

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

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

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

* URI: git://git.yoctoproject.org/meta-intel
  - branch: wrynose
  - revision: 79a9681ce83f6bf36aede3aeb8c1707d29bca329

* 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 ...

[thorstenl312]

Thanks! Can confirm the build succeeded.

[MaxIhlenfeldt]

@thorstenl312 thanks for the patch! It says Upstream-Status: Pending, do you have a link to the CL? In my experience upstream usually merges this kind of change without much hassle.

[thorstenl312]

Hi @MaxIhlenfeldt. Based off the yocto documentation, Upstream-Status: Pending means

No determination has been made yet, or patch has not yet been submitted to upstream.

I can look into submitting a CL later this week and update it to Upstream-Status: Submitted

[zboszor]

Hi @MaxIhlenfeldt. Based off the yocto documentation, Upstream-Status: Pending means

No determination has been made yet, or patch has not yet been submitted to upstream.

I can look into submitting a CL later this week and update it to Upstream-Status: Submitted

You only need this patch up to Chromium 151, hopefully they still accept submissions for that version.

As far as I can see, with 152, use-vaapi and use-v4l2 can both be enabled at compile time without a build issue.