wine-bugs April 2023

wine-bugs@winehq.org

1 participants
3565 discussions

[Bug 53789] New: charmap.exe from ReactOS leads to heap corruption under Wine
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=53789 Bug ID: 53789 Summary: charmap.exe from ReactOS leads to heap corruption under Wine Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 73279 --> https://bugs.winehq.org/attachment.cgi?id=73279 charmap file to reproduce Just for the record. This crash happens with certain fonts only, I used the Fixedsys font (https://aur.archlinux.org/packages/ttf-fixedsys-excelsior-linux) Attaching files to reproduce, from ROS commit 9cc9a26392ea4cc246284af61185db01f8212ca9. Problem is this line: https://gitlab.winehq.org/wine/wine/-/blob/wine-7.18/dlls/gdi32/uniscribe/s… where the index is < 0 Merge request (WIP): https://gitlab.winehq.org/wine/wine/-/merge_requests/1054 -- 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 53787] New: charmap.exe from ReactOS crashes under Wine with stackoverflow
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=53787 Bug ID: 53787 Summary: charmap.exe from ReactOS crashes under Wine with stackoverflow Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 73278 --> https://bugs.winehq.org/attachment.cgi?id=73278 charmap file to reproduce This crash happens with certain fonts only, I used the Fixedsys font (https://aur.archlinux.org/packages/ttf-fixedsys-excelsior-linux) Attaching files to reproduce, from ROS commit 9cc9a26392ea4cc246284af61185db01f8212ca9. -- 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 42787] New: Gal*Gun: Double Peace hangs when focus is lost
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=42787 Bug ID: 42787 Summary: Gal*Gun: Double Peace hangs when focus is lost Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: thexzoron(a)riseup.net Distribution: --- Created attachment 57812 --> https://bugs.winehq.org/attachment.cgi?id=57812 the debug log of this session When playing this game and you either switch workspaces or get the mouse out of the game it will lock up and the video will freeze but the audio will still play until you restart the window manager (in my cause i3). In some cases some of the audio cuts out and the game cannot be resumed however, I was not able to get to a scenario while logging where I could not resume the game after a window manager restart. -- 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 5

[Bug 48951] New: NVDA settings menu hangs
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=48951 Bug ID: 48951 Summary: NVDA settings menu hangs Product: Wine Version: 5.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: oleacc Assignee: wine-bugs(a)winehq.org Reporter: contact(a)jookia.org Distribution: --- NVDA's settings menu hangs due to it waiting on IAccPropServices's SetHwndPropServer and later ClearHwndProps methods. Commenting them out in NVDA's code shows no visible changes, likely due to the rest of the accessibility code being unimplemented. -- 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 45676] New: Keyboard non-functioning in Dark Souls 3
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=45676 Bug ID: 45676 Summary: Keyboard non-functioning in Dark Souls 3 Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hiigaran(a)hotmail.com Distribution: --- What works: - Game starts up - Main menu loads - Character creation works - Pre-game cinematic works - All mouse-related functions work What doesn't work: - Interacting with the main menu or in-game settings using the keyboard - In-game keyboard controls (movement, etc.) Pressing any key causes nothing to happen. Holding the key down for several seconds will cause the key to be registered for an instant. For example, pressing W to move the character forward will result in no action. Holding the key down will cause the character to step forward slightly, after several seconds. This essentially makes the game unplayable. Oddly enough, when naming your character on the character creation screen, the text box where you type a name in to actually works without issue. Issue is present on a prefix with no overrides. Tested on all Windows versions. Issue is also present while using DXVK. Ubuntu 18.04 Nvidia 396.51 -- 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 2

