https://bugs.kde.org/show_bug.cgi?id=413758
--- Comment #7 from [email protected] --- I just checked with KWin 5.18.1 and while it does not seem to actually crash, current behavior still results in a useless system once the external screen gets disconnected. It now behaves like this: 1) Start with no external screens connected, OK 2) Connect external screen, OK 3) Output moves to external screen, internal screen gets disabled, OK 4) Disconnect external screen 5) Internal screen stays dark and there is no way how to resurrect the machine bar killing KWin an restarting the whole session. I tried to attach gdb to KWin when it gets into this state but I don't think the output is particularly useful: (gdb) bt #0 0x00007f9d9ca87bb6 in ppoll () at /usr/lib/libc.so.6 #1 0x00007f9d9d065f73 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x00007f9d9d06763d in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #3 0x00007f9d95dd0e8e in QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so #4 0x00007f9d9d0104cc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #5 0x00007f9d9d0184d6 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #6 0x000056375e44931c in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /home/madcat/abs/kwin/trunk/src/kwin-5.18.1/main_wayland.cpp:676 -- You are receiving this mail because: You are watching all bug changes.
