Summary: | KWin crashes after pluggin in external monitor, and then hitting CTRL+TAB | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Jeppe Bundsgaard <jeppe> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | pfeiffer |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.3.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jeppe Bundsgaard
2015-09-24 06:24:34 UTC
*** This bug has been marked as a duplicate of bug 341497 *** Even though this is indeed a duplicate of bug 353122, I'm wondering if isn't possible to add a workaround for this scenario. Reason: the other crashes appear instantaneously when changing the display configuration where for a short moment no screen is available. The crash in this report may happen way later, when the screen configuration is all well. I suppose that something in the Alt-Tab box is cached from the previous display configuration, which becomes invalid later, leading to the crash. Is it possible to detect that situation and simply discard and recreate the invalid objects when pressing Alt-Tab? > The crash in this report may happen way later, when the screen configuration is all well.
The QXcbWindow::screen() on the *just created* QXcbWindow is 0x0, there's no chance to workaround that from KWin or anything else (likely because the applications primary screen is "still" 0x0)
The 0x0 screen is a major issue that pops up all over the Qt5 code (so it's indeed likely not an exact dupe, but the upstream bug also groups all bugs itr.)
|