- Wine-Bugs - list.winehq.org

[Bug 53026] New: F.E.A.R. (original) has "Disconneted from server" massage every time starting a new game
by WineHQ Bugzilla June 13, 2022

June 13, 2022

https://bugs.winehq.org/show_bug.cgi?id=53026 Bug ID: 53026 Summary: F.E.A.R. (original) has "Disconneted from server" massage every time starting a new game Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: VladimirVSC(a)yandex.ru Distribution: --- It is impossible to start a new game because of this (however the benchmark works good). Don't know, if it is a Wine bug or a game quirk, but for Windows 7 (x64) the same copy of the game works fine. -- 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 46609] New: openbor: executable freezes while loading game ( Marvel Infinity War)
by wine-bugs＠winehq.org June 13, 2022

June 13, 2022

https://bugs.winehq.org/show_bug.cgi?id=46609 Bug ID: 46609 Summary: openbor: executable freezes while loading game (Marvel Infinity War) Product: Packaging Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: cardogar(a)hotmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Created attachment 63509 --> https://bugs.winehq.org/attachment.cgi?id=63509 Log file When running the openbor game Marvel Infinity War the wine-preloder freezes (not responding). Game can be downloaded here http://www.zvitor.com.br/Downloads/miw_v1.2.rar Attached console output. Games constructed with different openbor engine versions work. -- 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 10

[Bug 53149] New: quartz:filtergraph - test_filter_state() has a pair of rare failures on Windows 10
by WineHQ Bugzilla June 13, 2022

June 13, 2022

https://bugs.winehq.org/show_bug.cgi?id=53149 Bug ID: 53149 Summary: quartz:filtergraph - test_filter_state() has a pair of rare failures on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com quartz:filtergraph - test_filter_state() has a rare failure on Windows 10: filtergraph.c:3730: Test failed: Got state 2. filtergraph.c:3731: Test failed: Got state 2. https://test.winehq.org/data/patterns.html#quartz:filtergraph The failure is known to happen on w1064v1909 and w10pro64 (21H1), but its failure rate is pretty low (3.2%) so it's unclear if other Windows versions are affected too. It does seem that the failure is specific to 64-bit code. -- 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 1

[Bug 53146] New: kernel32:process - test_handle_list_attribute() has a rare failure on Windows 10 1607+
by WineHQ Bugzilla June 13, 2022

June 13, 2022

https://bugs.winehq.org/show_bug.cgi?id=53146 Bug ID: 53146 Summary: kernel32:process - test_handle_list_attribute() has a rare failure on Windows 10 1607+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:process - test_handle_list_attribute() has a rare failure on Windows 10 1607+: On Windows 10 1607: process.c:4288: Test failed: Unexpected return value, error 127. where 127 == ERROR_PROC_NOT_FOUND And on Windows 10 1709+: process.c:4288: Test failed: Unexpected return value, error 203. 203 == ERROR_ENVVAR_NOT_FOUND which is a bit strange https://test.winehq.org/data/patterns.html#kernel32:process The failure rate is about 5.3%. -- 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 1

[Bug 53143] New: kernel32:debugger - test_debugger() fails randomly on Windows 10
by WineHQ Bugzilla June 12, 2022

June 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=53143 Bug ID: 53143 Summary: kernel32:debugger - test_debugger() fails randomly on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - test_debugger() fails randomly on Windows 10: debugger.c:1760: Test failed: unexpected instruction pointer 778B2A0C https://test.winehq.org/data/patterns.html#kernel32:debugger The address changes with every run which causes this failure to always look like a new one. -- 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 1

[Bug 53141] New: dsound:dsound - test_notify() has a rare failure on Windows
by WineHQ Bugzilla June 12, 2022

June 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=53141 Bug ID: 53141 Summary: dsound:dsound - test_notify() has a rare failure on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dsound:dsound - test_notify() has a rare failure on Windows: dsound.c:1072: Test failed: expected 0. got 258 or sometimes dsound.c:1072: Test failed: expected 1. got 258 or even dsound.c:1060: Test failed: got 00000000 dsound.c:1072: Test failed: expected 1. got 258 https://test.winehq.org/data/patterns.html#dsound:dsound The failure rate appear to be about 6.6% and this seems to only happen on Windows 10 1809+, real hardware (cw-gtx560) and VMs alike. This failure did not happen on all test configurations. Maybe there's something special about those that got this failure, or the others just got lucky due to the low failure rate. -- 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 1

