Bug 329006 - Duplicating layer group causes some child layers to become uneditable
Summary: Duplicating layer group causes some child layers to become uneditable
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Layer Stack (show other bugs)
Version: 2.8 Pre-Alpha
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: release_blocker
Depends on:
Blocks:
 
Reported: 2013-12-19 15:54 UTC by mc3dkid
Modified: 2014-01-28 22:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
This file shows the original layer group and the duplicate group above it with the non functional duplicate layer. (5.46 KB, application/x-krita)
2013-12-19 15:54 UTC, mc3dkid
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mc3dkid 2013-12-19 15:54:46 UTC
Created attachment 84172 [details]
This file shows the original layer group and the duplicate group above it with the non functional duplicate layer.

After duplicating a layer group many but not all layers become uneditable.  The only work around is to duplicate these layers, convert them into another kind of layer and then delete them.

Steps to reproduce:
1 Create new file
2 Create a new layer group
3 move the default layer into the group
4 create a new layer in the group
5 right click on the group and select duplicate
Comment 1 Dmitry Kazakov 2013-12-19 20:21:36 UTC
Well, I have such a feeling that the reason why you cannot see the changes when painting on the source layers is that you copied the fully opaque. The opaque layer in the second group just hides what you paint below in the first group. If you change the visibility of it, you'll see your strokes :)

I'll mark the bug as WAITINGFORINFO, please check if I got the problem correctly.
Comment 2 mc3dkid 2013-12-19 20:29:34 UTC
Well, that's not it.  I have this problem a lot because I work with a lot of layers and groups of layers.  After opening the example file I sent you earlier it appears that the layers in the saved file are now fine.
Comment 3 mc3dkid 2013-12-19 20:30:59 UTC
When this problem occurs the ability to delete the layer using the minus button becomes disabled as well.
Comment 4 mc3dkid 2013-12-19 20:38:22 UTC
Galdurnit!  Reproducibility is hard to nail down with this.  I thought I had it but it doesn't seem so...
Comment 5 mc3dkid 2013-12-19 20:41:56 UTC
CRAZY!  I just figured out the key ingredient.  You must complete the steps I mentioned using... A TABLET PEN!  Also, I can confirm that the layer status is fixed after saving closing and reopening the file.
Comment 6 Dmitry Kazakov 2013-12-19 21:10:10 UTC
Switch back to Unconfirmed then
Comment 7 Dmitry Kazakov 2013-12-22 10:39:00 UTC
It is not reproducible on Linux. Probably, Windows-specific, but I didn't test on windows yet.
Comment 8 Halla Rempt 2014-01-02 13:19:44 UTC
I can confirm on Windows.
Comment 9 Dmitry Kazakov 2014-01-02 20:28:50 UTC
Hi, mc3dkid!

I tested on Windows with both mouse and tablet and still cannot reproduce it. The only suspicious thing is that  the fully opaque layer in the second group is covering the first group so the results of the painting on them is unseen. But this is perfectly expected thing. I still can remove any layer with the minus sign.

Could you please update to the latest Krita version, and, if this bug still persists, make a video showing the bug?
Comment 10 Dmitry Kazakov 2014-01-02 20:29:58 UTC
Here are the links to the newest builds:

http://heap.kogmbh.net/downloads/krita_x64_2.7.9.3.msi
http://heap.kogmbh.net/downloads/krita_x86_2.7.9.3.msi
Comment 11 mc3dkid 2014-01-03 20:08:10 UTC
Just tested with the latest build you linked to and I still get the same issue.  Following the above steps I can get Krita to create uneditable Layer Groups even.
Comment 12 Dmitry Kazakov 2014-01-03 21:06:40 UTC
Hi, mc3dkid! Could you please make a video of it?
Comment 13 Halla Rempt 2014-01-28 21:13:29 UTC
I made http://www.valdyas.org/~boud/bug_329006_1.avi  -- I followed the exact steps, and I cannot reproduce any locking of layers... This is with the current x64 build of krita on Windows 7.
Comment 14 mc3dkid 2014-01-28 21:34:43 UTC
When using the latest I can no longer reproduce this bug by following the steps I listed.  Since the latest build is not using my old preferences and brushes (is there a reason for this?) I haven't used it much to test more thoroughly.
Comment 15 Halla Rempt 2014-01-28 22:24:47 UTC
I've been trying hard for some time to make sure that all settings were saved in Users\USER\AppData\Roaming\krita, instead of various .kde or kde directories in AppData. If you check the AppData folder and a share\apps\krita and share\config\kritarc in there, you could copy those to Users\USER\AppData\Roaming\krita. Take care, though, to remove the "input" folder!

That should restore your settings and brushes, except for changes to the zoom or pan actions and so on. The reason for that is that we've been changing the code for that a bit, so the old settings files from earlier betas cannot be loaded anymore.