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

[Bug 50664] New: Assassin's Creed II can't select controller
by WineHQ Bugzilla June 6, 2021

June 6, 2021

https://bugs.winehq.org/show_bug.cgi?id=50664 Bug ID: 50664 Summary: Assassin's Creed II can't select controller Product: Wine Version: 6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: atillolann-1815(a)yopmail.com Distribution: --- Created attachment 69368 --> https://bugs.winehq.org/attachment.cgi?id=69368 Log I can't select a controller in Assassin's Creed II. I am using a Xbox Series X/S controller. Using Wine 6.1-developer Tried using Wine 6.2 no luck. Distro: Linux Mint 19.0 Cinnamon 64 bit Arch: 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.

1 12

[Bug 50117] New: winedbg --gdb doesn't work
by WineHQ Bugzilla June 6, 2021

June 6, 2021

https://bugs.winehq.org/show_bug.cgi?id=50117 Bug ID: 50117 Summary: winedbg --gdb doesn't work Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: tomsod-m(a)ya.ru Distribution: --- After updating wine, winedbg's GDB mode stopped working for me. Instead of attaching to a program, it starts the program, then terminates itself. The latest unaffected version is 5.17; 5.18 to 5.21 all have this bug. The default mode of winedbg (without --gdb) works as expected, however. Steps to reproduce: run e.g. "winedbg --gdb notepad.exe". Expected behavior: winedbg stops at notepad's entry point and prompts for commands. Observed behavior: winedbg quits almost immediately, notepad runs freely. -- 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 11

[Bug 50594] New: Surge 1.6.6 VST works but shows only blank window
by WineHQ Bugzilla June 6, 2021

June 6, 2021

https://bugs.winehq.org/show_bug.cgi?id=50594 Bug ID: 50594 Summary: Surge 1.6.6 VST works but shows only blank window Product: Wine Version: 6.1 Hardware: x86-64 URL: https://github.com/surge-synthesizer/releases/releases /download/1.6.6/Surge-1.6.6-Setup.exe OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: and3md(a)gmail.com Distribution: --- Created attachment 69279 --> https://bugs.winehq.org/attachment.cgi?id=69279 Wine log Steps to reproduce: 1. Install LMMS - https://github.com/LMMS/lmms/releases/download/v1.2.1/lmms-1.2.1-win64.exe 2. Download and install Surge - https://github.com/surge-synthesizer/releases/releases/download/1.6.6/Surge… 3. Open LMMS 4. Change plugin embedding in Settings to No embedding (this is workaround of https://bugs.winehq.org/show_bug.cgi?id=48527) 5. Restart LMMS 4. Open the instruments plugins tab 5. Drag VeSTige to Song Editor window 6. Click Vestige in Song editor to show Vestige GUI 7. In Vestige Window click green folder icon 8. Go to Surge.dll 9. Click Open 10. Empty window appears On Windows 10 works ok. There are in log a lot of lines like: 017c:fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (0x1): monitor setting ignored 0188:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 0188:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #3: 0188:fixme:d3d_shader:print_glsl_info_log Vertex info 0188:fixme:d3d_shader:print_glsl_info_log ----------- 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[0].zw" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[2].zw" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[3].zw" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[5]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[6]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[7]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[8]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[9]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[10]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[11]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[12]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[13]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[14]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "vs_out[15]" might be used before being initialized 0188:fixme:d3d_shader:print_glsl_info_log 0188:fixme:d3d_shader:print_glsl_info_log Fragment info 0188:fixme:d3d_shader:print_glsl_info_log ------------- 0188:fixme:d3d_shader:print_glsl_info_log 0(37) : warning C7050: "R1.yzw" might be used before being initialized -- 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 2

[Bug 50613] New: several Wine Mono tests fail to load a referenced assembly on x86_64
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=50613 Bug ID: 50613 Summary: several Wine Mono tests fail to load a referenced assembly on x86_64 Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- When running the x86_64.bug-324535 testcase from Wine Mono, it fails with this exception: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'bug-324535-il, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. File name: 'bug-324535-il, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' [ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not load file or assembly 'bug-324535-il, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Test failed(1): x86_64.bug-324535 0 tests passed, 1 tests failed This can easily be checked by downloading the wine-mono tests zip file and running: $ wine run-tests.exe x86_64.bug-324535 Other testcases fail in a similar way, but only when run in a 64-bit process. For example, x86.bug-324535 passes. Bisect result: 7203ad0ecd06b451116fcfe3b08e4d620e853bd5 is the first bad commit commit 7203ad0ecd06b451116fcfe3b08e4d620e853bd5 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Jan 21 12:31:34 2021 +0100 ntdll: Load the COR header directly from the file handle. -- 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 6

[Bug 48043] New: user32:dce has a pair of random failures
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=48043 Bug ID: 48043 Summary: user32:dce has a pair of random failures Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 65584 --> https://bugs.winehq.org/attachment.cgi?id=65584 user32:dce: Loop over the test_destroyed_window() for 2 random failures. user32:dce has a pair of random failures in test_destroyed_window(): dce.c:648: Test failed: wrong window dce.c:658: Test failed: DC for destroyed window not reused One either gets the first one alone or both together. See https://test.winehq.org/data/tests/user32:dce.html These happen at random on a wide range of Windows versions: wxppro, w2003std, w2008s64, fg-win7u64-*, w1064v1507, w1064v1607. On Windows 10 the same type of error sometimes happens in test_dc_attributes() on line 127 which is another "wrong window\n" check. The attached patch loops over test_destroyed_window() which is sufficient to make these failures systematic. This can hopefully help debug the issue and make sure these are fixed. -- 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 15781] New: Can't run AllInOne-Office 5
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