[Bug 53140] New: Origin spawn multiple invisible Windows
by WineHQ Bugzilla June 12, 2022

June 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=53140 Bug ID: 53140 Summary: Origin spawn multiple invisible Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)tutanota.com Distribution: --- Created attachment 72583 --> https://bugs.winehq.org/attachment.cgi?id=72583 Origin windows seen from a Wine virtual desktop EA Origin when opened spawns extra windows that shouldn't be seen and do various things (they can be seen in the attachment). The first is a digital clock that only updates when focused. The second and the fourth one show garbage, while the third one is just a logo. The fifth one shows "OFFLINE MODE", and clicking it actually puts you in offline mode. The sixth one shows a list of items, all but "Achievements" and "Download Manager" are functional. They can be closed with no apparent side effect. Closing Origin's main window and then reopening it doesn't spawn them again. These windows are normally invisible (even in the taskbar), but they can be seen by either using Wine virtual desktop (where they can be seen in the taskbar) or by using a tiling window manager (the behavior depends on the WM: Sway for example tiles the extra windows while leaving the main window stacked (though the mouse cursor may stop matching the actual position), kwin-tiling doesn't tile the extra window but leaves extra space as if they need to be tiled while the main windows is stacked and very slow and unresponsive, Bismuth doesn't know how to handle this and crashes the entire desktop environment). While I don't know if the fact that they exist in the first place is "intended", their behavior is certainly destructive (though it can be worked around by setting the tiled window managers to not tile Origin, it certainly isn't something that should be done). (Wine version is set to unknown because I tested the Lutris script with both Wine-lutris and Wine-tkg, but not vanilla Wine). -- 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 52837] New: The text cannot be displayed normally in the "小K直播姬" software
by WineHQ Bugzilla June 12, 2022

June 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=52837 Bug ID: 52837 Summary: The text cannot be displayed normally in the "小K直播姬" software Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 3238998313(a)qq.com Distribution: --- Created attachment 72232 --> https://bugs.winehq.org/attachment.cgi?id=72232 The log output from the terminal (the action is recorded). Run "Little K Live Ji" on the 7.6 version of the development branch, and the expected version of WineD3D is 1.2. The packages for Winehq are packaged by the distribution ArchLinux. See the log file for details. The official website of the software is https://yunboai.com/liverc; you can also get a complete copy of the software from here: https://www.123pan.com/s/lgeRVv-zauHd, password: wine. I looked at the output and everything seems to be working fine until line 1578, after doing the login it opens a new process and reports back and forth warnings and errors for d3d11, some modules and WineD3D. The main thing that affects my continued use of the software is that in this new process it barely displays text properly and is mostly blank. According to the information, the software cannot be run directly after the d3dx11 bug patch is applied by Winetricks. Main output: MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0 This software has not been tested in versions prior to 7.6. -- 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 53127] New: mmdevapi:render - test_clock() gets misfit fragments on Windows 10 2004+
by WineHQ Bugzilla June 12, 2022

June 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=53127 Bug ID: 53127 Summary: mmdevapi:render - test_clock() gets misfit fragments on Windows 10 2004+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mmdevapi:render - test_clock() gets misfit fragments failures on Windows 10 2004+: render.c:1040: Test failed: BufferSize 24576 misfits fragment size 720 at rate 48000 https://test.winehq.org/data/patterns.html#mmdevapi:render This failure is somewhat rare and only happens on Windows 10 >= 2004. It also never happened on the cw-gtx560 and cw-rx460 machines. So it's possible that this is a QEmu issue. The ill fitting fragment size is also always the same: 24576. -- 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 1

[Bug 53126] New: mmdevapi:render - test_clock() has timing-related failures
by WineHQ Bugzilla June 12, 2022

June 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=53126 Bug ID: 53126 Summary: mmdevapi:render - test_clock() has timing-related failures Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mmdevapi:render - test_clock() has timing-related failures: render.c:1114: Test failed: Position 54256 too far after playing 100ms https://test.winehq.org/data/patterns.html#mmdevapi:render These happen on Windows and Wine and are quite frequent but the position changes on every run causing the failure to always look new. It may be possible to reduce the frequency of the failures by improving the accuracy of the timing measurements but it's not clear if the failures can be completely eliminated without making the timing margins meaninglessly large. See also: https://www.winehq.org/pipermail/wine-devel/2020-November/176708.html -- 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 1