Summary: | Konsole on Wayland crashes on large output of dots and numbers | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Wilhelm Wijkander <kdebugzilla> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | justin.zobel |
Priority: | NOR | ||
Version: | 19.12.1 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Wilhelm Wijkander
2020-05-06 17:43:54 UTC
#6 QMessageLogger::fatal (this=this@entry=0x7fffd70c5ba0, msg=msg@entry=0x7ff994ac00b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that the compositor crashed. Due to a Qt issue, when this happens, the app using it will crash too. KDE developers submitted a fix, but sadly it was not merged. See https://codereview.qt-project.org/c/qt/qtwayland/+/308984. Until we get better handling of this in Qt, the best we can do is debug why the compositor crashed in the first place. So can you please get a backtrace of the crash in kwin_wayland and then file a new bug report with it on kwin | wayland-generic? Thanks! You may be able to use the `coredumpctl` utility to retrieve the backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl |