Thanks for testing. So, your first log contains this error, though:
```
/build/chromium/parts/chromium/build
ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit
code.
dri_driver_dir = exec_script(pkg_config_script,
^----------
Current dir: /build/chromium/parts/chromium/build/out/Release/
Command: python3
/build/chromium/parts/chromium/build/build/config/linux/pkg-config.py -p
/snap/gnome-3-38-2004/current/usr/bin/pkg-config --dridriverdir dri
Returned 1 and printed out:
Error from pkg-config.
stderr:
```
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004586
Title:
Chromium's minigbm uses incorrect path for loading radeonsi_dri
driver.
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
[NOTE] This is for the HWACC build of chromium, from snap channel
latest/candidate/hwacc
$ snap info chromium | grep installed
installed: 107.0.5304.68-hwacc (2301) 172MB -
This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa
origin.
(Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers,
like NV12.)
Regular builds of the chromium snap will not use minigbm, and thus not
exhibit this behaviour!
Something goes wrong with the expansion of the macro DRI_DRIVER_DIR
$ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep
radeonsi_
/usr/lib64/dri/radeonsi_dri.so
DRI_DRIVER_DIR/radeonsi_dri.so
dlopen(radeonsi_dri.so) failed with error:
The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux-
gnu here.
I've also built current HEAD of chromium source code manually, and did
the same test on that, and that version is unaffected:
$ strings out/Default/chrome | grep radeonsi_
dlopen(radeonsi_dri.so) failed with error:
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
/usr/lib64/dri/radeonsi_dri.so
A partner found this change to third_party/minigbm/src/amdgpu.c:27 to
be working:
//#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so)
#define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so"
But it is better to understand why this expansion failed.
And it is possibly fixed in later chromium releases, if not, we should look
how our snap building differs from the official Linux building instructions for
chromium.
In any case, we should track this.
OS: Ubuntu 22.10
Package: chromium
Snap version: 107.0.5304.68-hwacc
Channel: latest/candidate/hwacc
Expectations: correctly loading driver from correct location.
Actual: using incorrect location.
I will follow up by testing this on a machine with an AMD GPU.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