[Bug 44682] New: Kingdom Come: Deliverance, The Witcher 3: low performances
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=44682 Bug ID: 44682 Summary: Kingdom Come: Deliverance, The Witcher 3: low performances Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: ben(a)tokidev.fr Distribution: --- Using the nvidia latest proprietary drivers and wine-3.3, it seems there are low performances on both Kingdom Come: Deliverance and The Witcher 3 (despite, for the later at least, bug #42592 being marked as fixed in 3.3). This is using CSMT (by explicitly enabling it in the registry), and with __GL_THREADED_OPTIMIZATIONS=0 (as suggested by the aforementioned bug report). Yet when using wine-2.21-staging with CSMT, performances are much better. Using wine-3.3-staging (the new 3.x rebased staging fork by alesliehughes@github) with CSMT does not seem to produce good results either (that is, not better than normal 3.3). As an example, for Kingdom Come: Deliverance with details set to high on a 1070TI and in the exact same conditions: * Wine 3.3 produces ~5 to 10 FPS. * Wine 3.3-staging produces roughly the same. * Wine 2.21-staging produces ~20 to 30 FPS. The results are similar in The Witcher 3 (3.3 is pretty laggy in ultra, although almost playable; 3.3-staging is the same; yet 2.21-staging makes the game completely playable at the same level of details and performances are better by at least twice). There are no explicit messages in the log that may suggest an easily identifiable cause. -- 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 45989] New: The Witcher 3 flickers horribly and has artifacts
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=45989 Bug ID: 45989 Summary: The Witcher 3 flickers horribly and has artifacts Product: Wine Version: 3.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alex_y_xu(a)yahoo.ca Distribution: Gentoo See the attached video. Basically, certain areas of the screen (e.g. most of Geralt, the outside sky, certain interior walls) flicker very badly. Also, there is a grassy-looking wall in the middle of the room. I am using a Northern Islands class card, so Vulkan is not supported. I am using Mesa 18.2.2. Apologies for the potato quality recording; I'm using sway at the moment and video recording isn't properly supported. I did try TW3 on X though and it had the same results. -- 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 47227] New: The Witcher 3 GOG patch 1.3: Rumblepad 2 D-pad doesn' t work after update to version 4.8 Staging
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=47227 Bug ID: 47227 Summary: The Witcher 3 GOG patch 1.3: Rumblepad 2 D-pad doesn't work after update to version 4.8 Staging Product: Wine-staging Version: 4.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue.krishna(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 64495 --> https://bugs.winehq.org/attachment.cgi?id=64495 terminal output to the bug I have a specific problem with these buttons: https://i.imgur.com/P49Q2QF.jpg With version 4.7 Staging the D-pad worked. And it seems like the upgrade to wine-4.8 (Staging) removed the D-pad support. All other buttons from the Rumblepad 2 still 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 4

[Bug 44561] New: The Witcher 3: Incorrect gamepad button mapping and not working triggers
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=44561 Bug ID: 44561 Summary: The Witcher 3:Incorrect gamepad button mapping and not working triggers Product: Wine Version: 3.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs(a)winehq.org Reporter: nickfaces(a)gmail.com Distribution: --- Problems with xpad (and steamos-xpad). With xboxdrv gamepad are not working. WIth -mimic-xpad and remapping buttons options game not launching. -- 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 43133] New: The Witcher 3: ambient occlusion distortions
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=43133 Bug ID: 43133 Summary: The Witcher 3: ambient occlusion distortions Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Created attachment 58341 --> https://bugs.winehq.org/attachment.cgi?id=58341 The Witcher 3: SSAO (ambient occlution) distortion When running The Witcher 3 with ambient occlusion on, there are various visual artifacts appearing. With SSAO, there is black dotted mesh, and with HBAO+ there are running black vertical lines. See attached screenshots. Game version: GOG, 1.31. System: Debian testing, x86_64. Graphics: AMD RX 480: AMD POLARIS10 (DRM 3.8.0 / 4.9.0-3-amd64, LLVM 3.9.1), Mesa 17.1.0-devel (git-af73acca2b). Resolution: 1920x1200. Settings: Max settings for all graphics, except Nvidia hairworks is off. -- 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 43786] New: The Witcher 3: textures disappear in some places when you move
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=43786 Bug ID: 43786 Summary: The Witcher 3: textures disappear in some places when you move Product: Wine Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Created attachment 59299 --> https://bugs.winehq.org/attachment.cgi?id=59299 The Witcher 3: Velen cave save with disappearing texture In some areas when you move, textures toggle, disappearing and appearing back. But they don't leave a transparent area, but rather just untextured surface when that happens. So I'm not sure if it's the same as other missing texture bugs or not. I attach a save in Velen cave where that happens, as well as a video capture of that texture toggling. Graphics: OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10 / DRM 3.15.0 / 4.12.0-2-amd64, LLVM 5.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.0-devel (git-3e54493265) -- 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 23

