Bug 442405

Summary: color mismatch
Product: [Applications] krita Reporter: kdesomeuser <fodmo>
Component: * UnknownAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: halla, tamtamy.tymona
Priority: NOR    
Version First Reported In: 4.4.8   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: log text from 4.4.8 and 5.0

Description kdesomeuser 2021-09-14 00:15:23 UTC
Created attachment 141527 [details]
log text from 4.4.8 and 5.0

STEPS TO REPRODUCE
1. set red color
2. draw

OBSERVED RESULT
drawn in blue color

EXPECTED RESULT
drawn in red color

Windows 7

video in google drive: https://drive.google.com/file/d/19SrtrpUqTj6bfGOAK8Di764SM5zWtDy2/view?usp=sharing
in video:
- try versions 4.4.8 and 5.0
- comparing with GIMP
- deleting krita files in %localappdata%, %appdata%
Comment 1 Halla Rempt 2021-09-14 06:39:00 UTC
Your graphics driver is broken, which means the R and B channels are swapped. You're also using Windows 7, which we don't support anymore: it's only with Windows 7 that there are still drivers with this bug. Please update to a newer version of Windows or Linux.
Comment 2 kdesomeuser 2021-09-14 16:55:14 UTC
(In reply to Halla Rempt from comment #1)
> Your graphics driver is broken, which means the R and B channels are
> swapped. You're also using Windows 7, which we don't support anymore: it's
> only with Windows 7 that there are still drivers with this bug. Please
> update to a newer version of Windows or Linux.

thank you.
- is GIMP using other drivers?
- older versions of Kryta won't have this problem? How solve problem in older Krita versions which support Windows 7?
Comment 3 kdesomeuser 2021-09-14 17:25:46 UTC
looks like Windows 7 has nothing to do with it. This can happen in Windows 10 too, based on https://www.reddit.com/r/krita/comments/c2je5y/does_anyone_have_a_fix_for_this_inverse_color_bug/
Comment 4 Halla Rempt 2021-09-14 19:03:00 UTC
Gimp doesn't use the gpu, so gimp isn't affected. You can disable canvas acceleration in Krita to work around the problem, but you will miss some functionality.
Comment 5 Tiar 2021-09-14 20:38:35 UTC
For a quick fix, change from ANGLE (DirectX) to OpenGL or the other way around in Configure Krita -> Display. That will allow you to still use Canvas Acceleration and won't slow down Krita as much as not using any acceleration.
You can also update your graphics card driver, and if it doesn't help, write to the manufacturer that either their ANGLE or OpenGL (I don't remember which is more often at fault) driver is incorrect in regard to color channels.
Comment 6 kdesomeuser 2021-09-18 03:08:04 UTC
(In reply to Tiar from comment #5)
> For a quick fix, change from ANGLE (DirectX) to OpenGL or the other way
> around in Configure Krita -> Display. That will allow you to still use
> Canvas Acceleration and won't slow down Krita as much as not using any
> acceleration.
> You can also update your graphics card driver, and if it doesn't help, write
> to the manufacturer that either their ANGLE or OpenGL (I don't remember
> which is more often at fault) driver is incorrect in regard to color
> channels.
there is no "OpenGL" item =( https://i2.paste.pics/143f74d4c69be8e013fe3fdd77807a6f.png
is it possible to get the OpenGL acceleration for Krita in this system? I understand that the questions are not the right place .. but who could help me =(

thank you
Comment 7 Halla Rempt 2021-09-18 06:45:43 UTC
No, your Windows is too old. We don't support Windows 7 anymore.
Comment 8 kdesomeuser 2021-09-18 15:03:42 UTC
(In reply to Halla Rempt from comment #7)
> No, your Windows is too old. We don't support Windows 7 anymore.

what to do if I update windows and the error is the same?

example: https://www.reddit.com/r/krita/comments/c2je5y/does_anyone_have_a_fix_for_this_inverse_color_bug/
Comment 9 kdesomeuser 2021-09-26 21:31:56 UTC
someone in support believes that the problem is not on the side of ATI/AMD
https://i2.paste.pics/203d10ca8e73d0adbeff7251378a2170.png
is it possible to somehow confirm that the problem is on their side?
What if 
>>This issue could be caused due to driver conflict, registry corruption etc.