https://bugs.kde.org/show_bug.cgi?id=414116
--- Comment #3 from Matt Fagnani <matthew.fagn...@utoronto.ca> --- Created attachment 130090 --> https://bugs.kde.org/attachment.cgi?id=130090&action=edit New crash information added by DrKonqi plasmashell (5.19.3) using Qt 5.14.2 - What I was doing when the application crashed: I logged into Plasma 5.19.3 on Wayland in Fedora Rawhide with Qt 5.14.2, KF 5.72.0 from sddm. I've continued to see these plasmashell crashes where the Wayland connection broke occasionally when logging in and at other times like when using Firefox. The crashes happened particularly when there's been high I/O to the drive Fedora was on. Several KDE programs aborted each time I logged out of Plasma 5.19.3 and earlier on Wayland with the same error. Is there a setting that could increase something like a timeout duration for Qt programs before the Wayland connection is considered to be broken? - Unusual behavior I noticed: The background went black and automatically reappeared. -- Backtrace (Reduced): #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x00007f28fadfa8a4 in __GI_abort () at abort.c:79 #6 0x00007f28fb21da7f in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffe676728f0, msg=msg@entry=0x7f28e997c160 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #8 0x00007f28e98ff8a9 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90 -- You are receiving this mail because: You are watching all bug changes.
