https://bugs.kde.org/show_bug.cgi?id=461429
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |BACKTRACE
Status|REOPENED |NEEDSINFO
--- Comment #6 from Nate Graham <n...@kde.org> ---
> Nov 14 10:11:36 laurenz-ManjaroKDE kaccess[2134]: The X11 connection broke
> (error 1). Did the X11 server die?
> Nov 14 10:11:36 laurenz-ManjaroKDE systemd[1770]:
> app-kaccess@autostart.service: Failed with result 'exit-code'.
> Nov 14 10:11:37 laurenz-ManjaroKDE kwin_wayland[1810]: QtDBus: cannot relay
> signals from parent QObject(0x56044f5c3ba0 "") unless they are emitted in the
> object's thread QThread(0x56044f30a1f8 "libinput-connection"). Current thread
> is QThread(0x56044f25d210 "").
> Nov 14 10:11:37 laurenz-ManjaroKDE kwalletd5[1789]: The Wayland connection
> broke. Did the Wayland compositor die?
> Nov 14 10:11:37 laurenz-ManjaroKDE kwalletd5[1789]: The Wayland connection
> broke. Did the Wayland compositor die?
> Nov 14 10:11:37 laurenz-ManjaroKDE kded5[1911]: The Wayland connection broke.
> Did the Wayland compositor die?
> Nov 14 10:11:37 laurenz-ManjaroKDE plasmashell[1949]: The Wayland connection
> broke. Did the Wayland compositor die?
Yep that tells us that kwin_wayland died for some reason. Sadly it's a known
and unavoidable issue that when kwin_wayland crashes, all apps crash too (see
https://bugreports.qt.io/browse/QTBUG-85631). But we still need to know why
KWin crashed. For that, we need a backtrace of the KWin crash itself. You may
be able to retrieve it with `coredumpctl`. See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
--
You are receiving this mail because:
You are watching all bug changes.
