May 2020 - Wine-Bugs - list.winehq.org

[Bug 42874] New: Battle.net App is unable to update games
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

https://bugs.winehq.org/show_bug.cgi?id=42874 Bug ID: 42874 Summary: Battle.net App is unable to update games Product: Wine Version: 2.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 57992 --> https://bugs.winehq.org/attachment.cgi?id=57992 Console output Any game requiring an update will cause a loop and not finish updating. Overwatch, Hearthstone, World of Warcraft or whatever other Game you have will announce a possible update is ready. If it is started, it will never finish and you will be notified of a possible update again. -- 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.

2 39

[Bug 28109] New: winmm capture tests fail on some machines
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

http://bugs.winehq.org/show_bug.cgi?id=28109 Summary: winmm capture tests fail on some machines Product: Wine Version: 1.3.26 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: mmdevapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com On my Asus G60JX laptop, with Ubuntu 11.04, winmm's capture tests fail with err:winmm:WINMM_OpenDevice Activate failed: 80004005 capture.c:148: Test failed: waveInOpen(1): format=8000x 8x1 flags=50000(CALLBACK_EVENT) rc=MMSYSERR_ERROR(Undefined external error.) err:winmm:WINMM_OpenDevice Activate failed: 80004005 capture.c:148: Test failed: waveInOpen(1): format=8000x 8x1 flags=50008(CALLBACK_EVENT|WAVE_FORMAT_DIRECT) rc=MMSYSERR_ERROR(Undefined external error.) This is a bit like bug 27895. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 20

[Bug 45876] New: Call of Duty Black Ops III no mouse input
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

https://bugs.winehq.org/show_bug.cgi?id=45876 Bug ID: 45876 Summary: Call of Duty Black Ops III no mouse input Product: Wine Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mo78(a)abv.bg Distribution: --- Created attachment 62382 --> https://bugs.winehq.org/attachment.cgi?id=62382 Call of Duty Black Ops III wine log Hello, I managed to install Windows Media Foundation dlls and regs and the game finally started. It wotks very well with DXVK and has a good framerate. Unfortunately there's no mouse click input in the main menu. Actually there is a cursor but you don't click nowhere hence I started a new game via the keyboard. After the game starts it runs with high FPS but there isn't mouse and you can't navigate (turn right, left, up, down, etc). In the mean time right click works and it triggers the weapon's scope. Installing dx and xact doesn't help. Forced MouseWarpOverride and "Automatically capture the mouse in full-screen windows" doesn't help too. Please, tell me what log flags do you need and I'll provide them. The provided log is from begining of the game to the first level when the actual gameplay begins. -- 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.

2 52

[Bug 27298] New: The Witcher 2 Slow Performance on any setting.
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

http://bugs.winehq.org/show_bug.cgi?id=27298 Summary: The Witcher 2 Slow Performance on any setting. Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mblackwell1024(a)gmail.com The Witcher 2 experiences extreme lag and gets around 5-10fps (subjective) no matter what video settings are selected. Lowering resolution or settings (even at the lowest) gives what appears to be < 5fps increase. On this setup: Q9550 GTX 460 2Gig RAM The game should pull closer to 20-30fps on Ultra, and 30-50fps on High (according to benchmarks and user feedback about the game on Windows) even at a 1080p resolution. The only console output when playing is: fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats fixme:d3d9:Direct3DShaderValidatorCreate9 stub fixme:d3d:state_lastpixel Last Pixel Drawing Disabled, not handled yet -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 48

[Bug 49092] New: Blindwrite 7 crashes with a stack overflow
by WineHQ Bugzilla July 17, 2020

July 17, 2020

https://bugs.winehq.org/show_bug.cgi?id=49092 Bug ID: 49092 Summary: Blindwrite 7 crashes with a stack overflow Product: Wine Version: 5.7 Hardware: x86 URL: https://web.archive.org/web/20131210151026/http://down load2.vso-software.fr/Blindwrite7_setup.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- 0024:err:seh:setup_exception_record stack overflow 1696 bytes in thread 0024 eip f7c0b6cb esp 00220c90 stack 0x220000-0x221000-0x320000 A stack trace from winedbg yields: Wine-gdb> bt #0 0xf7dc8fff in pthread_sigmask () from /usr/lib32/libpthread.so.0 #1 0x7bcb47fb in wine_server_call (req_ptr=0x222220) at ../../../wine/dlls/ntdll/server.c:387 #2 0x7bc95d7c in close_handle (handle=0x124) at ../../../wine/dlls/ntdll/om.c:393 #3 0x7bc95e88 in NtClose (Handle=0x124) at ../../../wine/dlls/ntdll/om.c:433 #4 0x7b043a04 in RegCloseKey(a)4 (hkey=0x124) at ../../../wine/dlls/kernelbase/registry.c:968 #5 0x0069ab55 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #6 0x00699e14 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #7 0x0069a89b in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #8 0x0069a84f in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #9 0x0073bb4b in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #10 0x007354d2 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #11 0x00736cc5 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #12 0x00736f53 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #13 0x00737f77 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #14 0x007384a9 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #15 0x00a9a1a7 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #16 0x00a99388 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #17 0x00a99394 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #18 0x00a99394 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe #19 0x00a99394 in ?? () from /home/hazel/.wine/dosdevices/c:/Program Files (x86)/VSO/BlindWrite/7/BW.exe the last frame repeating ad nauseam. I haven't figured out what's causing the bug. I have to presume it's a regression, though, given bug 38235 and the comments there. -- 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 4

