https://bugs.kde.org/show_bug.cgi?id=413058
--- Comment #1 from Matt Fagnani ---
Created attachment 125158
--> https://bugs.kde.org/attachment.cgi?id=125158=edit
New crash information added by DrKonqi
konsole (19.12.1) using Qt 5.13.2
- What I was doing when the application crashed:
I was running Plasma 5.17.5 on Wayland in Fedora Rawhide with Qt 5.13.2, KF
5.66.0, Mesa 19.3.2. I opened Konsole 19.2.1. I opened a second tab. I ran
coredumpctl gdb on a kwin_wayland crash which happened when logging out on the
previous boot. I reported those type of kwin_wayland crashes at
https://bugs.kde.org/show_bug.cgi?id=416147. The core dump file was 2.1 GB, and
it took a few minutes for coredumpctl gdb to decompress and process the core
dump. I ran bt in gdb to get a trace. Konsole stopped responding for about a
minute with Not Responding in the title bar. Konsole's colours faded. Konsole
disappeared. The trace in Dr. Konqi showed the error "The Wayland connection
broke. Did the Wayland compositor die?" in frame 9 of the crashing thread 1.
I've previously seen Konsole abort with that error as in my previous report
here. I've also seen that error for
plasmashell https://bugs.kde.org/show_bug.cgi?id=414116
ksysguard https://bugs.kde.org/show_bug.cgi?id=413901
system settings https://bugs.kde.org/show_bug.cgi?id=414118
The underlying problem might be in Qt particularly qtwayland.
-- Backtrace (Reduced):
#6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7 0x7f99fb711899 in __GI_abort () at abort.c:79
#8 0x7f99f9de6b25 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1907
#9 QMessageLogger::fatal (this=this@entry=0x7ffce5796200,
msg=msg@entry=0x7f99e8b2ee30 "The Wayland connection broke. Did the Wayland
compositor die?") at global/qlogging.cpp:888
#10 0x7f99e8a7e84b in QtWaylandClient::QWaylandDisplay::checkError
(this=) at /usr/include/qt5/QtCore/qlogging.h:91
--
You are receiving this mail because:
You are watching all bug changes.
