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

[Bug 44692] 64-bit .NET apps crash on startup with Wine-Mono ( Medieval Engineers, Dashware 1.9)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44692 --- Comment #9 from Anastasius Focht <focht(a)gmx.net> --- Hello Louis, --- quote --- Is there a recipe ATM to get .NET Framework 4.x properly installed in 64-bit WINEPREFIX? --- quote --- no, not in a clean way. It's essentially manual extraction of some dlls from {.msi,.msu,.mzz} packages and putting them in proper 64-bit locations. The underlying 32-bit/64-bit MSI client/server insufficiencies and mixed 32-bit/64-bit MSI package handling bugs causing this are already documented. I don't want to have these bugs ignored/stalled for more years just because workarounds exist with winetricks. We already had this in the past with various other issues. No one will bother/attempt to fix them if there is no pressure from end users. If you provide winetricks hacked recipe(s) for working mixed mode 32-bit/64-bit .NET Framework installation in 64-bit WINEPREFIX, then go on. You should be prepared to provide support for bug reports resulting from these on your own. 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.

April 1, 2018

[Bug 44692] 64-bit .NET apps crash on startup with Wine-Mono ( Medieval Engineers, Dashware 1.9)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44692 --- Comment #8 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Anastasius Focht from comment #7) > Hello folks, > > The aforementioned apps run further (albeit into other unrelated issues) > with 64-bit .NET Framework 4.x properly installed in 64-bit WINEPREFIX. Is there a recipe ATM to get .NET Framework 4.x properly installed in 64-bit WINEPREFIX? -- 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.

April 1, 2018

[Bug 43434] StarCraft: Brood War doesn' t run without setting the Windows version to 2003 or Vista

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43434 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net --- Comment #11 from Anastasius Focht <focht(a)gmx.net> --- Hello Igor --- quote --- that if I run "winedbg StarCraft.exe" then it fails differently (it is able to show message box). Trace output from the same thread: 002d:exception in TLS callback (proc=0x1073d8f8,module=0x10000000,reason=PROCESS_ATTACH,reserved=0) 002d:Call PE DLL (proc=0x10025ae0,module=0x10000000 L"ClientSdk.dll",reason=PROCESS_ATTACH,res=0x1) ... 002d:Call user32.MessageBoxW(00000000,0033f680 L"Game Initialization Failed!",0033f6c8 L"ERROR",00000010) ret=100262fa --- quote --- Please don't run Blizzard games under a debugger unless you know what you are doing. There are anti-debugger checks in the startup code. Besides these software protection related issues with StarCraft are already known/documented in various tickets. I still don't get the purpose of this ticket? https://us.battle.net/forums/en/starcraft/topic/20754255399 --- quote --- Win XP WILL NOT work beyond 1.16.1. Unfortunately, the Installer for 1.18 DOES NOT tell the User this information; INSTEAD, the 1.18, (StarCraft Anthology), Installer goes through the ENTIRE installation, AND THEN prevents the game from Launching. --- quote --- IMHO this ticket is invalid. 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.

April 1, 2018

[Bug 44879] Universe Sandbox 2 crashes on unimplemented function api-ms-win-core-timezone-l1-1-0.dll.GetDynamicTimeZoneInformationEffectiveYear

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44879 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net Ever confirmed|0 |1 Summary|unimplemented function |Universe Sandbox 2 crashes |api-ms-win-core-timezone-l1 |on unimplemented function |-1-0.dll.GetDynamicTimeZone |api-ms-win-core-timezone-l1 |InformationEffectiveYears |-1-0.dll.GetDynamicTimeZone | |InformationEffectiveYear Status|UNCONFIRMED |NEW --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, confirming on behalf of OP. Windows 8+ API it seems. MSDN: https://msdn.microsoft.com/en-us/library/windows/desktop/hh706894(v=vs.85).… --- snip --- $ grep -Hrni GetDynamicTimeZoneInformationEffectiveYears dlls/api-ms-win-core-timezone-l1-1-0/api-ms-win-core-timezone-l1-1-0.spec:4:@ stub GetDynamicTimeZoneInformationEffectiveYears dlls/advapi32/advapi32.spec:321:# @ stub GetDynamicTimeZoneInformationEffectiveYears dlls/kernelbase/kernelbase.spec:490:# @ stub GetDynamicTimeZoneInformationEffectiveYears --- snip --- 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.

April 1, 2018

[Bug 44882] Call of Duty Infinite Warfare crashes after Splash-Screen with a Direct-X Error

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44882 --- Comment #1 from Christian <christian.frank(a)gmx.de> --- Created attachment 60949 --> https://bugs.winehq.org/attachment.cgi?id=60949 logfile (7z format) part 2 -- 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.

