https://bugs.kde.org/show_bug.cgi?id=353578
--- Comment #8 from tobijk <tobias.johannes.klausm...@mni.thm.de> --- (In reply to Marco Martin from comment #7) > can you reproduce and get the console output as well when the assert gets > hit? It is reproducible and the output is (already stated above): Useful console output: ... requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 2286, resource id: 0, major code: 21 (ListProperties), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 2336, resource id: 0, major code: 21 (ListProperties), minor code: 0 Maybe it is important to say: This is a notebook connected to an external monitor, where the internal monitor is disabled, thus when disabling the external monitor, the last output goes away. _Maybe_ the unexisting screen 0 is the internal notebook lcd... -- You are receiving this mail because: You are watching all bug changes.
