e30e358ce6
Amends 2c67d47ea15c6dc34cc20d8fbdb406efb19f11d7, after which we emitted the signal, as the setParent(nullptr) call in the destructor would call back into the QDockWidget::event override. That change was correct, but we are now emitted signals while in the destructor, after a potential subclass destructor was already completed. This crashed applications that had slots connected to those signals. While arguably an application problem (PMF connections need to be disconnected explicitly), we can avoid this regression by blocking the emission of that signal when already in the destructor. Fixes: QTBUG-136485 Pick-to: 6.9.1 6.8 6.5 Change-Id: I6d5e98136beedc94c22287ccfd1198dd80f4f95e Reviewed-by: Axel Spoerl <axel.spoerl@qt.io> (cherry picked from commit 7869593119ffaea6002e6668814af159a2077398) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.