August 2018 - Wine-bugs - list.winehq.org

[Bug 41054] New: Battle.net.exe deadlocks in CriticalSection
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=41054 Bug ID: 41054 Summary: Battle.net.exe deadlocks in CriticalSection Product: Wine-staging Version: 1.9.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rankincj(a)yahoo.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Trying to launch Blizzard's Battle.net.exe using Wine Staging 1.9.15 RPMs from Fedora 24. However, the process deadlocks and prints messages like: err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in thread 0063, blocked by 0000, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in thread 0063, blocked by 0000, retrying (60 sec) This happens with both 32 bit and 64 bit prefixes. Disabling all "staging" options via winecfg does not help. -- 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.

1 10

[Bug 40225] New: NtQuerySection returns wrong size
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=40225 Bug ID: 40225 Summary: NtQuerySection returns wrong size Product: Wine Version: 1.9.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: mail(a)georg.so Distribution: --- Created attachment 53743 --> https://bugs.winehq.org/attachment.cgi?id=53743 NtQuerySection test case via boost interprocess When using NtQuerySection to get the file size of a file mapping the wine result deviates from the native one. With wine, it seems that the size is rounded up to the next page. On native windows, the real file size is returned. How to reproduce (e.g. with a mingw cross compile environment): mkdir build cd build mingw64-cmake .. mingw64-make wine64 main Actual behavior: fixme:winediag:start_process Wine Staging 1.9.3 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. region.get_size() == 4096 sizeof(inp)-1 == 5 Assertion failed! Program: Z:\home\gms\program\libixxxutil\build-case-win-rel\main.exe File: /home/gms/program/libixxxutil/test/mapped_size_case/main.cc, Line 28 Expression: region.get_size() == sizeof(inp)-1 abnormal program termination Expected behavior (as e.g. on Windows 7): No output and success exit code. How reproducible: always The test program uses Boost Interprocess functions for creating that mapping and getting the size. See also: cf. http://www.boost.org/doc/libs/1_60_0/doc/html/boost/interprocess/mapped_reg… > The OS could allocate more pages than size/page_size(), but get_address() will always return the address passed in this function (if not null) and get_size() will return the specified size. http://stackoverflow.com/a/26983182/427158 -> NtQuerySection -- 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.

1 9

[Bug 42288] New: Shantae and the Pirate' s Curse - gameplay area resized to a tiny rectangle
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=42288 Bug ID: 42288 Summary: Shantae and the Pirate's Curse - gameplay area resized to a tiny rectangle Product: Wine-staging Version: 2.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ikk_pl(a)yahoo.co.uk CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 56999 --> https://bugs.winehq.org/attachment.cgi?id=56999 Screenshot showing the problem Normally the game uses pixelized graphics during gameplay. In wine the play area does not get resized to the entire screen, but instead stays at the same size in a tiny rectangle in the middle of the screen. (Note that the game doesn't run on vanilla wine, it needs staging patches for the CreateDeferredContext call.) -- 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.

1 5

[Bug 39368] New: Some games (F.E.A.R. 1, Hitman: Contracts) crash on start when EAX(Environmental Audio Extensions) enabled
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=39368 Bug ID: 39368 Summary: Some games (F.E.A.R. 1, Hitman: Contracts) crash on start when EAX(Environmental Audio Extensions) enabled Product: Wine-staging Version: 1.7.40 Hardware: x86 URL: http://www.gamershell.com/download_10167.shtml OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 52478 --> https://bugs.winehq.org/attachment.cgi?id=52478 F.E.A.R. demo backtrace When EAX is enabled in staging, some games crash on start. Two examples are F.E.A.R. or Hitman: Contracts. Both games have demos to reproduce the problem. Hitman: Contracts demo: http://www.gamershell.com/download_5663.shtml wine-1.7.51-268-g781b88b (Staging) Fedora 22 32-bit Alsa 1.0.29, stereo speaker setup (PA is not running) Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2) -- 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.

1 10

