Summary: | Color picker not working after creating a new layer | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Manga Tengu <mangatengu> |
Component: | Color Selectors | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ghevan, halla |
Priority: | NOR | Keywords: | triaged |
Version: | 4.4.5 | ||
Target Milestone: | --- | ||
Platform: | macOS (DMG) | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Manga Tengu
2021-07-28 19:08:15 UTC
Could you give more information on your session? Is Instant Preview on? Do you select the color instantly after adding a new layer?? How big or complex th eimage has to be? Do I need to be painting for a long session for it to trigger? Does this happen on master? I tried with a diverse files selection, and I could not reproduce the behaviour. Instant preview is disabled, Selecting the color is what blocks right after creating the new layer. Then I can do whatever, if I don't close the file, it won't work. Images are very simple (happened with a 2 layers image 4000x4000 px) Sessions were long yes. I didn't try on master and this is so sparse it could take a lot of time to say if it happens or not. That's also why you can't reproduce it easily. Or maybe I missed a detail. However, that's the limit of what I noticed. Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. I cannot reproduce this at all -- maybe my new mac is just too fast. I'm not sure what to do here: if we cannot reproduce the issue, we cannot fix it either. Lets set this as worksforme then, I cannot reproduce it on neither of the macs. It seems everything is fine for me.
Sorry but what is a worksforme exactly? I read this:
>>> Current definition of WORKSFORME in bugzilla is:
"
WORKSFORME
All attempts at reproducing this bug were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the bug can be reopened.
"
I mean in 5.0.2 |