Bug 415616

Summary: Install problem on Windows 10. GUI severely corrupted
Product: [Applications] kdenlive Reporter: Tom Courtney <tpcourtney>
Component: Setup & InstallationAssignee: Vincent PINON <vpinon>
Status: RESOLVED FIXED    
Severity: major CC: fritzibaby, gamedude1403, tpcourtney, zerossb
Priority: NOR Flags: fritzibaby: timeline_corruption+
Version First Reported In: 19.12.0   
Target Milestone: ---   
Platform: Other   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Corrupt GUI after installation

Description Tom Courtney 2019-12-27 17:08:40 UTC
Created attachment 124742 [details]
Corrupt GUI after installation

SUMMARY
INstalled KDENLIVE 19.12.0.  GUI is large.  Can't see menus. 

STEPS TO REPRODUCE
1. INstall 19.12.0
2. Open kdenlive
3. Immediately see the problem

OBSERVED RESULT
SCreen is magnified.  Can't see menu. See attachment. 

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: WIndows 10


ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2019-12-28 11:57:08 UTC
*** Bug 415622 has been marked as a duplicate of this bug. ***
Comment 2 emohr 2019-12-29 17:07:40 UTC
Your Intel graphic card driver was updated. Move the mouse to the top. The menus are showing up. Try to reach settings -> openGL backend -> enable OpenGLES. Restart Kdenlive. This should solve your Intel graphic driver issue. 

Maybe this statement helps: https://forum.kde.org/viewtopic.php?f=265&t=161309#p425882
Comment 3 Tom Courtney 2019-12-29 17:34:03 UTC
Thank you, thank you, thank you!  That workaround worked. :)
Comment 4 emohr 2019-12-30 10:27:44 UTC
Thank you for the feedback. Glad to hear it works. 

I updated the download page and the Kdenlive manual with this solution.

We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.
Comment 5 zerossb 2019-12-30 12:06:56 UTC
Thank you very much, I followed the steps right and it worked!
Comment 6 Patrick Silva 2019-12-30 23:13:16 UTC
*** Bug 415717 has been marked as a duplicate of this bug. ***