Blame SOURCES/0011-Use-qWarning-and-_exit-instead-of-qFatal-for-wayland.patch

429548
From 9ee2ea141adc7765f6c212e63839ef23a4494b30 Mon Sep 17 00:00:00 2001
429548
From: Weng Xuetian <wengxt@gmail.com>
429548
Date: Tue, 9 Mar 2021 10:43:59 -0800
429548
Subject: [PATCH 11/36] Use qWarning and _exit() instead of qFatal for wayland
429548
 error
429548
429548
This type of error is likely to happen upon system logout. qFatal would
429548
trigger sigabrt and leave unnecessary coredump on the system. Using
429548
qWarning here would make it consistent with xcb's io error.
429548
429548
Pick-to: 5.15 6.0 6.1
429548
Change-Id: I571ba007bf2453486b81837cccdbefa5f181b63d
429548
Reviewed-by: David Edmundson <davidedmundson@kde.org>
429548
---
429548
 src/client/qwaylanddisplay.cpp | 5 +++--
429548
 1 file changed, 3 insertions(+), 2 deletions(-)
429548
429548
diff --git a/src/client/qwaylanddisplay.cpp b/src/client/qwaylanddisplay.cpp
429548
index fe094f6f..f10c1f79 100644
429548
--- a/src/client/qwaylanddisplay.cpp
429548
+++ b/src/client/qwaylanddisplay.cpp
429548
@@ -206,10 +206,11 @@ void QWaylandDisplay::checkError() const
429548
     int ecode = wl_display_get_error(mDisplay);
429548
     if ((ecode == EPIPE || ecode == ECONNRESET)) {
429548
         // special case this to provide a nicer error
429548
-        qFatal("The Wayland connection broke. Did the Wayland compositor die?");
429548
+        qWarning("The Wayland connection broke. Did the Wayland compositor die?");
429548
     } else {
429548
-        qFatal("The Wayland connection experienced a fatal error: %s", strerror(ecode));
429548
+        qWarning("The Wayland connection experienced a fatal error: %s", strerror(ecode));
429548
     }
429548
+    _exit(1);
429548
 }
429548
 
429548
 void QWaylandDisplay::flushRequests()
429548
-- 
429548
2.33.1
429548