Created attachment 129713 [details] kritacrash.log This bug doesn't occur in stable version 4.3. It is easy to reproduce on 5.0.0-prealpha (git 23be7ef) and few earlier versions. STEPS TO REPRODUCE 1. run Krita 2. File -> new 3. Make sure the Layers docker is visible 4. Add layer 5. Drag it (or click on down-arrow) to send layer 2 below layer 1 6. Krita crash SOFTWARE/OS VERSIONS Krita Version: 5.0.0-prealpha (git 23be7ef), Qt version compiled: 5.12.8, loaded: 5.12.8.
I can't reproduce this with the Jun 27 5.0.0 prealpha (git 689fe92) Windows .zip package. There is a crash bug that has a similar trigger action but requires that the new image is created from previously copied content, using Ctrl+Shift+N: https://bugs.kde.org/show_bug.cgi?id=423473
Created attachment 129720 [details] settings for new document dialog that causes crash on my system Just checked with (git 689fe92) Windows .zip package. Crash is still present on my system, so I reset everything :) and make sure that nothing is on clipboard. I found that crash occurs when checking either: - Background: As canvas color or - Background: As fill layer in Create new document dialog Background: As raster layer - is fine
The oldest package I have on my computer is ga98fccf6ef. The bug is also present there.
I can confirm this for the Jun 27 5.0.0 prealpha (git 689fe92) Linux appimage. As noted in Comment 2 , it happens for background as Canvas Colour or as Fill Layer. You don't need to add a new layer. If you create a new multilayer image, moving any layer to the bottom of the layer stack will give the crash when it gets to the bottom. This now seems more similar to https://bugs.kde.org/show_bug.cgi?id=423473
It seems that the bug is gone at least in gc2b2b792c3. g05babe088f is fine too. I don't know about https://bugs.kde.org/show_bug.cgi?id=423473
This crash now does not happen on the Jul 23 5.0.0 prealpha (git c60995a) or the last successful Jul 20 4.3.1 alpha (git f119f41) appimages. It doesn't happen on those Jul 15 builds either. There must have been a mystery commit, which has also fixed: https://bugs.kde.org/show_bug.cgi?id=423473