Created attachment 2075027 [details] screenshot of the notification Description of problem: In Rawhide, KDE sometimes shows a notification from KWin that says "XWayland has crashed". That's all it says. Clicking the notification does nothing. drkonqi shows no crashes. There is no trace of XWayland, or anything else, crashing in the system journal. Version-Release number of selected component (if applicable): kwin-6.2.90-2.fc42 How reproducible: About one in three tries (well, I tried three times locally, it happened once...) Steps to Reproduce: 1. Boot a clean Fedora Rawhide KDE - live image or installed 2. Open Notifications Actual results: A notification which appears to be lying, and is unactionable Expected results: No such useless notification Additional info: This is a downstream report of https://bugs.kde.org/show_bug.cgi?id=499473 . I'm filing it as it actually looks like a Final blocker, per "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop" - https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria#SELinux_and_crash_notifications . This is partly a polish criterion. It's partly about not wanting important things to be crashing, but it is also specifically meant to cover *spurious* crash notifications, because they give a very bad impression of Fedora (it makes people say "Fedora is unstable" and stuff like that).
https://bugs.kde.org/show_bug.cgi?id=498837 is an earlier upstream report with some more investigation.
I reported this problem at https://bugzilla.redhat.com/show_bug.cgi?id=2338761 There was a fatal server error in Xwayland "Cannot write display number to fd 72", kwin failed to establish the the XCB connection, and Xwayland quit with the code 1.
ah, sorry, didn't find either of your bugs. closing as a dupe. *** This bug has been marked as a duplicate of bug 2338761 ***