[Bug 43861] New: The Witcher: Movement problems
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=43861 Bug ID: 43861 Summary: The Witcher: Movement problems Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: const1993(a)gmail.com Distribution: --- The movement keys do not work right away, the character can continue to run for another 15 seconds after I stop moving -- 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 24

[Bug 50722] New: State of Decay 2: Juggernaut Edition icons rendering is wrong with OpenGL renderer
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=50722 Bug ID: 50722 Summary: State of Decay 2: Juggernaut Edition icons rendering is wrong with OpenGL renderer Product: Wine Version: 6.2 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 69472 --> https://bugs.winehq.org/attachment.cgi?id=69472 example wine-6.2-320-gee4e33ed9ac -- 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 42953] New: ffxiv dx11 fixme:d3d11: d3d11_device_CreateBlendState Per-rendertarget blend not implemented.
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=42953 Bug ID: 42953 Summary: ffxiv dx11 fixme:d3d11:d3d11_device_CreateBlendState Per-rendertarget blend not implemented. Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ssbkm(a)icloud.com Distribution: --- unhandled dx11 -- 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 11

[Bug 30400] New: Final Fantasy 7 in the first fight scene
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=30400 Bug #: 30400 Summary: Final Fantasy 7 in the first fight scene Product: Wine Version: 1.5.1 Platform: x86 URL: http://download.cnet.com/Final-Fantasy-VII-demo/3000-7 538_4-10020419.html OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Created attachment 39739 --> http://bugs.winehq.org/attachment.cgi?id=39739 terminal output Bug 9220 is fixed, so this is the next crash. Get the game from http://download.cnet.com/Final-Fantasy-VII-demo/3000-7538_4-10020419.html austin@aw21 ~ $ sha1sum ff7demo.zip 79a555cd1874410a93952486e511bb8492e82a56 ff7demo.zip unzip/run. Bug 9220 would crash it once Cloud swung his sword. This no longer happens, the fight scene starts, then about 15 seconds later => crash. -- 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 21

[Bug 54517] New: riched20:editor - KDE? Clipboard interference causes test_EM_SETUNDOLIMIT() failures
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54517 Bug ID: 54517 Summary: riched20:editor - KDE? Clipboard interference causes test_EM_SETUNDOLIMIT() failures Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- riched20:editor - KDE? Clipboard interference causes test_EM_SETUNDOLIMIT() failures: editor.c:3667: Test failed: EM_SETUNDOLIMIT didn't allow the first undo with UNDOLIMIT set to 2 editor.c:3670: Test failed: EM_SETUNDOLIMIT didn't allow a second undo with UNDOLIMIT set to 2 See https://test.winehq.org/data/patterns.html#riched20:editor These failures mostly happen on my desktop, fg-deb64, though they did happen a few times on on master and lastestmaster (sic) too (latestmaster did not have that issue). * My desktop is Debian 11 + KDE. * master and lastestmaster are Linux Mint 21 (desktop environment unknown) On my desktop, whenever Wine modifies the clipboard, some non-Wine process accesses it and sometimes causes the clipboard content to be lost. Whether that has an impact on the tests depends on whether the test is done with the clipboard content by the time that access happens, i.e. there is a race condition. test_EM_SETUNDOLIMIT() does multiple pastes in a row (101 + 3), each of which accesses the clipboard, which leaves time for that other process to cause the clipboard content to be lost. This results in some pastes not happening so that there are fewer pastes to undo than expected. Hence the failures above. The test could be modified to check the length of the text field as a way to verify that it got the expected number of successful pastes. If not, it could either limit undos to however many pastes succeeded, or redo a copy plus more pastes to reach the target number. But I don't remember losing the clipboard content outside of Wine. Of course, unlike Wine's tests I never perform hundreds of copy/pastes per second so maybe that's why. Anyway, there may be something wrong in Wine and then fixing that would be a better approach. Or it may be a bug in some other component on my desktop that mishandles the clipboard. Also, even if the clipboard content is not lost, the WM_PASTE handling does a simple OpenClipboard() which would fail if winex11 is already accessing it to handle a query from some other process in the system. That seems too fragile and would also cause missing undos. I don't know how Windows behaves in that case though : Does the WM_PASTE simply fail? Is the OpenClipboard() operation repeated indefinitely? Just a few 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.

1 4

