Summary: | Crash when trying to set window rules | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | David Edmundson <kde> |
Component: | rules | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | isma.af |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | unspecified | Flags: | thomas.luebking:
ReviewRequest+
|
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
URL: | https://git.reviewboard.kde.org/r/117738/ | ||
Latest Commit: | Version Fixed In: | 5.19 | |
Sentry Crash Report: |
Description
David Edmundson
2014-04-23 11:40:21 UTC
#12 0x00007ff2834c1f2a in KWin::DetectDialog::readWindow (this=0x248de10, ... #11 KWin::DetectDialog::executeDialog (this=this@entry=0x248de10) #6 KWin::DetectDialog::selectedClass (this=0x0) -> emit detectionDone(exec() == KDialog::Accepted); evil QDialog::exec() condition - needs QPointer guard. I'm really curious - do you know how you managed to do this? You would eg. "somehow" closed the dialog (but that's hardly possible in this condition - except for explicit dbus call) You should have only be able to interact with the keyboard. Nothing DBus, just clicking. I may have had a delay on the detect window properties. I can't reproduce it when trying here now. I'd consider this as fixed now we don't have this dialog |