Firefox doesn't start after installation of amdgpu driver
Hi,
I have a laptop with an AMD Ryzen 7 8845HS CPU, including a Radeon 780M iGPU, running Ubuntu 24.04. In order to fully utilize the GPU by supporting OpenCL acceleration I installed the additional drivers by: `sudo amdgpu-install --usecase=graphics,multimedia,opencl --opencl=rocr --opengl=mesa`
After that programs which benefit from OpenCL acceleration recognize the GPU, however firefox starts crashing with the following error msg:
XPCOMGlueLoad error for file /usr/lib/firefox/libmozgtk.so: libwayland-client.so.0: failed to map segment from shared object Couldn't load XPCOM.
It seems that the AMD GPU drivers registered their libraries in `/etc/ld.so.conf.d` as 10-rocm-opencl.conf, 20-amdgpu.conf which means that libraries within the given folders are found first.
This applies to the libwayland-client library, which is used by `/usr/lib/firefox/libmozgtk.s`:
ldd /usr/lib/firefox/libmozgtk.so | grep amd libwayland-client.so.0 => /opt/amdgpu/lib/x86_64-linux-gnu/libwayland-client.so.0 (0x00007013767bf000)
Interestingly the same `libmozgtk.so` library is used by thunderbird:
ldd /usr/lib/thunderbird/libmozgtk.so | rg -i amd libwayland-client.so.0 => /opt/amdgpu/lib/x86_64-linux-gnu/libwayland-client.so.0 (0x00007d44b0f41000)
However thunderbird just works fine, so I expect that there might be something wrong with firefox utilizing this library.
Maybe I should also mention, that I'm not even using wayland as desktop compositor, but good old x11:
echo $XDG_SESSION_TYPE x11
Is there any way to further debug this issue?
所有回复 (2)
Maybe I should mention that I'm using the firefox 133.0 debian package from the `ppa.launchpadcontent.net/mozillateam/ppa/ubuntu` repository, not the one from snap.
I checked other desktop programs which link against `libwayland-client.so.0` and do not have any problems such as firefox.
由carcass_dev0于修改
I was curious if this issue also occurs with older firefox versions and installed the package "firefox-esr". After that the issue has been gone... This is good but not really a satisfying outcome, as I have the feeling that the problem could occur again with a new version.