[Bug 54007] New: in kde plasma fullscreen videogames cause gap between taskbar and bottom edge of the screen
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54007 Bug ID: 54007 Summary: in kde plasma fullscreen videogames cause gap between taskbar and bottom edge of the screen Product: Wine-staging Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: HarlanStaggs(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73586 --> https://bugs.winehq.org/attachment.cgi?id=73586 this is how it looks with and without launched game characteristics: Operating System: Nobara Linux 36 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-201.fc36.x86_64 (64-bit) Graphics Platform: X11 how to reproduce: 1) launch some fullscreen videogame (personally i do it with lutris from flathub, maybe its important) 2) alt+tab to another non-fullscreen window 3) put cursor in bottom edge of the screen 4) try to switch windows with mouse wheel 5) notice small (several pixels height) gap between bottom edge of the screen and taskbar, and also between taskbar and current non-fullscreen window in focus. 6) close fullscreen videogame 7) everything is normal, taskbar is adjacent to the bottom edge of the screen without gaps this started to happen after update to wine-7.22 (Staging), i've never seen this before, so i assume this bug occurs in this particular version. -- 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 54854] New: Locking the KDE screen causes user32:win to fail systematically
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54854 Bug ID: 54854 Summary: Locking the KDE screen causes user32:win to fail systematically Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Locking the KDE screen causes user32:win to fail systematically. Specifically it gets failures in test_nonclient_area(): win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. win.c:1581: Test failed: Got unexpected color 0xc0c0c0. in test_activateapp(): win.c:11013: Test failed: Expected foreground window 0, got 00FE0060 win.c:11019: Test failed: Expected foreground window 002D0142, got 00FE0060 win.c:11082: Test marked todo: Expected WM_ACTIVATEAPP(0), did not receive it. and in test_topmost(): win.c:11683: Test failed: 01ED0126: expected prev 005D00BE, got 00000000 win.c:11697: Test failed: hwnd should NOT be topmost win.c:11699: Test failed: 01ED0126: expected NOT topmost win.c:11643: Test failed: 1: hwnd 01ED0126 is still topmost win.c:11724: Test marked todo: owner should be topmost win.c:11727: Test marked todo: hwnd2 should be topmost win.c:11750: Test marked todo: hwnd should NOT be topmost win.c:11764: Test marked todo: hwnd should NOT be topmost win.c:11805: Test marked todo: hwnd should be topmost win.c:11807: Test succeeded inside todo block: child should be topmost win.c:11809: Test marked todo: child2 should be topmost win.c:11810: Test failed: grandchild should be topmost win.c:11818: Test failed: child should NOT be topmost win.c:11821: Test succeeded inside todo block: grandchild should NOT be topmost win.c:11824: Test failed: 0007012A: expected NOT topmost win.c:11643: Test succeeded inside todo block: 5: hwnd 01070060 is still topmost [... more todos ...] See https://test.winehq.org/data/patterns.html#user32:win Only my development desktop runs the Wine tests in KDE and I normally avoid locking the screen when doing so. But it is quite remarkable that only three tests units have an issue with this configuration: this one, comctl32:tooltips (bug 54582) and user32:input (bug 54583). -- 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 54853] New: Locking the KDE screen causes user32:input to fail systematically
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54853 Bug ID: 54853 Summary: Locking the KDE screen causes user32:input to fail systematically Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Locking the KDE screen causes user32:input to fail systematically. Specifically it gets failures in test_rawinput(): input.c:2918: Test marked flaky: 4: unexpected WM_MOUSEMOVE message input.c:2929: Test failed: 4: Unexpected cursor movement input.c:2929: Test failed: 5: Unexpected cursor movement input.c:2929: Test failed: 6: Unexpected cursor movement input.c:2502: Test marked todo: Expected wparam 1, got 0 input.c:2929: Test failed: 7: Unexpected cursor movement input.c:2929: Test failed: 8: Unexpected cursor movement input.c:2918: Test marked flaky: 9: unexpected WM_MOUSEMOVE message input.c:2645: Test marked flaky: 9: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 9: Unexpected cursor movement input.c:2502: Test marked todo: Expected wparam 1, got 0 input.c:2645: Test marked flaky: 10: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 10: Unexpected cursor movement input.c:2502: Test marked todo: Expected wparam 1, got 0 input.c:2645: Test marked flaky: 11: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 11: Unexpected cursor movement input.c:2645: Test marked flaky: 12: foreground process expected WM_MOUSEMOVE message input.c:2929: Test failed: 12: Unexpected cursor movement input.c:2921: Test marked todo: 13: expected WM_INPUT message input.c:2929: Test failed: 13: Unexpected cursor movement input.c:2929: Test failed: 14: Unexpected cursor movement input.c:2929: Test failed: 15: Unexpected cursor movement input.c:2929: Test failed: 16: Unexpected cursor movement and in test_GetMouseMovePointsEx_process(): input.c:1730: Test failed: expected to get 64 mouse move points but got -1 input.c:1741: Test failed: expected to get 64 mouse move points but got -1 input.c:1787: Test marked todo: expected to get -1 mouse move points but got 64 input.c:1788: Test marked todo: expected ERROR_ACCESS_DENIED got -559038737 See https://test.winehq.org/data/patterns.html#user32:input Only my development desktop runs the Wine tests in KDE and I normally avoid locking the screen when doing so. But it is quite remarkable that only three tests units have an issue with this configuration: this one, comctl32:tooltips and user32:win. -- 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 54852] New: Locking the KDE screen causes comctl32:tooltips to fail systematically
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54852 Bug ID: 54852 Summary: Locking the KDE screen causes comctl32:tooltips to fail systematically Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Locking the KDE screen causes comctl32:tooltips to fail systematically: tooltips.c:252: Test failed: 0: Failed to get current tool 0. tooltips.c:259: Test failed: 0: Unexpected hwnd CCCCCCCC. tooltips.c:260: Test failed: 0: Unexpected hinst CCCCCCCC. tooltips.c:261: Test failed: 0: Unexpected uId cccccccc. tooltips.c:262: Test failed: 0: Unexpected lParam cccccccc. [... same errors for iterations 1 to 5...] tooltips.c:504: Test marked todo: Adding the tool to the tooltip succeeded! tooltips.c:1150: Test marked todo: 0: Unexpected ret value 1, size 45, max size 44. tooltips.c:1218: Test failed: TTN_SHOW parent seq: the msg sequence is not complete: expected 0000 - actual 004e v6util.h:92: created cc6.manifest [... same errors again ...] See https://test.winehq.org/data/patterns.html#comctl32:tooltips Only my development desktop runs the Wine tests in KDE and I normally avoid locking the screen when doing so. But it is quite remarkable that none of the other comctl32 tests has any issue in that scenario, and that out of all the Wine tests only two others have extra failures (user32:input and user32:win). Also the failures are not unique to this case: * The test_customdraw() failures also happen on Windows, but only one at a time (bug 54580). * The test_TTN_SHOW() also happen randomly in Wine the rest of the time (bug 54581). Given that these failures are usually quite hard to reproduce, locking the KDE screen may make them easier to debug, assuming this case does not involve a totally different code path. -- 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 48046] New: Resident Evil 4 (Steam): Frame rate issues when clicking the left mouse button
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=48046 Bug ID: 48046 Summary: Resident Evil 4 (Steam): Frame rate issues when clicking the left mouse button Product: Wine Version: 4.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skidrowa(a)gmail.com Distribution: --- The game's frame rate tanks when you click the left mouse button and can go as low as 5 FPS if you hold click and move the mouse at the same time. The cursor also flickers between it's current position and the middle of the screen, making it virtually impossible to play using keyboard and mouse. -- 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 51372] New: Resident Evil 4 (2007) Sometimes crashes at startup.
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=51372 Bug ID: 51372 Summary: Resident Evil 4 (2007) Sometimes crashes at startup. Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: BOBBLOG(a)protonmail.com Distribution: --- Created attachment 70229 --> https://bugs.winehq.org/attachment.cgi?id=70229 RE4Terminal.txt Resident Evil 4 (2007) Sometimes crashes at startup. I see a few error messages about xrandr. I have attach the terminal messages. Tested in a wine prefix just d3dx9_30 installed by winetricks. -- 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 51325] New: Resident Evil 4 (2007) Hangs usually within 15-30 minutes.
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=51325 Bug ID: 51325 Summary: Resident Evil 4 (2007) Hangs usually within 15-30 minutes. Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: BOBBLOG(a)protonmail.com Distribution: --- Resident Evil 4 (2007) Ver.1.1.0 DVD Hangs usually within 15-30 minutes. Most times i see a message box of Microsoft Visual C++ Runtime Error "This application has requested the Runtime to terminate in an unusual way. Please contact the applications support team for more information." I tested this in a wine prefix with d3dx9 installed via winetricks because the game will not boot up with it. I tried WINEDEBUG=+msgbox but, every time i did the game would just hang and not show anything related to the message box. I did however get this message on the terminal. 01e4:fixme:d3d9:Direct3DShaderValidatorCreate9 Returning stub validator 67C9E028. 0454:err:quartz:BaseMemAllocator_Commit fnAlloc failed with error 0x8007000e 0454:err:quartz:BaseMemAllocator_Commit fnAlloc failed with error 0x8007000e 0454:err:gstreamer:gstdemux_init_stream Failed to commit allocator, hr 0x8007000e. radeon: mmap failed, errno: 12 radeon: mmap failed, errno: 12 0174:err:d3d:wined3d_debug_callback 0x8f4a328: "GL_OUT_OF_MEMORY in glTexSubImage". This err message was only displayed once in the many times that the game hanged. -- 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 50550] New: Resident Evil 4 Ultimate HD crashes at gameplay near beginning of game
by WineHQ Bugzilla 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=50550 Bug ID: 50550 Summary: Resident Evil 4 Ultimate HD crashes at gameplay near beginning of game Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru Distribution: --- Created attachment 69220 --> https://bugs.winehq.org/attachment.cgi?id=69220 Backtrace of error Steam version of Resident Evil 4 Ultimate HD crashes at gameplay near beginning of 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 4

