https://bugs.kde.org/show_bug.cgi?id=396509
--- Comment #14 from Rebecca Breu <rebe...@rbreu.de> --- I have the same issue. I'm on Debian Stable, using a Wacom tablet, and have been using Krita for a long while with this setup without any problems. The nightly build appimage 1519ff6 from Nov 17 was fine. Now with a nightly build 6dc2f8a from Dec 11, I get the layers issue. It doesn't happen all the time, but yeah, often when I add or try to move a layer, I will notice that the response becomes sluggish, and trying to save the image leads to the "Waiting for an image operation to finish" popup. None of the options presented lets me actually save my image, with or without the image operation Krita is supposedly waiting for, or get Krita out of that state. All I can do is kill Krita from my OS. Though I don't think it's actually maxing my CPU? I'd have to take a closer look. Another thing I've had happen with the Dec 11 build and not the Nov 17 is segfaults when confirming a transformation. Again, doesn't happen all the time, I can go transforming dozens of times, but it's often enough that it's disruptive. As I understand, with the nightly app images for Linux I cant't get any debug stuff/core dumps? I'd have to compile myself to help debugging the dev version? Anyway, I'm trying the build from yesterday now and see how it goes. FWIW, I've went through the commit messages on master to see if there's anything that looks like it could be the culprit for this behaviour, and all I found was the ocio update. On my end, I did one Debian update between then and now, attaching the log, just in case; so seeing that I'm not the only one with this problems I'm not sure it's relevant. -- You are receiving this mail because: You are watching all bug changes.