April 1, 2018

[Bug 44882] New: Call of Duty Infinite Warfare crashes after Splash-Screen with a Direct-X Error

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44882 Bug ID: 44882 Summary: Call of Duty Infinite Warfare crashes after Splash-Screen with a Direct-X Error Product: Wine Version: 3.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Created attachment 60948 --> https://bugs.winehq.org/attachment.cgi?id=60948 logfile (7z format) part 1 Hi, when trying to start the game, i shows the splash screen and then shows a message Box with an Direct-X Error (sadly in german, but you can find it in the attached trace): 6549764:008b:Call user32.MessageBoxW(00050162,00238e80 L"Schwerwiegender DirectX-Fehler.\n\nWeitere Hinweise finden Sie in der Readme-Datei.",00238c80 L"DirectX-Fehler",00000010) ret=140d577cb The first number is the line number. As i noticed that none of the newer Cod titles is working in wine and it is still a somewhat popular gameing franchise, it would be fantastic if a dev could take a look at the trace. If there are any questions, i am glad to help. Had to split the 7z logfile in 2 pieces, xaa and xab. Thx a lot ! Christian -- 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.

April 1, 2018

[Bug 44877] Guild Wars 2 Launcher Crashes

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44877 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- I suspect this is the broken CSMT checkbox. Do you have the CSMT checkbox checked in winecfg? -- 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.

April 1, 2018

[Bug 44881] MidRadio Player doesn' t send SysEx messages to the MIDI device.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44881 Sagawa <sagawa.aki+winebugs(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download --- Comment #1 from Sagawa <sagawa.aki+winebugs(a)gmail.com> --- I found out that this bug is caused by MIDI stream MEVT_LONGMSG handling. I sent an audio test case and a patch: - Test case, https://source.winehq.org/patches/data/144245 - Patch, https://source.winehq.org/patches/data/144246 -- 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.

April 1, 2018

[Bug 44692] 64-bit .NET apps crash on startup with Wine-Mono ( Medieval Engineers, Dashware 1.9)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44692 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win64 Component|ntdll |mscoree Summary|Medieval Engineers crashes |64-bit .NET apps crash on |on startup |startup with Wine-Mono | |(Medieval Engineers, | |Dashware 1.9) CC| |focht(a)gmx.net --- Comment #7 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, refining fields/summary to explicitly mention Wine-Mono. The aforementioned apps run further (albeit into other unrelated issues) with 64-bit .NET Framework 4.x properly installed in 64-bit WINEPREFIX. 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.

April 1, 2018

[Bug 44881] New: MidRadio Player doesn' t send SysEx messages to the MIDI device.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44881 Bug ID: 44881 Summary: MidRadio Player doesn't send SysEx messages to the MIDI device. Product: Wine Version: 3.4 Hardware: x86 URL: http://download.music-eclub.com/mrplayer/win/mr7211.ms i OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu MidRadio Player is a MIDI player distributed by Yamaha Corporation. When I choose an external MIDI port in the option dialog, it doesn't send System Exclusive (SysEx) message at all. How to setup: 1) Download MidRadio player from the above URL. 2) Install mr7211.msi using msiexec, i.e. wine msiexec /i mr7211.msi. 3) Follow the setup wizards (written in Japanese). How to reproduce: 1) Create a virtual MIDI port by "amidi -p virtual -d" 2) In another terminal, chdir to the install directory and run MidRadio palyer, i.e. "wine MidRadio.exe" 3) Click No (or Yes) for cooperation in quality improvement. (first start up time only) 4) Choose the following menu item: オプション(Option) - MIDI出力先の設定(Setup MIDI output) 5) In the dialog, choose MIDIデバイスを使う(Use MIDI device) and pick up the virtual MIDI device port, e.g. "Client-129 - Virtual RawMIDI", from the drop down list. 6) Click [OK] and close the dialog window. 7) Press Ctrl+O or choose the following menu item: ファイル(File) - ファイルを開く(Open a file) 8) Select a MIDI file which contains SysEx message. I tested with Free Sample MIDI Files for Yamaha GM and XG Keyboards[1]. 9) Click 開く(Open), then MidRadio Player plays it. Expected behavior: - amidi's terminal window shows SysEx message, e.g. F0 7E 7F 09 01 F7 for GM System On. Then, shows another MIDI message, Note On, Note Off, etc. - No playback voice as we're using virtual port. Actual behavior: - amidi's terminal window doesn't show SysEx message. However, it shows common MIDI message, Note On, Note Off, etc. - No playback voice. [1] http://faq.yamaha.com/us/en/article/musical-instruments/keyboards/digitalke… -- 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.

April 1, 2018