https://bugs.winehq.org/show_bug.cgi?id=45409
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Summary|RankedGaming Launcher RGC |RankedGaming Launcher RGC |doesn't start |doesn't start (app is | |Wine-aware, exits by design | |when Wine is detected) CC| |focht@gmx.net Status|NEW |RESOLVED
--- Comment #5 from Anastasius Focht focht@gmx.net --- Hello folks,
--- quote --- I would have resolved it as NOTOURBUG, what bug is that about wine-aware programs? --- quote ---
for broken apps with the workaround identified, collectors exist. For example:
* bug 42497 ("Wine aware apps crash into broken codepath (related to UpdateLayeredWindow): Resolume Avenue 4.6.1, Amaranth, Max7, Novation Circuit Editor")
In this case the developers don't want their app for whatever reason to be run under Wine. They don't even try to work around something.
--- snip --- ... 0042C2E2 FF15 F4106A00 CALL DWORD PTR DS:[<&KERNEL32.GetProcAddress>] ... 0042C319 8945 94 MOV DWORD PTR SS:[EBP-6C],EAX ... 0042C335 8B45 94 MOV EAX,DWORD PTR SS:[EBP-6C] 0042C338 85C0 TEST EAX,EAX 0042C33A 0F85 E6050000 JNZ 0042C926 ... 0042C926 C70424 1B000000 MOV DWORD PTR SS:[ESP],1B 0042C92D E8 EE741400 CALL <JMP.&msvcrt.exit> ... --- snip ---
IMHO 'invalid' -> app refuses to run under Wine by design.
Even with the Wine-Staging feature of hiding Wine-specific exports, developers will still find a way to detect it.
It's actually fairly easy to do avoiding without leaving any trace in logs. I've talked about it in some discussion at WineConf 2018 (walking in-memory loader module list, manually process exports ...).
In the end it's an endless battle like in other industries: virus/malware vs. anti-virus, cheat vs. anti-cheat.
Regards