https://bugs.kde.org/show_bug.cgi?id=358722
Thomas Lübking <thomas.luebk...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0 |1
--- Comment #4 from Thomas Lübking <thomas.luebk...@gmail.com> ---
Workspace holds a pointer pointing Compositor::self() which is nuked by
Application::destroyCompositor() (so m_compositor in workspace now dangles)
This was previously prevented by noop'ing destroyCompositor() as long as there
was Workspace::self() and boke with
commit 1998d5ac1ad92011505f0e00761ccc618099fa19
Date: Tue Nov 10 08:52:40 2015 +0100
[wayland] Improve tear-down to not crash if X11 applications are still
around
We need to destroy the compositor after Xwayland terminated and after
the internal Wayland connection is destroyed. This means when destroying
the Workspace we may no longer destroy the Compositor at the same time.
Also we need to ensure that other tear down functionality doesn't call
into the no longer existing internal client connection.
With this change kwin doesn't crash when exiting with Wayland and/or
X11 windows still open.
.......
void Application::destroyCompositor()
{
- if (Workspace::self()) {
- // compositor is destroyed together with Workspace
- return;
- }
delete Compositor::self();
}
.......
--
You are receiving this mail because:
You are watching all bug changes.
