https://bugs.winehq.org/show_bug.cgi?id=53453
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #12 from Zeb Figura z.figura12@gmail.com --- (In reply to Anonymous from comment #10)
I think the lesson here is that a single wine configuration shouldn't contain the installation of multiple independent applications, because it becomes a debugging nightmare (because the tools don't exist).
When I run with some empty WINEPREFIX directory, winecfg shows a window with some tabs as it is supposed to do (and asks about the installation of mono). So, it's an absolute certainty that some incompatibility related _only_ to the library resolution of winecfg between 6.01 and 7.13 was introduced.
I don't understand how someone writing a program can make such basic mistakes in the first place and if such a thing happens (because apparently the programmer wasn't as smart as they thought they were) once doesn't immediately provide such bug minimization tools (such tools have been written about for _decades_ and have been part of the "art" for much longer than that).
Because Wine is hard enough, broadly. Also, it's not a class of bug that comes up that often.
Anyway, in cases like this IME the problem tends to be not reuse of prefixes for multiple applications *per se*, but rather:
(a) programs installing native DLLs in a prefix, (b) people doing the same thing manually, and forgetting about it or not mentioning it in bug reports, (c) similarly, configuring the wine version, registry keys, native overrides, etc., (d) applications which didn't install correctly in the first place, or don't work on the first run, or only work on the first run...
with (c) being the most common. It's often easiest to check that by opening winecfg and looking for differences in the windows version or native overrides.