Bug 408068

Summary:	4.2 Semi transparent U.I.
Product:	[Applications] krita	Reporter:	Neptunian <rolffromm>
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	dimula73, ghevan, halla, manutronics, wingfield.owl
Priority:	NOR
Version:	4.2.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:

Description Neptunian 2019-05-29 13:19:45 UTC

SUMMARY
Installed Krita 4.2 (104Mb 64 bit windows install) on windows 7 64 bit, and when launching the application, the entire window is semi transparent... It was installed normally over the old 1.7 install, at first I installed to a different partition on my ssd, then reinstalled to C:, then redownloaded the exe, reinstalled, restarted my computer, and the U.I. is still transparent. reinstalled 4.1.7 and had no issues.

STEPS TO REPRODUCE
1. install 4.2
2. ???

OBSERVED RESULT
https://imgur.com/a/zkle8TE

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 7 64 bit service pack 1
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Halla Rempt 2019-05-29 14:47:20 UTC

Please try to reset Krita's settings and try 4.2.0 again. If that doesn't make a difference, provide the output of the System Information For Bug Reports dialog which you can find in the Help menu.

Comment 2 Neptunian 2019-05-30 12:36:49 UTC

I didn't reset the setting but managed to fix it by changing out of sRGB(8 bit) when using OpenGL, or by using Direct3D 11 via ANGLE. (My monitor is not HDR)

Comment 3 vanyossi 2019-05-30 16:16:18 UTC

Marking as fixed.

On windows ANGLE should be the preferred way to add canvas acceleration anyways.

Comment 4 Halla Rempt 2019-06-03 05:51:13 UTC

*** Bug 408228 has been marked as a duplicate of this bug. ***

Comment 5 Halla Rempt 2019-06-03 07:47:01 UTC

This also happens on Linux, it does need looking into.

Comment 6 Dmitry Kazakov 2019-06-03 08:06:00 UTC

Bug 408225 seem to be related, but still a different bug and will have to be fixed differently.

Comment 7 Neptunian 2019-06-06 01:36:30 UTC

Same behavior on 4.2.1. Switching to Direct3D fixes it.
https://imgur.com/mKRTswv
https://imgur.com/S5h4nrG

Comment 8 Halla Rempt 2019-06-06 08:18:24 UTC

This bug report is about linux, so your comment probably should have gone to https://bugs.kde.org/show_bug.cgi?id=408225

Comment 9 Neptunian 2019-06-06 16:54:06 UTC

(In reply to Boudewijn Rempt from comment #8)
> This bug report is about linux, so your comment probably should have gone to
> https://bugs.kde.org/show_bug.cgi?id=408225

Uh, did I set it as linux? If I did, sorry, it's a windows 7 problem.

Comment 10 Halla Rempt 2019-06-21 12:04:17 UTC


*** This bug has been marked as a duplicate of bug 408089 ***

Comment 11 Halla Rempt 2019-06-24 07:14:15 UTC

*** Bug 409061 has been marked as a duplicate of this bug. ***