Bug 427601

Summary: Impossible to load the right User Interface on stand alone version
Product: [Applications] kdenlive Reporter: romainlouzier28
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED WORKSFORME    
Severity: critical CC: fritzibaby, snd.noise
Priority: NOR Flags: fritzibaby: timeline_corruption+
Version First Reported In: 20.08.2   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: User interface screenshot

Description romainlouzier28 2020-10-12 16:52:06 UTC
Created attachment 132302 [details]
User interface screenshot

SUMMARY
Impossible to load the right User Interface on stand alone version
During the first utilisation of the product it worked

SOFTWARE/OS VERSIONS
Windows: 10
KDE 20.08.2
Comment 2 romainlouzier28 2020-10-14 06:21:02 UTC
Thank you very much solution 2 works !

Romain 


> Le 12 oct. 2020 à 20:56, emohr <bugzilla_noreply@kde.org> a écrit :
> 
> https://bugs.kde.org/show_bug.cgi?id=427601
> 
> emohr <fritzibaby@gmx.net> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Flags|                            |timeline_corruption+
>                 CC|                            |fritzibaby@gmx.net
> 
> --- Comment #1 from emohr <fritzibaby@gmx.net> ---
> Please follow this steps:
> https://userbase.kde.org/Kdenlive/Manual/Windows_Issues#Intel_graphic_card_driver
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 3 emohr 2020-10-14 16:24:10 UTC
To solve the issue following question: 

So you are saying that you have done step 2 only. Correct? 

Which "openGL backend" setting do you have now. DirectX? 

Does it work with all "openGL backend" settings as long as you have no [misc] section in kdenliverc?
Comment 4 farid 2021-03-07 12:12:08 UTC
Can you provide some feedback please?
Comment 5 Bug Janitor Service 2021-03-22 04:33:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 romainlouzier28 2021-03-22 07:45:50 UTC
Hi
As i have already reported to you the 14th of October
Solution 2 worked
The bug is closed 
Many thanks 

Romain 



> Le 22 mars 2021 à 05:33, Bug Janitor Service <bugzilla_noreply@kde.org> a écrit :
> 
> https://bugs.kde.org/show_bug.cgi?id=427601
> 
> --- Comment #5 from Bug Janitor Service <bug-janitor@kde.org> ---
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least
> 15 days. Please provide the requested information as soon as
> possible and set the bug status as REPORTED. Due to regular bug
> tracker maintenance, if the bug is still in NEEDSINFO status with
> no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
> due to lack of needed information.
> 
> For more information about our bug triaging procedures please read the
> wiki located here:
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> 
> If you have already provided the requested information, please
> mark the bug as REPORTED so that the KDE team knows that the bug is
> ready to be confirmed.
> 
> Thank you for helping us make KDE software even better for everyone!
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 7 emohr 2021-03-22 15:55:44 UTC
Thank you for the feedback and contribution. 

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.