https://bugs.kde.org/show_bug.cgi?id=426805

            Bug ID: 426805
           Summary: kritalcmsengine.dll causes Krita to crash at launch on
                    Lenovo Legion Y7000P
           Product: krita
           Version: 4.3.0
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Color models
          Assignee: krita-bugs-n...@kde.org
          Reporter: tyson...@tysontan.com
  Target Milestone: ---

Created attachment 131826
  --> https://bugs.kde.org/attachment.cgi?id=131826&action=edit
kritalcmsengine.dll crash log

There has been multiple report of Krita crashes at launch on a specific laptop:
Lenovo Legion Y7000P (2019). The kritacrash.log file revealed it to be caused
by kritalcmsengine.dll.

One of the reporters appeared to be a very experienced IT engineer. He
cooperated in a thorough troubleshoot that exhausted all my knowledge with no
success. According to his report, the same machine was able to run Krita until
he had to reinstall Windows 10 because his kid broke the system. It is now
running the latest Windows 10 2004, with all the updates and newest drivers
installed.

The machine might have some peculiar hardware/software configurations. It has a
NVIDIA GTX1660 GPU, the system listed 2 displays, with identical device name:
Lenovo Display 1920x1080 (It has a specific driver). I suspect one of them is
connected to Intel integrated GPU. I instructed him to change the display
driver to Generic PNP Display, but it didn't work.

In Windows 10's Color Management dialogue, only one display was listed, and it
has 3 ICM/ICC profiles attached. I instructed him to delete them and uncheck
"use my settings for this device", which didn't work either. We also repeat the
same procedure on System-wide settings, didn't work either.

For some reason, on Advanced tab of Windows Color Management dialogue, it was
using Relative Colormetric. I instructed him to changed it back to System
Default, it didn't work.

At that point, I exhausted all possible workarounds and decided to make this
report.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to