Created attachment 120706 [details]
gdb thread apply all bt
After using the select opaque feature and adjusting a vector line, the canvas stopped responding to paint type inputs. Whenever I tried to drag in paint mode (ex: after pressing b), the cursor wouldn't move from the initial point from where I had touched the pen to my tablet. I could use the angle measure tool just fine, but couldn't do any paint related thing. It looks like I may have tried to select the text tool after this, which caused krita to crash.
This is version 4.2.1 git-01440fb that I compiled with a build type of RelWithDebInfo. I saved the core file and binary, and if they would be helpful, I can make it available to download. (It's 130MB compressed).
STEPS TO REPRODUCE
1. Make canvas not respond to paint type inputs
2. Select text tool
Linux/KDE Plasma: Ubuntu 19.04 / Linux 5.0.0-16-generic
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Attached is the 'thread apply all bt' for the core dump created by the reported crash.
It's likely that the reason I wasn't able to select anything on the canvas was that it was a grouped layer, so that isn't an issue.
Could you check with the latest nightly build? I've seen Dmitry fix a crash with a very similar backtrace.
(In reply to Boudewijn Rempt from comment #2)
> Could you check with the latest nightly build? I've seen Dmitry fix a crash
> with a very similar backtrace.
I did try painting on a layer group, and then selecting the text tool, but krita didn't crash. Unfortunately, I don't remember the steps I did precisely enough to be able to reproduce it. It may not even be that sort of crash.
None of the crashes I have core dumps for so far can be easily reproduced. I know this makes debugging more difficult and bugs reports less useful, which is why I am using a RelWithDebInfo build and have a core file I can provide instead. Would using a debug build (or anything else) be more helpful?
I enabled the Settings->Configure krita->Miscellaneous->Enable logging for bug reports after this bug report, but it doesn't seem like it would have given any better hints.
No... A debug build wouldn't be more useful.
The bug was fixed in this commit:
*** This bug has been marked as a duplicate of bug 407554 ***