[Bug 45701] New: Warframe: Launcher.exe does not update, keeps relaunching itself
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

https://bugs.winehq.org/show_bug.cgi?id=45701 Bug ID: 45701 Summary: Warframe: Launcher.exe does not update, keeps relaunching itself Product: Wine Version: 3.12 Hardware: x86 URL: http://content.warframe.com/dl/Warframe.msi OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: duhowpi(a)gmail.com Distribution: Debian Created attachment 62127 --> https://bugs.winehq.org/attachment.cgi?id=62127 Warframe Launcher loop log When a new version of Warframe Launcher is released, the Launcher downloads a tmp file and moves it to Launcher.exe.cpy . Then, a new process is called "Launcher.exe -relaunched", but as the Launcher is not updated (keeps the old version), this process is repeated infinitely until I manually move Launcher.exe.cpy and replace Launcher.exe. sha1sum / size / name: fa13c8d7e41d2d3db1b3c3ce4a1de67c70e9b992 1319104 Launcher.exe.cpy (new) 6b7b651df12daa68538c13bf6ddf4bae421e7efd 1307328 Launcher.exe (old) Log attached +relay, loop done 3 times. -- 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.

2 14

[Bug 18072] New: Core Media Player throws an exception on launch
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

http://bugs.winehq.org/show_bug.cgi?id=18072 Summary: Core Media Player throws an exception on launch Product: Wine Version: 1.1.19 Platform: PC-x86-64 URL: http://www.tucows.com/preview/299014 OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com My roommate despises VLC, and is in love with this media player. Step 1 in his dogfood transition to Ubuntu would be getting this media player to work in Wine. Problem 2: on launch, throws exception and refuses to launch. Exception EExternalException in module ntdll.dll at 0002B168. External exception C0000025. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 22

[Bug 31023] New: CuteFTP 8.3.4 - "Encountered an improper argument." Error boxes after most actions.
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

http://bugs.winehq.org/show_bug.cgi?id=31023 Bug #: 31023 Summary: CuteFTP 8.3.4 - "Encountered an improper argument." Error boxes after most actions. Product: Wine Version: 1.5.7 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nicekiwi(a)gmail.com Classification: Unclassified Created attachment 40721 --> http://bugs.winehq.org/attachment.cgi?id=40721 debug logfile Interacting with most buttons and will cause at least one popup box with the text "Encountered an improper argument.". -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 7

[Bug 36546] New: Please remove `tmpfs` special treatment in ntdll
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

http://bugs.winehq.org/show_bug.cgi?id=36546 Bug ID: 36546 Summary: Please remove `tmpfs` special treatment in ntdll Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com I do love running Wine in /tmp which is mounted as `tmpfs` in my Linux. However every other application installer whines that disk C: is not local so I have to use tricks to force applications to install in a WINEPREFIX which is located in RAM. Please, remove the special treatment of tmpfs mount points. -- 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.

2 40

[Bug 47409] New: odd behavior in several apps changing resolution after a crash
by wine-bugs＠winehq.org July 17, 2020

July 17, 2020

https://bugs.winehq.org/show_bug.cgi?id=47409 Bug ID: 47409 Summary: odd behavior in several apps changing resolution after a crash Product: Wine Version: 4.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- To make a thing clear: this isn't a GPU driver problem, over the years, I've seen this happen with a few different graphic cards using different drivers; also, while I'm opening this only now, the problem might be already over a decade old, just hard to trigger/notice, unless you're looking for it. If an app that changes resolution crashes during resolution change, *some* of the time it leaves xserver in an inconsistent state, where despite running 'xrandr -s <foo>', the app that crashed can't be started again until xserver restart (as simply shutting down whole wine doesn't work). If I start a second instance of the server, the app will start there without a problem there (that is, if no other problem occurs), but that leads to a different problem: if there are other wine apps running on the first display, another xerror triggered crash might happen. Due to excessive randomness involved (and the need to trigger a crash in the first place), this is hard to reproduce *exactly*, yet in the past years I've seen it quite a few times. Also, to make it clear, I've seen this in many unrelated apps, their only common theme was changing resolution (and perhaps using directdraw, but I'm not sure about this part). Also, while not sure about it, IIRC, all of those apps didn't change the res back upon Alt-Tab - for some reason, I think this might be important. xerror in the first case: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 7 (RRSetScreenSize) Value in failed request: 0x0 Serial number of failed request: 438 Current serial number in output stream: 439 xerror in the second case: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 10 (X_UnmapWindow) Resource id in failed request: 0x4c00003 Serial number of failed request: 322 Current serial number in output stream: 325 In the second case, it might simply be that wine caches DISPLAY value somewhere in the driver and tries to access first display with the resolution change, but no idea what's the first case, if xrandr is insufficient for a reset. -- 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.

2 1