Bug 440368 - Color picker not working after creating a new layer
Summary: Color picker not working after creating a new layer
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Color Selectors (show other bugs)
Version: 4.4.5
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2021-07-28 19:08 UTC by Manga Tengu
Modified: 2022-06-29 09:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manga Tengu 2021-07-28 19:08:15 UTC
SUMMARY
Sometimes when selecting the color (with command pressed) the eyedropper doesn't work, there is only one swatch of color next to the cursor and the second one (the one that shows the selection) doesn't show. Then the color doesn't change.
Also the overview bugs and doesn't show the canvas.

This happens rarely and randomly, so it was a pain to find the trigger, but it happened to me twice right after creating a new layer so I guess this is it.

My workaround is to close the file (no need to close krita) and reopen it.


STEPS TO REPRODUCE
1. Create a new layer
2. Try to pick some color
3. This is very random and sparse

macOS: 11.2.3 (20D91)
Comment 1 vanyossi 2021-08-02 18:54:00 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.
Comment 2 Manga Tengu 2021-08-03 07:55:01 UTC
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.
Comment 3 Bug Janitor Service 2021-08-04 04:34:06 UTC
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.
Comment 4 Halla Rempt 2022-06-28 11:30:12 UTC
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.
Comment 5 vanyossi 2022-06-28 23:25:34 UTC
Lets set this as worksforme then, I cannot reproduce it on neither of the macs.
Comment 6 Manga Tengu 2022-06-29 09:27:00 UTC
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.
"
Comment 7 Manga Tengu 2022-06-29 09:27:21 UTC
I mean in 5.0.2