[Bug 41271] New: Fallout 4 - Audio issues (no sounds, hangs when playing intro video)
by wine-bugs＠winehq.org 20 Apr '23

20 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=41271 Bug ID: 41271 Summary: Fallout 4 - Audio issues (no sounds, hangs when playing intro video) Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: kimmo.myllyvirta(a)gmail.com Distribution: --- Created attachment 55571 --> https://bugs.winehq.org/attachment.cgi?id=55571 1.9.18 logs This could be dupe of bug #36977, but also hits bug #39402 possibly some others too. But since I can't find a decent workaround which works for Fallout 4, it might be ok to open a new bug. Not quite sure if the component is correct, either xaudio2 or dsound anyway. A bunch of logs attached, see below what they mean. Steam version of the game, only Steam and Fallout 4 installed to a clean prefix. Steam installs xact from _CommonRedist when first time launching the game. When the game is started it hangs when it should play the intro video; +tid,+dsound log attached (Log: fo4_tid_dsound.txt, +tid,+dsound). This could be bug #36977, since the game uses radgametools bink. With builtin xaudio2_7 the intro video works sometimes (extremely rarely, sorry I don't have decent log of this). But after the video is finished it will always hang after; warn:xaudio2:IXAudio2Impl_CreateSourceVoice OpenAL can't convert this format! when it tries to play the music for the main menu. (see bug #39402) With xaudio2_7 set to disabled the intro video works, but again extremely rarely. And it results to no sounds in Fallout 4 since bink player uses dsound, but Fallout 4 itself doesn't, it seems. There is "sAudioAPI=XAudio2" setting in Fallout4.ini, but it is a legacy setting. I can't find any indication of it supporting anything else than xaudio2 (on older Bethesda games there was other options available). Now the weird hack part; Since this feels like a race condition, I added usleep(100000) to the beginning of IDirectSound8Impl_Release, which seems to help a lot (this issue might not have anything to do with dsound release, that's just the first place I tried); - native xaudio2: the intro video works, and the music in main menu plays ok, always - success :) (Log: fo4_tid_dsound_sleep_hack.txt, +tid,+dsound ) - builtin xaudio2_7: the intro video works, but the music in main menu doesn't and the game hangs (as expected) after; warn:xaudio2:IXAudio2Impl_CreateSourceVoice OpenAL can't convert this format! (Log: fo4_tid_dsound_xaudio2_sleep_hack_builtin_xaudio2_7.txt, +tid,+dsound,+xaudio2 ) - disable xaudio2_7: the intro video works, no music in the main menu, but the game doesn't hang (Log: fo4_tid_dsound_sleep_hack_disable_xaudio2_7, +tid,+dsound ) Notes; - The main menu is just a black screen (lots of d3d11 fixmes in those logs), you just have to listen and imagine you are there :) - I also tried xact and xact_jun2010 with winetricks - those make no difference, works just like the xact shipped with 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.

2 38

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs April 2023