Bug 442676 - Color selector will not update if green and blue values are the same if using color picker
Summary: Color selector will not update if green and blue values are the same if using...
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Color Selectors (other bugs)
Version First Reported In: 4.4.8
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2021-09-19 01:16 UTC by Wontoon
Modified: 2021-09-26 06:55 UTC (History)
3 users (show)

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


Attachments
A *.kra file with colors laid out so you can see the bug for yourself. (712.54 KB, application/x-krita)
2021-09-19 01:16 UTC, Wontoon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wontoon 2021-09-19 01:16:19 UTC
Created attachment 141692 [details]
A *.kra file with colors laid out so you can see the bug for yourself.

SUMMARY
When using the color picker on a specific range of colors, the color selector will remain on its previous hue. An example problem color that will trigger this bug is (208, 26, 26); my testing seems to show that the bug appears if the green and blue values are the same, but not if the green and blue values are the same. Note that I use HSV, but the bug seems to be present within the other ones (HSL, etc).

STEPS TO REPRODUCE
1. Place the color on the canvas, with the green and blue values being the same.
2. Select the color from any other color that does .
3. Profit.

OBSERVED RESULT
What happens is that the hue will shift on the outer ring, but not in the square (and it treats it as the previous hue, so the bug is not visual). Note that I'm using the configuration where you have the ring and the square inside of it, second one in the grid of options that lets you choose the style (values darken toward the bottom half). The bug is visible throughout all settings, however. 

EXPECTED RESULT
The hue should also change in the color selector; in my case, from any color to the red hue.

SOFTWARE/OS VERSIONS
Windows: Windows 10
macOS: N/A
Linux/KDE Plasma: N/A
(available in About System)
KDE Plasma Version: --
KDE Frameworks Version: --
Qt Version: --

ADDITIONAL INFORMATION
Attached a file with the colors in question. Use the color selector to pick a "good color" and then select a "problem color".
Comment 1 Halla Rempt 2021-09-19 09:23:32 UTC
Sorry, but even with the test file, I cannot reproduce this. I have checked both the dedicated color picker tool as well as the ctrl-click color picker of the freehand tool. I enabled the Specific Color Selector so I could see the numbers of the colors, and they all changed properly.
Comment 2 Lynx3d 2021-09-19 13:20:43 UTC
It sounds a lot like a duplicate of bug 437625, which is fixed in master for a while now.

It wasn't backported to 4.x though, since no more 4.x releases were planned...
Comment 3 Wontoon 2021-09-19 22:17:15 UTC
(In reply to Halla Rempt from comment #1)
> Sorry, but even with the test file, I cannot reproduce this. I have checked
> both the dedicated color picker tool as well as the ctrl-click color picker
> of the freehand tool. I enabled the Specific Color Selector so I could see
> the numbers of the colors, and they all changed properly.

Odd. I can consistently reproduce the bug on my end, even as I'm typing this comment in version 4.4.8. If need be I can find some screen recording software and show the bug in action.

Also going to raise the possibility of it being an OS-related bug, if you're not using Windows. I've had Krita just break when selecting colors after a Windows Update, but the devs pushed out an update shortly after and fixed it. Plus I did get pushed a Windows Update a couple of days ago, hence the possibility. :Oc
Comment 4 Halla Rempt 2021-09-20 09:10:46 UTC
Ah, I only tested on Linux.
Comment 5 Halla Rempt 2021-09-20 12:02:24 UTC
Okay, I tested on Windows now as well, and I still cannot reproduce the issue.
Comment 6 Tiar 2021-09-23 19:28:20 UTC
@Wontoon please check Krita 5.0 beta 1 too? First you need to backup your configuration and resources, here's the info how: https://krita-artists.org/t/help-krita-improve-with-structured-beta-testing-of-the-new-resource-system-in-krita-5-0/28779#before-you-start-how-to-back-up-things-5
Comment 7 Wontoon 2021-09-25 19:42:16 UTC
(In reply to Tiar from comment #6)
> @Wontoon please check Krita 5.0 beta 1 too? First you need to backup your
> configuration and resources, here's the info how:
> https://krita-artists.org/t/help-krita-improve-with-structured-beta-testing-
> of-the-new-resource-system-in-krita-5-0/28779#before-you-start-how-to-back-
> up-things-5

Heya! My apologies for the late response; got overwhelmed by a few things. But, I did take the time to test to see if the bug is in the recent nightly build of Krita 5.0.0-beta1 (git 0ff34e9) on Windows, and I can happily confirm that the bug is NOT present in that build, at least.
Comment 8 Bug Janitor Service 2021-09-26 04:35:42 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 9 Halla Rempt 2021-09-26 06:55:03 UTC
Okay, thanks for checking!