Comment # 9 on bug 1217429 from Petr Vorel
Running on yesterday update, with new chromium, it keeps failing. I double
check it's does not segfault on xorg, only on wayland.

Let me know if you need updated coredump file (coredumpctl dump --output=foo)
or any other log.

$ grep VERSION_ID /etc/os-release
VERSION_ID="20231122"

$ rpm -qa | grep -e chromium -e wayland -e wlroots -e sway- | sort
chromium-ffmpeg-extra-114.0.5735.198-1699.1.pm.2.x86_64
chromium-plugin-widevinecdm-4.10.2710.0-1699.1.pm.3.x86_64
chromium-119.0.6045.159-1.1.x86_64
kwayland-5.112.0-1.1.x86_64
libgstwayland-1_0-0-1.22.7-1.1.x86_64
libnvidia-egl-wayland1-1.1.13-1.1.x86_64
libqt5-qtwayland-5.15.11+kde59-1.1.x86_64
libva-wayland2-2.20.0-1.1.x86_64
libwayland-client0-1.22.0-1.3.x86_64
libwayland-cursor0-1.22.0-1.3.x86_64
libwayland-egl1-1.22.0-1.3.x86_64
libwayland-server0-1.22.0-1.3.x86_64
libwlroots11-0.16.2-2.5.x86_64
patterns-sway-sway-20200619-6.1.x86_64
qt6-wayland-6.6.0-1.2.x86_64
sway-branding-openSUSE-0.15.2-1.1.noarch
sway-marker-0.3~0-2.5.x86_64
sway-1.8.1-6.1.x86_64
wayland-devel-1.22.0-1.3.x86_64
xwayland-23.2.2-1.1.x86_64


You are receiving this mail because: