https://bugs.kde.org/show_bug.cgi?id=411202
Lynx3d <l...@aspect-design.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |l...@aspect-design.de
--- Comment #5 from Lynx3d <l...@aspect-design.de> ---
This crash still puzzles me, all my attempts to find the cause failed so far.
First of all, I also have the issue with the 4.2.x appimages on (K)Ubuntu
18.04, but only with those.
I tried self-compiled master, 4.2.x from krita lime PPA, 4.1.x appimages (that
for some reason fail to use OpenGL) and 4.0.4 appimage. I couldn't get any of
them to crash, leading me to believe the issue is somehow related of Qt 5.12
used for the 4.2 builds.
What's also strange is that it's only the non-modal dialog used to select
foreground color, the background color dialog is not crashing here.
I also want to add that for me, the foreground color dialog doesn't render at
all anymore once it had been closed until you resize the window. Just the
window frame/shadow renders on opening, but inside is just frozen to whatever
happened to be on screen already until resizing it. Resizing the dialog like
mad seems to be the easiest way to make it crash.
However, all version I tested sometimes print this a couple of times on
resizing, but am not sure from which widget it comes from:
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::setRenderHint: Painter must be active to set rendering hints
So something in code must also be wrong, but so far I don't see how that could
be related to random crashes deep in the guts of Qt, doesn't even seem
correlated in time.
If I could at least make a build myself that crashes, I could test if my branch
with the reworked code still has this issue or not...
--
You are receiving this mail because:
You are watching all bug changes.