http://bugs.winehq.org/show_bug.cgi?id=15781 Summary: Can't run AllInOne-Office 5 Product: Wine Version: 1.1.7 Platform: Other URL: http://www.allinone-office.de/ OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com A user asked for this package here: http://www.linux-forum.de/warenwirtschaft-allione-5-0-a-20117.html so I tried installing it. First, you have to set your language to German, e.g. LANG=DE_de.UTF-8 or it commplains about a language mismatch. Then, you have to set your Windows version to NT 4 with winecfg, else it complains that it needs Windows NT 4 or higher. Then it installs. The font in the installer is almost too tiny to read, even with corefonts installed. It first silently installs the Access 2002 runtime libraries and Jet 40, and those subinstallers aren't particularly happy; they both end with err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned 1627 but the main installer continues blindly. It asks if you want to keep the existing version of some wine dll; I said yes. It installs a menu item showing that the way to run the app is wine "C:\\Program Files\\Common Files\\Microsoft Shared\\Access Runtime\\Office10\\MSAccess.exe" /Runtime "C:\\Program Files\\AllInOne-Office\\AllInOne-Office.mde" but that fails with file not found... maybe because of the access runtime installation problem? -- 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 13

[Bug 50224] New: Grand Theft Auto 4: Crashes when starting the game
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=50224 Bug ID: 50224 Summary: Grand Theft Auto 4: Crashes when starting the game Product: Wine Version: 5.8 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sterum77(a)gmail.com Created attachment 68729 --> https://bugs.winehq.org/attachment.cgi?id=68729 backtrace of GTA IV After starting the game it immediately crashes and generates the attached output. As with wine version 4.X the game runs fine, so it looks like something is broken in version 5.X. -- 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 47180] New: Nocturne unhandled exception bug on startup
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=47180 Bug ID: 47180 Summary: Nocturne unhandled exception bug on startup Product: Wine Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jagsoul87(a)gmail.com Distribution: --- Created attachment 64434 --> https://bugs.winehq.org/attachment.cgi?id=64434 Unhandled exception register dump/log file When trying to run Nocturne the game crashes displaying an error message, when I click on "show details" it shows the following message: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code. The following register dump and full log file it's attached to this bug report. -- 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 8

[Bug 50366] New: Starcraft Remastered unable to create local LAN multiplayer game.
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=50366 Bug ID: 50366 Summary: Starcraft Remastered unable to create local LAN multiplayer game. Product: Wine-staging Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: darinsmiller(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- When trying to create a LAN game in Starcraft Remastered: 1st attempt: Message pop says "Failed to advertise the game. (Error 5:12)." 2nd attempt: The "Creating game" pop-up window displays indefinitely and no game is ever created. Lutris with wine version 5.7.10-x86_64 is able to create LAN games in Starcraft Remastered. Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-33-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 NVidia Driver: 455.45.01 -- 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 28

[Bug 51188] New: test_user_shared_data() fails in ntdll:virtual
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=51188 Bug ID: 51188 Summary: test_user_shared_data() fails in ntdll:virtual Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 70061 --> https://bugs.winehq.org/attachment.cgi?id=70061 AllFeatures traces test_user_shared_data() fails on Windows 7 and 8.1 in ntdll:virtual. https://test.winehq.org/data/patterns.html#ntdll:virtual On Windows 7 there are two failures: virtual.c:962: Test failed: Got unexpected AllFeatures[1] 128, expected 256. virtual.c:966: Test failed: Got unexpected Features[1].Size 128, expected 256. And on Windows 8.1 there is one: virtual.c:957: Test failed: Got unexpected AllFeatureSize 0. The test also has a special case which claims to be for Windows 10 Pro, though in fact the broken behavior seems to describe the behavior of all Windows 10 versions: ok(xstate.AllFeatures[i] == feature_sizes[i] || broken(!xstate.AllFeatures[i]) /* win10pro */, Given that this is related to processor features it's interesting to check what processors are involved: https://testbot.winehq.org/JobDetails.pl?Key=91253 w7u Win7 IvyBridge-IBRS (QEmu) fails w7pro64 Win7 SandyBridge (QEmu) success w2008s64 Win2008 kvm64 (QEmu) skipped (missing XState features) cw-gtx560 Win8.1 i7-2600K fails cw-rx460 Win8.1 i7-2600K fails w8 Win8.1 kvm32 (QEmu 32-bit) skipped (missing XState features) w864 Win8.1 core2duo (QEmu) skipped (missing XState features) cw-rx460 Win10 1507 i7-2600K broken (success) w1064v1507 Win10 1507 IvyBridge-IBRS (QEmu) broken (success) w1064v1607 Win10 1607 IvyBridge-IBRS (QEmu) broken (success) w1064v1709 Win10 1709 IvyBridge-IBRS (QEmu) broken (success) w1064v1809 Win10 1809 IvyBridge-IBRS (QEmu) broken (success) w1064v1909 Win10 1909 IvyBridge-IBRS (QEmu) broken (success) w10pro64 Win10 2004 IvyBridge-IBRS (QEmu) broken (success) w1064 Win10 2009 IvyBridge-IBRS (QEmu) broken (success) So it looks like there is no XState support on kvm32, kvm64 and core2duo processors which explains why the TestBot gets no failure on Windows 8.1. As for the half-size issue on w7u, this may be because that processor is 32-bit and not 64-bit. Finally, at best the comment for the broken(!xstate.AllFeatures[i]) is wrong, or that broken statement itself is wrong given that it considers the behavior of all Windows 10 versions to be broken. -- 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