[Bug 42127] New: DOOM (2016): Crash on the main menu.
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=42127 Bug ID: 42127 Summary: DOOM (2016): Crash on the main menu. Product: Wine-staging Version: 2.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b.adam.martin(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 56667 --> https://bugs.winehq.org/attachment.cgi?id=56667 terminal output and backtrace Since only one attachment is allowed, I have pasted the terminal output at the head of the backtrace.txt. Search for "backtrace" to skip. 4.8.13-1-ARCH GTX 770 nvidia 375.26-1 i5 4670k wine-2.0-rc2 (Staging) --- The Arch repos haven't yet updated to rc3; it's flagged. $ wine DOOMx64vk.exe The game launches fine, goes through the splash screen, and then when presented with the main menu, abruptly crashes. I have tried setting different Windows versions winecfg, same result with each. I have also run $ wine DOOMx64.exe, same result. -- 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.

1 3

[Bug 45589] New: Starcraft 2: Sound stops working after a while
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=45589 Bug ID: 45589 Summary: Starcraft 2: Sound stops working after a while Product: Wine-staging Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yumekuineru(a)hotmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62013 --> https://bugs.winehq.org/attachment.cgi?id=62013 Sound stopped working within the last 10 seconds Sound sometimes drops out for me in the middle of a Starcraft 2 game or replay (or it seems while at main menu also). After sound drops out the same behaviour as is reported in the bug https://bugs.winehq.org/show_bug.cgi?id=45502 occurs (the game freezes if audio device setting is changed or the exit game button is pressed) It might be one of my overrides since it is a prefix I have not modified in a while after I managed to get it working, though the issue started occuring quite recently. It occurs less frequently than all the time as was the case before the fixes staged in this issue though. Versions: WINE_COMMIT="25cc380b8ed41652b135657ef7651beef2f20ae4" #3.13 STAGING_COMMIT="2f3ba1fb462894ad267d72d07ed2114e0ae1f5c2" Patches applied (all seem to mainly pertain to League of Legends): 0003-Pretend-to-have-a-wow64-dll.patch 0006-Refactor-LdrInitializeThunk.patch 0007-Refactor-RtlCreateUserThread-into-NtCreateThreadEx.patch 0009-Refactor-__wine_syscall_dispatcher-for-i386.patch Attachment in https://bugs.winehq.org/show_bug.cgi?id=45550#c8 I am not sure how to reliably reproduce the issue, though I was able to capture a debug log from the channels described on the wiki for Sound: +tid,+seh,+mmdevapi,+winmm,+driver,+msacm,+midi,+dsound,+dsound3d,+xaudio2,+xapofx,+dmusic,+mci,+pulse,+oss,+alsa,+coreaudio,+timestamp I copied the file I was redirecting output to when I heard sound stop (perhaps a few seconds after), then took the tail of the copied file which seems to span abouts 10 seconds of logtime. I do not believe I have made any changes to pulseaudio except for disabling flat-volumes and adding the following sink (that currently was not being used): ``` DEFAULT_OUTPUT=$(pacmd list-sinks | grep -A1 "* index" | grep -oP "<\K[^ >]+") pactl load-module module-combine-sink sink_name=recordleague slaves=$DEFAULT_OUTPUT sink_properties=device.description="leagueaudio" ``` -- 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.

1 24

[Bug 43543] New: Wrong sounds in Within a Deep Forest
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=43543 Bug ID: 43543 Summary: Wrong sounds in Within a Deep Forest Product: Wine-staging Version: 2.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine(a)thecybershadow.net CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- The sound effects in Within a Deep Forest seem to be broken. Specifically, the wrong samples seem to be used. For example, selecting a ball material produces a metallic sound (instead of the loud "twirp"), and bouncing around with the initial ball material plays various hums and occasionally splashing noises. Reproducible with WaDF version 1.1.4 and wine-staging 2.14 on a clean WINEPREFIX. Not reproducible with wine 2.14. -- 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.

1 7

[Bug 42318] New: Sleeping Dogs - CSMT prevents getting past introductory videos, without CSMT the videos are all purple and continue looping without starting the actual game.
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=42318 Bug ID: 42318 Summary: Sleeping Dogs - CSMT prevents getting past introductory videos, without CSMT the videos are all purple and continue looping without starting the actual game. Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: casparcedro96(a)gmail.com Distribution: --- Created attachment 57063 --> https://bugs.winehq.org/attachment.cgi?id=57063 Crash with CSMT enabled So it seems Sleeping Dogs does not like CSMT for some reason and even without it I cannot seem to get past the intro videos which show up pink but the audio is perceptible - it continues to loop playing the videos but never gets into the game. -- 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.

1 8

[Bug 40458] New: Photoshop CC 2015 Amtlib issues
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=40458 Bug ID: 40458 Summary: Photoshop CC 2015 Amtlib issues Product: Wine-staging Version: 1.9.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: msnduy(a)hotmail.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 54210 --> https://bugs.winehq.org/attachment.cgi?id=54210 logs I have issues with running Photoshop CC 2015 (64bit) in Wine-Staging. It installs fine with both staging and stable (PDApp only works with Staging). But I can't start it in staging without an error although in wine stable it works normally but the user interface of photoshop is somehow not correctly rendered. Wine-Staging (Compiled from git upstream): Photoshop shows an error with the error code 16. By luck I also came across the amtlib.log file which also contained error message with the same error code, saying: 04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | Error: Failed to update RW check key ! 04/12/16 22:38:32:097 | [ERROR] | | | | AMT | | | 57 | ERROR: SLCache is not writable, hence exiting. (Errno = 16) I am sure it's the amtlib what is causing the issue as I didn't get these lines with wine-stable. The tricky part is that I don't know what patch from wine-staging is causing this issue. I attached the log files which are interesting. I am not sure now how to debug this further as the wine debug output isn't helpful either (basically the same output as wine stable). What might by broken can be Registry/memory/file access, the problem is that I don't know what api calls amtlib is doing. Well, if someone can give me further instructions how to debug the issue I would be glad. Also if you have enough time or whatsoever you could try install Photoshop CC 2015 :). -- 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.

1 8

[Bug 43761] New: World of Warcraft d3d11 textures rendering regression and other... Wine Staging 2.17
by wine-bugs＠winehq.org 20 Aug '18

20 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=43761 Bug ID: 43761 Summary: World of Warcraft d3d11 textures rendering regression and other... Wine Staging 2.17 Product: Wine-staging Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zefkerrigan(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59257 --> https://bugs.winehq.org/attachment.cgi?id=59257 World of Warcraft d3d11 textures rendering regression. Wine Staging 2.17 Sorry, but I really do not have the opportunity to find out if this bug is in the development Wine branch, because World of Warcraft can only be launched in Wine Staging, but it can not be launched in a "vanilla" development Wine branch. So, I using only Wine Staging. I could not get the output of the console, because, unfortunately, when I tried to run the game through the console, I did not manage to run the game until the stage of character management/movement. That is, the game hangs up every time the progress bar ends after clicking on the "Enter the World" button. But, I was surprised that the game is normally run through a shortcut on the dock bar, which also contains the same command in the line Exec=wine64 'c:/Program Files (x86)/World of Warcraft/Wow-64.exe' which I entered into the console (but, without "Exec=", of course). When I used Wine Staging 2.16 I did not have any noticeable rendering bugs with the World of Warcraft in DirectX11 mode, or DirectX9. But, with Wine Staging 2.17 I began to see what's on the attached screenshot if WoW is running in DirectX11 mode. But, in DirectX9 mode this bug does not appear, and there are no any distortions in the graphics. My specs: Arch Linux x86_64 with latest updates, GNOME. GPU Radeon HD7770 with latest Mesa. Wine Staging 2.17 with CSMT is on, x64 Wine prefix, 64bit WoW build. -- 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.

1 16