Created attachment 109038 [details] The file with the problem. In Windows 10 x64, with Pre-Alpha 2, there's a file that I have where if you do ungroup 'Dithering Support' or delete 'Layer 202' found in the main layer group named 'filtered image', the 'o' layer group is altered. You can confirm that by noticing there is a higher range of difference when comparing the o layer with the reference layer using the orange layer as the only visible layer. I don't think this was suppose to happen as I don't remember using anything other than the main group layer as instanced layers for the o group layer. All one can do by this point, is literally only hide Layer 'Layer 202' under 'filtered image'.
Also, when comparing the difference, use the brightness/contrast to actually see a lot more difference.
I'm sorry, but you really have to be much clearer: I cannot understand your bug report at all.
*** Bug 387269 has been marked as a duplicate of this bug. ***
Not really a bug after checking again. If you care for more details on why I thought it was a bug, you can read the rest of the post. I checked again, and the 'o' layer group which is one of the main group did contained a clone layer of one of the sub-group under 'filtered image' which is named 'dithering support'. Manipulating that 'dithering support' group would affect the 'o' layer group. That was a mistake which was taken as a bug. Sorry, I haven't noticed that mistake at all despite checking many time, but only confirmed it after checking one of the disabled subgroup under the 'o' group. To clarify: The main group are: -i -o -s -Border -Filtered Image -Reference And the secondary sub group for "Filtered Image" was: -Dithering Support In Dithering Support: -Layer 202 In the 'o' group, there was many instanced layers of the 'Filtered Image'. Only one of them was 'Dithering Support'. That wasn't noticed for a long while. Manipulating the 'Dithering Support' ends up altering the 'o' main group because one of the instanced layer was 'dithering support' group which is a subgroup of 'Filtered Image' which is the main group.
I believed I have commented on here before, but it didn't show up. I think there has to be a way to see networks of clone layers in order to make it easier on users to work with many clone layers to avoid this error. But I don't think this is a valid report, but it does reveal the very issue of working on many clone layers.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!