Current minigalaxy 1.3.0 seems to somehow corrupt the wine prefixes

[ell1e]

Just some months ago, I managed to install and run most games, other than DOS due to that other unresolved issue using minigalaxy just fine. But with the current version 1.3.0, somehow it seems to break the wine prefixes after it managed to run the GOG.com installer just fine, leading to me being unable to launch the game with either no reaction to the play button or strange errors popping up:

Now if it was just one game affected I would just reinstall it, assuming a weird lightning in a bottle rare glitch, but all regular Windows games seem to be affected. Winecfg won't launch either for any of them. On the host system outside of flatpak, wine is installed both as a 64bit and 32bit version. I couldn't think of any obvious reason why this would be happening, so is this a minigalaxy regression of some sorts?

Affected minigalaxy version: 1.3.0

Affected on linux distro: openSUSE Slowroll

Install method for minigalaxy: flathub/flatpak

[sharkwouter]

Odd, seems like a flatpak specific issue. Could you report this to the flatpak repo?

[ell1e]

Sadly, combined with #592 it seems like in practice, it's not possible to launch any games anymore no matter which type. I reported that other one to the flatpak but there wasn't much of a reaction.

Is there a different distribution independent install method for minigalaxy that works? Also, is there any button to force minigalaxy to somehow repair a broken wineprefix, preferably without throwing away all the game files? (E.g. by copying over all the system files from a working wine prefix)

[ell1e]

This seems to have been fixed somehow in 1.3.1, perhaps #615 or something similar was related to this.