June 2018 - Wine-Bugs - list.winehq.org

[Bug 45232] TIDAL (.NET 4.5 app) installer crashes

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45232 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet Summary|TIDAL can't be installed |TIDAL (.NET 4.5 app) |with exe installer |installer crashes CC| |focht(a)gmx.net --- Comment #1 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, I can't reproduce the crash with Wine 3.11 nor Wine-Staging 3.8, 3.10 in 32-bit WINEPREFIX. Prerequisite: * 'winetricks -q dotnet45' The app is UAC aware and tries to re-launch the installer using if it detects admin token (bug 40613). It uses '{9BA05972-F6A8-11CF-A442-00A0C90A8F39}' -> ShellWindows -> WindowsShell.Item -> Document.Application.ShellExecute for de-elevation. * https://blogs.msdn.microsoft.com/aaron_margosis/2009/06/06/faq-how-do-i-sta… * http://mdb-blog.blogspot.com/2013/01/nsis-lunch-program-as-user-from-uac.ht… --- snip --- $ WINEDEBUG=+seh,+process,+shell wine ./TIDALSetup.exe ... 0014:trace:shell:ShellDispatch_ShellExecute (L"Z:\\home\\focht\\Downloads\\TIDALSetup.exe", 0x33f1c0 {VT_BSTR: L" --rerunningWithoutUAC"}, 0x33f1b0 {VT_BSTR: L""}, 0x33f1a0 {VT_BSTR: L""}, 0x33f190 {VT_I4: 10}) ... --- snip --- Your crash location: --- snip --- 004063CB | 6A 3C PUSH 3C 004063CD | B8 0EC94100 MOV EAX,0041C90E 004063D2 | E8 C5560100 CALL 0041BA9C 004063D7 | 8BF2 MOV ESI,EDX 004063D9 | 33DB XOR EBX,EBX 004063DB | 895D E0 MOV DWORD PTR SS:[EBP-20],EBX 004063DE | 8D45 E0 LEA EAX,[EBP-20] 004063E1 | 895D FC MOV DWORD PTR SS:[EBP-4],EBX 004063E4 | 50 PUSH EAX 004063E5 | 68 B04C4200 PUSH OFFSET 00424CB0 004063EA | 6A 17 PUSH 17 004063EC | 53 PUSH EBX 004063ED | 68 A0D24100 PUSH OFFSET 0041D2A0 004063F2 | FF15 14D24100 CALL DWORD PTR DS:[<&ole32.CoCreateInstance>] ; ShellWindows 004063F8 | 6A 03 PUSH 3 004063FA | 58 POP EAX 004063FB | 66:8945 BC MOV WORD PTR SS:[EBP-44],AX 004063FF | 895D C4 MOV DWORD PTR SS:[EBP-3C],EBX 00406402 | 33C0 XOR EAX,EAX 00406404 | 8D7D CC LEA EDI,[EBP-34] 00406407 | AB STOS DWORD PTR ES:[EDI] 00406408 | AB STOS DWORD PTR ES:[EDI] 00406409 | AB STOS DWORD PTR ES:[EDI] 0040640A | AB STOS DWORD PTR ES:[EDI] 0040640B | 8D45 CC LEA EAX,[EBP-34] 0040640E | 50 PUSH EAX 0040640F | FF15 BCD14100 CALL DWORD PTR DS:[<&OLEAUT32.#8>] 00406415 | 895D E4 MOV DWORD PTR SS:[EBP-1C],EBX 00406418 | 8D55 E4 LEA EDX,[EBP-1C] 0040641B | C645 FC 03 MOV BYTE PTR SS:[EBP-4],3 0040641F | 8B45 E0 MOV EAX,DWORD PTR SS:[EBP-20] 00406422 | 52 PUSH EDX 00406423 | 6A 01 PUSH 1 00406425 | 8D55 DC LEA EDX,[EBP-24] 00406428 | 8B08 MOV ECX,DWORD PTR DS:[EAX] ; *boom* 0040642A | 52 PUSH EDX 0040642B | 6A 08 PUSH 8 0040642D | 8D55 CC LEA EDX,[EBP-34] 00406430 | 52 PUSH EDX 00406431 | 8D55 BC LEA EDX,[EBP-44] 00406434 | 52 PUSH EDX 00406435 | 50 PUSH EAX 00406436 | FF51 3C CALL DWORD PTR DS:[ECX+3C] ; 0x0039012C ... 0039012C | 8D4424 04 LEA EAX,[ESP+4] 00390130 | 50 PUSH EAX 00390131 | 68 0F000000 PUSH 0F 00390136 | E8 0A78C07D CALL 7DF97945 ; xCall [/home/focht/projects/wine/mainline-src/dlls/oleaut32/tmarshal.c:1416] in oleaut32 0039013B | C2 1C00 RETN 1C ... --- snip --- --- snip --- Wine-dbg>bt Backtrace: =>0 0x7dfd9945 xCall(method=0xf, args=0x33dcd4) [/home/focht/projects/wine/mainline-src/dlls/oleaut32/tmarshal.c:1416] in oleaut32 (0x0033dd48) 1 0x0040654c in tidalsetup (+0x654b) (0x0033dd78) 2 0x004065d0 in tidalsetup (+0x65cf) (0x0033de38) 3 0x00407539 in tidalsetup (+0x7538) (0x0033fe64) 4 0x0040a0aa in tidalsetup (+0xa0a9) (0x0033feb0) 5 0x7b46dad0 call_process_entry+0xb() in kernel32 (0x0033fec8) 6 0x7b46dc0b start_process+0x12c(entry=<couldn't compute location>, peb=<couldn't compute location>) [/home/focht/projects/wine/mainline-src/dlls/kernel32/process.c:1099] in kernel32 (0x0033ffd8) 7 0x7b46dade start_process_wrapper+0x9() in kernel32 (0x0033ffec) ... --- snip --- Looks like something is broken on your host if a simple instantiation of 'ShellWindows' AppID fails (out-of-proc COM server). In a 64-bit WINEPREFIX it suffers from: "TMStubImpl_Invoke not implemented on non-i386". $ sha1sum TIDALSetup.exe 618693e9da33c64fdb535437f7d4419ca7e898a2 TIDALSetup.exe $ du -sh TIDALSetup.exe 53M TIDALSetup.exe $ wine --version wine-3.11 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 45370] New: redefinition of typedef 'DWRITE_GLYPH_RUN_DESCRIPTION'

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45370 Bug ID: 45370 Summary: redefinition of typedef 'DWRITE_GLYPH_RUN_DESCRIPTION' Product: Wine Version: 3.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)protonmail.com Distribution: --- Created attachment 61681 --> https://bugs.winehq.org/attachment.cgi?id=61681 log from failed compile (gcc 4.2.2) gcc 4.2.2 Wine-3.11 compiling fails with: error: redefinition of typedef 'DWRITE_GLYPH_RUN_DESCRIPTION' -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 45369] Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45369 --- Comment #2 from Zebediah Figura <z.figura12(a)gmail.com> --- This would make sense if explorer.exe crashes; it'll try to start the winedbg crash dialogbut the latter will involve creating a window and thus starting another instance of explorer.exe. In that case creating the registry key HKCU\Software\Wine\WineDbg and setting the value ShowCrashDialog to 0 should work around the problem. It would be good to fix this, of course. Could you please attach a log with +seh,+win,+explorer,+module? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 44893] SKSE64 fails to initialize, reports: "couldn' t allocate trampoline, no free space before image" ( virtual address space between KUSER_SHARED_DATA and main executable reported as reserved )

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44893 --- Comment #8 from Christian Widmer <CWidmer(a)umbrox.de> --- https://bugs.winehq.org/show_bug.cgi?id=45218 is probably the same issue and has patches attached. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 45369] Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45369 roman(a)hargrave.info <roman(a)hargrave.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 45369] Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45369 --- Comment #1 from roman(a)hargrave.info <roman(a)hargrave.info> --- Created attachment 61680 --> https://bugs.winehq.org/attachment.cgi?id=61680 A screenshot of process hacker running in the prefix which displays the deeply nested explorer beneath winedbg. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 45369] New: Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45369 Bug ID: 45369 Summary: Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed Product: Wine-staging Version: 3.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: roman(a)hargrave.info CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 61679 --> https://bugs.winehq.org/attachment.cgi?id=61679 A portion of wine console output collected after the event I'd like to open with a note that I am not submitting this on wine-devel, as I the only application that has been able to cause these crashes will not run well enough to reliably reproduce the error without DXVK, and in turn wine-staging (as far as I am aware, DXVK continues to require a patch in the staging patchset that has not been mainlined - correct me if i am wrong). The application which has been causing problems is Grand Theft Auto V, though specifically Rock Star Social Club (I can't be terribly certain - but the issue tends to crop up when social club is brought in to the question). Glancing at the crash info in the terminal (winedbg is actually not even visible yet as it is too preoccupied with explorer), this is the result of an exception thrown within libcef.dll, which judging by the name and the platform which it is used by, is chromium embedded framework - a common offender. Knowing this, i'll just avoid the social club in-game if at all possible, but what's concerning is the outcome. Something about the manner in which it has gone about crashing causes some _very_ eratic behaviour in winedbg. For some reason, `explorer.exe /desktop` is invoked as a child process of winedbg and then fails to start. Another instance of explorer with the same parameters is then started by the child, as well as some concurrent instances (I think - when you have so many process running that your PIDs roll over it start to get hard to track who started who) - effectively an explorer fork bomb, though it dies off fast enough if you get to winedbg and kill it or its parent. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 45218] Fallout 4 Script Extender fails to allocate trampoline buffers

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45218 Christian Widmer <shadow(a)umbrox.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shadow(a)umbrox.de -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 44893] SKSE64 fails to initialize, reports: "couldn' t allocate trampoline, no free space before image" ( virtual address space between KUSER_SHARED_DATA and main executable reported as reserved )

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44893 --- Comment #7 from Christian Widmer <shadow(a)umbrox.de> --- Unfortunately, I have to revoke my previous statement. After installing a mod to test (SkyUI) the error does indeed occur. I am sorry for the noise. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018

[Bug 44893] SKSE64 fails to initialize, reports: "couldn' t allocate trampoline, no free space before image" ( virtual address space between KUSER_SHARED_DATA and main executable reported as reserved )

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44893 Christian Widmer <shadow(a)umbrox.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shadow(a)umbrox.de --- Comment #6 from Christian Widmer <shadow(a)umbrox.de> --- I just tried SKSE-2.0.7 (runtime 1.5.39) on wine 3.11 and I did not get the error. My operating system is Gentoo Linux x86_64. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 24, 2018