Summary: | Falkon crash within Plasma Wayland session | ||
---|---|---|---|
Product: | [Applications] Falkon | Reporter: | Andreas Sturmlechner <asturm> |
Component: | general | Assignee: | David Rosca <nowrep> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | asturm |
Priority: | NOR | Keywords: | drkonqi, wayland-only |
Version First Reported In: | 3.1.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Andreas Sturmlechner
2020-04-13 11:36:41 UTC
Created attachment 127497 [details]
New crash information added by DrKonqi
falkon (3.1.0) using Qt 5.14.2
It just happened again - while trying to switch to a different tab.
-- Backtrace (Reduced):
#7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#8 0x00007fc2da8d655b in __GI_abort () at abort.c:79
#9 0x000056249ddf8fb0 in msgHandler(QtMsgType, QMessageLogContext const&, QString const&) (msg=..., context=..., type=<optimized out>) at /var/tmp/portage/www-client/falkon-3.1.0-r1/work/falkon-3.1.0/src/main/main.cpp:116
#10 msgHandler(QtMsgType, QMessageLogContext const&, QString const&) (type=<optimized out>, context=..., msg=...) at /var/tmp/portage/www-client/falkon-3.1.0-r1/work/falkon-3.1.0/src/main/main.cpp:99
#11 0x00007fc2dada7738 in qt_message_print(QtMsgType, QMessageLogContext const&, QString const&) (msgType=QtFatalMsg, context=..., message=...) at /var/tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/global/qlogging.cpp:1843
#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 |