[kwin] [Bug 381461] Two overlapping QMessageBox instances causes KWin to lock up

https://bugs.kde.org/show_bug.cgi?id=381461 --- Comment #14 from Vlad Zahorodnii --- With if (ac && ac->isModal()) { if (hasTransient(ac, true)) { return false; } } in allowWindowActivation(), kwin is no longer knocked out by the demo application, but I'm

[kwin] [Bug 381461] Two overlapping QMessageBox instances causes KWin to lock up

https://bugs.kde.org/show_bug.cgi?id=381461 alex...@gmx.net changed: What|Removed |Added CC||alex...@gmx.net -- You are receiving this

[kwin] [Bug 381461] Two overlapping QMessageBox instances causes KWin to lock up

https://bugs.kde.org/show_bug.cgi?id=381461 --- Comment #13 from Christoph Feck --- Running the attached testcase, I also observed the weird behavior. Depending on the order I try to close the windows, I got 100% CPU usage (distributed between all processes), not being able to

[kwin] [Bug 381461] Two overlapping QMessageBox instances causes KWin to lock up

https://bugs.kde.org/show_bug.cgi?id=381461 --- Comment #12 from Thomas Lübking --- Doesn't really knock out fluxbox, but once you pass focus to the "wrong" dialog, they apparently start a race on the window focus and you cannot pass it at will. The reason seems to be

[kwin] [Bug 381461] Two overlapping QMessageBox instances causes KWin to lock up

https://bugs.kde.org/show_bug.cgi?id=381461 Jan Kundrát changed: What|Removed |Added CC||j...@kde.org, |