Description of problem: When a Chrome based app that uses X11 is run, many times the app will crash and take xwayland with it, preventing apps that need xwayland to run. Version-Release number of selected component (if applicable): Fedora 36 KDE How reproducible: Varies. The chromium package, Flatpak Chrome, Flatpak MS Edge, and nwjs seem to always cause a crash. Steps to Reproduce: 1. Run an application that uses Chromium Actual results: The app and xwayland crashes. Apps that need xwayland no longer work. Appindicators that were from xwayland apps crash. Expected results: The apps run Additional info: nwjs always crashes, even on GNOME, though it doesn't take out xwayland with it. nwjs crashes with the following error: "libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)" This is a laptop with switchable Vega 8/Polaris graphics. This did not happen on Fedora 35.
As it turns out this actually has nothing to do with Chromium. Filing a separate one for the actual issue.
Ignore that. To reproduce this issue, run DRI_PRIME=1 glxinfo under a wayland session in KDE, and XWayland immediately crashes.
Well, actually, this has nothing to do with "Wayland" (the component) which is just a set of protocol definitions and a small IPC library, That said, if Xwayland crashes, the first thing to provide is a backtrace (with symbols) of Xwayland in gdb. Can you please provide the following: 1. Install the debuginfo package for xorg-x11-server-Xwayland 2. Run "coredumpctl gdb" on the Xwayland process that crashed 3. attach the output of "bt" and "bt full" from the gdb session
Created attachment 1882567 [details] backtrace I've never generated a backtrace before, so hopefully I did this right.
(In reply to Alastor Tenebris from comment #4) > I've never generated a backtrace before, so hopefully I did this right. You did, perfect thanks! That is probably a dupe of bug 2088807 Was it you who filed https://gitlab.freedesktop.org/xorg/xserver/-/issues/1344 upstream as well?
(In reply to Olivier Fourdan from comment #5) > (In reply to Alastor Tenebris from comment #4) > > I've never generated a backtrace before, so hopefully I did this right. > > You did, perfect thanks! > > That is probably a dupe of bug 2088807 > > Was it you who filed > https://gitlab.freedesktop.org/xorg/xserver/-/issues/1344 upstream as well? That was not me. Here's the upstream bug report: https://bugs.kde.org/show_bug.cgi?id=452062. Looks like it has something to do with having switchable AMD GPUs.
I fired a scratch build for Xwayland with the fix from https://gitlab.freedesktop.org/xorg/xserver/-/issues/1344, can you please give this build a try once it's complete: https://koji.fedoraproject.org/koji/taskinfo?taskID=87434411
Yep that seemed to fix it.
Brilliant, thanks for testing and confirming!
FEDORA-2022-0ee78d34e9 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ee78d34e9
FEDORA-2022-0ee78d34e9 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0ee78d34e9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ee78d34e9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0ee78d34e9 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.