[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no 
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2015-10-14 8:33:47
Message-ID: bug-341497-17878-qLEqIGdUbW () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #39 from Thomas Lübking <thomas.luebking@gmail.com> ---
Fwwi, *every* single backtrace I've seen in this regard was a Qt internal
nullptr resolution.

The design was changed and left tons of unconditional (primary) screen accesses
in Qt behind and instead of going for the obvious and just add a dummy screen
(preserving source compatibility as well), they chose to "if
(QGuiApplication::primaryScreen()) { ... }" on every single occurrence.
Workloading approach, but not our problem at all.

Once Qt stops crashing by itself, there *might* popup KDE (and other Qt client)
code issues from "QWidget * QDesktopWidget::screen(int screen = -1)", but so
far, we didn't make it into client code because Qt crashed before.
If we see them once, we got to fix them then.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]