Follow-up to my earlier comment: I've now identified the specific ICD, and
ruled out the GPU hardware itself. Two experiments:
1) Hardware ruled out. I disabled the discrete GPU entirely in BIOS
(Graphics Device: NVIDIA Optimus -> Integrated Graphics); the NVS 4200M is
now absent from lspci. The crash is unchanged — identical stack-smash /
exit_code=134 / "GPU process isn't usable" with all ICDs visible. So the
mere presence of the second GPU is not the trigger. (Also note: now
reproduced on Vivaldi 8.1.4087.61 as well as .55.)
2) ICD bisect. Launching the browser once per installed ICD manifest with
only that ICD visible and the workaround unset:
for icd in /usr/share/vulkan/icd.d/*.json; do
env -u VK_LOADER_DRIVERS_DISABLE \
VK_DRIVER_FILES="$icd" VK_ICD_FILENAMES="$icd" \
vivaldi --user-data-dir=/tmp/vktest ...
done
Results:
asahi_icd: ok
gfxstream_vk_icd: ok
intel_hasvk_icd: ok
intel_icd: ok
lvp_icd: ok
nouveau_icd: ok
nvidia_icd: CRASH <--
radeon_icd: ok
virtio_icd: ok
All eight Mesa ICDs load fine. The one and only trigger is
nvidia_icd.json — which on this machine comes from libnvidia-gl-390, the
legacy 390 branch (the last driver series supporting Fermi chips like the
NVS 4200M). Its manifest is ancient (file_format_version 1.0.0,
api_version 1.0.65) and points at libGLX_nvidia.so.0. dlopen of that
library by the browser's bundled Vulkan loader is what trips the stack
protector in glibc's dlerror path.
This likely explains the machine correlation better than the hardware
does: any Fermi-era Optimus machine (the reporter's E6420, my T520) that
ever had the proprietary driver installed will be sitting on the
nvidia-390 legacy userspace, and it's that userspace — not the GPU — that
kills the bundled loader. The distro loader (libvulkan1 1.3.275) handles
the same manifest without crashing, so this looks like the bundled
loader mishandling a dlopen failure path that newer system loaders
tolerate.
For the original reporter, worth checking:
dpkg -l | grep nvidia-390
ls /usr/share/vulkan/icd.d/
Refined workarounds, in order of preference:
- If the NVIDIA GPU is unused (very likely on this hardware — 390 has
no useful Vulkan anyway): remove the legacy driver packages
(libnvidia-gl-390 etc.); the offending manifest goes with them.
- Otherwise, a targeted VK_LOADER_DRIVERS_DISABLE=nvidia* in
/etc/environment — no need for the blanket '*' from my earlier
comment, everything Mesa loads fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2133259
Title:
Chromium 142.0.7444.175 Snap craches on launch, stack smashing
detected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2133259/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
