MS Windows 10 Pro x64 Intel Kdenlive 16.12.1 beta for MS Windows + FFmpeg download per instructions on https://kdenlive.org/download/ Program start & Config Wizard start complain about missing Breeze icons. Screenshot attached. Also complains about missing external programs for DVD interaction but that is not a concern at the present.
Created attachment 103518 [details] Screenshot missing Breeze icons complaint
Unfortunately, I cannot reproduce on Win8.1 with the recent Kdenlive/Win package.
Hmmm... Cannot now reproduce on program launch myself. Aughhhh!!! Win10 broke parts of a lot of open source GUI tools I use but weirdly I have also sometimes seen this breakage cure itself after re-opening a tool several times across days, as if Win10 is learning and fixing stuff. Frustrating for the traditional bug report model. Let's close this bug as cannot reproduce. HOWEVER, confirmed the missing icons side issue in bug 375275: Settings->Run Config Wizard still starts up with the Missing Breeze Icons complaint.
Can reconfirm; happens when (re)running the "Wizzard".
'Can reconfirm; happens when (re)running the "Wizzard".' Are these statements or questions? And regards this bug 375271 or bug 375275? If regards bug 375275 then this dialog preemptively should move to bug 375275. Re-confirming here regards bug 375275: on opening the Wizard still get 'Missing Package: Breeze icons...'. Will update bug 375275 with xref as well.
What does the title of this bug report read? "v16.12.1 beta for MS Windows complains about missing Breeze icons". So one could imagine that this is what a comment under this title refers to, or is this unimaginable? Next, what is the # of this bug report? It can be found next to the bug report title: 375271. A comment thus usually, see below, refers to this number. Or does this sound far fetched? Did you see the english writing sign for a question in my comment? No? Good. So, a solid assumption would be that it's a statement. Actually, the concept of bug reports and comments in bug reports: the title of a report should be descriptive and referring to the bug being reported. Unless explicitly referencing another bug report, bug report comments are belonging and thus related, to the report they are part of. I hope that clarifies the situation. Feel free to ask fuethwr questions in the G+ community or the forum if you need to. Thank you very much for your cooperation.
Recall original title referred to context of Kdenlive program launch, which could then not be reproduced. Then it was noted that the Config Wizard showed similar symptoms and a bug opened separately for that which referred to this bug for the screenshot.
Recall this bug title referred to the context of a Kdenlive program launch, so the title is descriptive. Subsequently, the symptom could then not be reproduced. Then it was noted that the Config Wizard showed similar symptoms and a bug opened separately for that (bug 375275) which referred to this bug for the screenshot. As indicated in Comment 3, this bug can be CLOSED because it cannot be reproduced. Bug 375275 has been updated to have its own independent screenshot.
Closing.