https://bugs.kde.org/show_bug.cgi?id=498837
--- Comment #3 from Matt Fagnani <matt.fagn...@bell.net> --- Created attachment 177580 --> https://bugs.kde.org/attachment.cgi?id=177580&action=edit Journal of Plasma startup with Xwayland has crashed notification and debugging enabled The Xwayland has crashed notification appears to be from XwaylandLauncher::handleXwaylandFinished https://invent.kde.org/plasma/kwin/-/blob/master/src/xwayland/xwaylandlauncher.cpp#L270 void XwaylandLauncher::handleXwaylandFinished(int exitCode, QProcess::ExitStatus exitStatus) { qCDebug(KWIN_XWL) << "Xwayland process has quit with exit status:" << exitStatus << "exit code:" << exitCode; #if KWIN_BUILD_NOTIFICATIONS KNotification::event(QStringLiteral("xwaylandcrash"), i18n("Xwayland has crashed")); #endif In Plasma 6.2.90 in a VM, I put QT_LOGGING_RULES="*.debug=true;qt*.debug=false" in /etc/environment and I restarted Plasma until the Xwayland has crashed notification was shown. 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. Jan 21 23:22:47 kwin_wayland_wrapper[9053]: (EE) Jan 21 23:22:47 kwin_wayland_wrapper[9053]: Fatal server error: Jan 21 23:22:47 kwin_wayland_wrapper[9053]: (EE) Cannot write display number to fd 72 Jan 21 23:22:47 kwin_wayland_wrapper[9053]: (EE) Jan 21 23:22:47 kwin_wayland[8992]: kwin_xwl: Failed to establish the XCB connection (error 1) Jan 21 23:22:47 kwin_wayland[8992]: kwin_xwl: Xwayland process has quit with exit status: QProcess::NormalExit exit code: 1 Xwayland didn't create a core dump. I'm attaching the journal from the Plasma session with the Xwayland has crashed notification. -- You are receiving this mail because: You are watching all bug changes.
