1) Follow the instructions and try a clean wineprefix as they recommend. 2) wine --version should specify which version you are using. If the version is < 3 you may want to update your wine installation using the packages from winehq. 3) Search the winehq bug database of existing, e.g. using the phr...

Here is a demo for wine testers.
https://www.factorio.com/download-demo

Which game do you execute?

> Can installing a programme break the computer. Theoretically yes. Practically never. Installers for Windows programs are generally not designed with the aim to cause malicious behavior on Linux computers, they do not expect you to use Wine. What an installer usually changes is: - it puts program f...

I haven't found any logs to give more information but will look for them if you can give me some suggestions on where. Have you tried to run the app launcher from the console? That should give you the log output (which you could pipe in a file). As they write the installed app should be in $WINEPRE...

Try in the console to discover what you are running.

Nice work!

a) When yad is not installed Winestarter conf fails in line 3917
$yad_bin --width=520 --title "Winestarter configurator" --window-icon=$img_wine_desk_ui --no-buttons \

b) Typo in dialoque "Wine bottle edition"

You are right. I don't think anyone on the devel list is malicious and you have excellent coders there with lots of experiences. Tools alone don't help. And in a way as coders we do not care if people are nice to us in what they say, when we write shitty code and they tell us exactly that and explai...

Let me give you one recent example from the patch watcher: A fairly unknown contributor Zhiyi Zhang committed patches to fix memory leaks. These patches were rejected because it was not deemed necessary to fix them. Of course such patches are low hanging fruits. If I were him or her I would never co...

Some of them were never submitted to the main tree. Some of them were taken from attachments to bugs here and had long been abandoned by their authors. Some were also clearly labeled by their authors as hacks, not proper fixes. And some were submitted to staging because the author doesn't want them...

The fundamental issue seems to be that there is no one on the wine team who walks staging patches through the adoption process and if feedback on submitted patches was given it is lost. KDE uses reviewboard, also with github we have a nice process to discuss and autoreview patches. Say, if there are...