wine-bugs January 2024

wine-bugs@winehq.org

1 participants
2720 discussions

[Bug 55835] New: putenv clobbers previous getenv
by WineHQ Bugzilla 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=55835 Bug ID: 55835 Summary: putenv clobbers previous getenv Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: blitzkriegoutlaw(a)hotmail.com Distribution: --- Created attachment 75335 --> https://bugs.winehq.org/attachment.cgi?id=75335 Sample code performing a putenv/_putenv_s to an empty string will clobber a previous getenv. There may be other cases, but this is the one I ran into. I've attached sample code. On Windows it returns: AMD64 Family 23 Model 1 Stepping 2, AuthenticAMD AMD64 Family 23 Model 1 Stepping 2, AuthenticAMD On Wine it returns: x86 Family 6 Model 79 Stepping 1, GenuineIntel Family 6 Model 79 Stepping 1, GenuineIntel The string is globbered by the _setenv_s due to the shift in memory by removing another environment variable. -- 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 53516] New: user32:input failed due to unexpected WM_TIMECHANGE message
by WineHQ Bugzilla 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=53516 Bug ID: 53516 Summary: user32:input failed due to unexpected WM_TIMECHANGE message Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:input failed due to unexpected WM_TIMECHANGE message: input.c:4525: Test failed: SendInput triggered unexpected message 0x1e https://test.winehq.org/data/patterns.html#user32:input This happened on 2022-08-05 in the w10pro64-fr-64 test configuration. But user32:msg has also received such an unexpected message on 2022-08-02 on w10pro64-pt-BR-64 (see bug 53273). It appears this message is sent by Windows when an application modifies the system time. If the application is another test then it should make sure all such messages have been sent before continuing. But it is quite possible that this message is sent when Windows resynchronizes with some internet time server in which case this message could arrive in any test at any time. -- 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 51477] New: user32:input test_Input_blackbox() gets unexpected 00&41(A) keystate changes
by WineHQ Bugzilla 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=51477 Bug ID: 51477 Summary: user32:input test_Input_blackbox() gets unexpected 00&41(A) keystate changes Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_Input_blackbox() gets unexpected 00&41(A) keystate changes: https://test.winehq.org/data/patterns.html#user32:input input.c:757: Test failed: 0 (a4/0): 00 from 00 -> 81 unexpected input.c:757: Test failed: 0 (a4/0): 41 from 00 -> 01 unexpected * This exclusively happens for the first sendinput_test entry which is supposed to simulate pressing the left Alt key (VK_LMENU == 0xa1). * I do not know what the 00 virtual key code corresponds to. According to the failure message this key is getting pressed down and toggled. * The 41 virtual key code should be the 'A' key but that's not a toggle key (unlike, e.g., Caps Lock) so the low order bit should be meaningless. So it's strange that it changed from off to toggled. * These failures happen on the following machines: (41 corresponds to 100% reproducible, some machines may have fewer than 41 runs) 17 2008_newtb-w2008s64-32 1 2008_newtb-w2008s64-64 5 win7_newtb-w7u-2qxl 7 win81_cw-rx460-32 4 win1507_cw-gtx560-1507-32 5 win1507_cw-rx460-1507-32 1 win1709_cw-rx460-1709-64 39 win2009_cw-gtx560-2009-32 39 win2009_cw-gtx560-2009-64 41 win2009_cw-rx460-2009-32 41 win2009_cw-rx460-2009-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 4

[Bug 17414] New: user32/dde test crashes if +heap enabled
by wine-bugs＠winehq.org 26 Jan '24

26 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=17414 Summary: user32/dde test crashes if +heap enabled Product: Wine Version: 1.1.15 Platform: PC URL: http://test.winehq.org/data/6a1537c4b5037be5253c33021fda 3a02430533f7/wine_xp_ae-ub-810-heap/riched32:editor.html OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: enhancement Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=19484) --> (http://bugs.winehq.org/attachment.cgi?id=19484) backtrace in 1.1.15 wine: Unhandled page fault on read access to 0x00130000 at address 0x6045971b (thread 0009), starting debugger... ... =>0 0x6045971b CompareStringW+0x13b(lcid=1033, style=0, str1=0x130000, len1=0, str2=0x6074c780, len2=-1) [/home/austin/wine-git/dlls/kernel32/../../include/wine/unicode.h:216] in kernel32 (0x0032f848) 1 0x6045bed4 lstrcmpW+0x64(str1=<register EDI not in topmost frame>, str2=<register ESI not in topmost frame>) [/home/austin/wine-git/dlls/kernel32/locale.c:2834] in kernel32 (0x0032f878) 2 0x60681d7a dde_server_wndprocW+0x3da(hwnd=0xe0028, msg=1000, wparam=458798, lparam=<register EDI not in topmost frame>) [/home/austin/wine-git/dlls/user32/tests/dde.c:1215] in user32_test (0x0032f8b8) 3 0x6082337a WINPROC_wrapper+0x1a() in user32 (0x0032f8e8) 4 0x608237ca call_window_proc+0x6a(hwnd=<register EDI not in topmost frame>, msg=<register ESI not in topmost frame>, wp=458798, lp=1204994, result=0x32f998, arg=0x606819a0) [/home/austin/wine-git/dlls/user32/winproc.c:458] in user32 (0x0032f928) 5 0x60828af7 WINPROC_call_window+0xf7(hwnd=<register EDI not in topmost frame>, msg=1000, wParam=458798, lParam=1204994, result=0x32f998, unicode=1, mapping=WMCHAR_MAP_DISPATCHMESSAGE) [/home/austin/wine-git/dlls/user32/winproc.c:2218] in user32 (0x0032f968) 6 0x607e7ee6 DispatchMessageW+0x96(msg=<register EDI not in topmost frame>) [/home/austin/wine-git/dlls/user32/message.c:3122] in user32 (0x0032f9a8) 7 0x607a4037 WDML_SyncWaitTransactionReply+0xe7(hConv=0x1254b8, dwTimeout=<register ESI not in topmost frame>, pXAct=0x125508, ack=0x32fb84) [/home/austin/wine-git/dlls/user32/dde_client.c:1069] in user32 (0x0032fa08) 8 0x607a4b21 DdeClientTransaction+0x651(pData="test dde command", cbData=17, hConv=0x1254b8, hszItem=0xdead, wFmt=48879, wType=16464, dwTimeout=1000, pdwResult=0x32fb84) [/home/austin/wine-git/dlls/user32/dde_client.c:1225] in user32 (0x0032fa68) 9 0x60686158 test_dde_aw_transaction+0x638() [/home/austin/wine-git/dlls/user32/tests/dde.c:1374] in user32_test (0x0032fb98) ... 216 while (*s) s++; Attached is the backtrace...I've stripped out +heap, so the output is readable, but easily reproducible. -- 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 54089] New: user32:input - test_SendInput() sometimes gets an unexpected 0x738 message on w1064v1709
by WineHQ Bugzilla 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=54089 Bug ID: 54089 Summary: user32:input - test_SendInput() sometimes gets an unexpected 0x738 message on w1064v1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_SendInput() sometimes gets an unexpected 0x738 message on w1064v1709: * 2022-060-14 input.c:4439: Test failed: SendInput triggered unexpected message 0x60 input.c:4457: Test failed: SendInput triggered unexpected message 0x738 * 2022-12-05 input.c:4560: Test failed: SendInput triggered unexpected message 0x60 input.c:4578: Test failed: SendInput triggered unexpected message 0x738 See https://test.winehq.org/data/patterns.html#user32:input It's not clear why this only happens on w1064v1709. I suspect this is a repeat of bug 48815 where this 0x738 message was being sent to a message-only UserAdapterWindowClass window (but apparently that impacted all Windows 10 >= 1709). If so maybe user32:input should selectively ignore some messages like user32:win now does: commit fa28e05cf5b0101fb046c4845391634791268200 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Jan 31 14:18:07 2022 +0100 user32/tests: Ignore messages for UserAdapterWindowClass windows. Wine-Bug: https://bugs.winehq.org//show_bug.cgi?id=48815 Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 51473] New: user32:input Some SendInput() set LastError to ERROR_ACCESS_DENIED on cw-rx460 19.11.3
by WineHQ Bugzilla 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=51473 Bug ID: 51473 Summary: user32:input Some SendInput() set LastError to ERROR_ACCESS_DENIED on cw-rx460 19.11.3 Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com More specifically some cw-rx460 machines have the following failures: https://test.winehq.org/data/patterns.html#user32:input input.c:4410: Test failed: SendInput returned 1, error 0x5 input.c:4413: Test failed: SendInput returned 16, error 0x5 input.c:4464: Test failed: SendInput returned 16, error 0x5 These fail not because SendInput() failed, but because it modified LastError, setting it to ERROR_ACCESS_DENIED. This only happens on the following machines which have in common that they use the 19.11.3 Radeon driver which is the latest version that will run on these Windows versions: win1507_cw-rx460-1507-32 win1507_cw-rx460-1507-64 win81_cw-rx460-32 win81_cw-rx460-64 The failure is systematic on these machines. -- 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 51471] New: user32:input receives unexpected WM_SYSTIMER messages in test_SendInput()
by WineHQ Bugzilla 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=51471 Bug ID: 51471 Summary: user32:input receives unexpected WM_SYSTIMER messages in test_SendInput() Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:input sometimes receives unexpected WM_SYSTIMER messages in test_SendInput(): https://test.winehq.org/data/patterns.html#user32:input input.c:4477: Test failed: SendInput triggered unexpected message 0x118 Notes: * This is random: there is no machine where it happens systematically; and different machines don't necessarily have the issue on the same day. * This does not happen on a specific Windows version though not all seem to be impacted either. Specifically this issue has been seen on the following machines: win7_newtb-w7u-2qxl win7_newtb-w7u-de win7_newtb-w7u-el win7_newtb-w7u-es win7_newtb-w7u-pt-PT 2008_newtb-w2008s64 win81_cw-rx460 win1507_cw-gtx560-1507 win1507_cw-rx460-1507 win1909_cw-gtx560-1909 win2009_cw-gtx560-2009 win2009_cw-rx460-2009 * Maybe the following article can be useful: https://devblogs.microsoft.com/oldnewthing/20160624-00/?p=93745 -- 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 42784] New: Lost Planet dx10 demo black screen after starting new game
by wine-bugs＠winehq.org 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=42784 Bug ID: 42784 Summary: Lost Planet dx10 demo black screen after starting new game Product: Wine Version: 2.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andras(a)sth.sze.hu Distribution: --- Created attachment 57802 --> https://bugs.winehq.org/attachment.cgi?id=57802 +d3d11, + d3d_shader After starting new game or performance test in Lost Planet dx10 demo, it shows only black screen. It tries to create a geometry shader and fails. As far as I see, it want to use a vertex shader as geometry shader. See log file. -- 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 36007] New: oleaut32/vartype tests crash with WINEDEBUG=warn+heap
by wine-bugs＠winehq.org 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=36007 Bug ID: 36007 Summary: oleaut32/vartype tests crash with WINEDEBUG=warn+heap Product: Wine Version: 1.7.16 Hardware: x86 URL: https://test.winehq.org/data/7e874aed75765f3c017673178 cfd64301b7ba3ed/linux_ae-fedora64-heap/oleaut32:vartyp e.html OS: Linux Status: NEW Keywords: download, testcase Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com vartype.c:6446: LCIDs: System=0x00000409, User=0x00000409 vartype.c:6289: Test failed: unexpected len .. Backtrace: =>0 0x7b8519db CompareStringEx+0x1fb(locale=0x0(nil), flags=0, str1="??????????H", len1=0xffffffff, str2="test", len2=0xffffffff, version=(nil), reserved=0x0(nil), lParam=0) [/home/austin/wine-git/dlls/kernel32/../../include/wine/unicode.h:200] in kernel32 (0x0034fb78) 1 0x7b851a76 CompareStringW+0x65(lcid=<couldn't compute location>, flags=<couldn't compute location>, str1=<couldn't compute location>, len1=<couldn't compute location>, str2=<couldn't compute location>, len2=<couldn't compute location>) [/home/austin/wine-git/dlls/kernel32/locale.c:2979] in kernel32 (0x0034fbc8) 2 0x7b8521d8 lstrcmpW+0x67(str1=<couldn't compute location>, str2=<couldn't compute location>) [/home/austin/wine-git/dlls/kernel32/locale.c:3216] in kernel32 (0x0034fc18) 3 0x7ed4d53b test_bstr_cache+0x9a() [/home/austin/wine-git/dlls/oleaut32/tests/vartype.c:6290] in oleaut32_test (0x0034fca8) 4 0x7ed9e3e2 func_vartype+0xc1() [/home/austin/wine-git/dlls/oleaut32/tests/vartype.c:6449] in oleaut32_test (0x0034fd48) -- 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 54223] New: [Wine 8.0-rc2] [Severe Performance Regression] [Unigine Heaven Benchmark 4.0] Wine DirectX11 to OpenGL Severely Low FPS
by WineHQ Bugzilla 26 Jan '24

26 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=54223 Bug ID: 54223 Summary: [Wine 8.0-rc2] [Severe Performance Regression] [Unigine Heaven Benchmark 4.0] Wine DirectX11 to OpenGL Severely Low FPS Product: Wine Version: 8.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: CHECK_1234543212345(a)protonmail.com Distribution: --- ⬤ System Information: OS: Ubuntu 22.10 Kernel: 6.1.0 CPU: Ryzen 7 1700 GPU: XFX RX580 4GB Window Manager: OpenBox Compositor: No Compositor, Xorg TearFree Disabled ⬤ Issue: Wine's DirectX11 to OpenGL was the fastest on Wine 6.0, but then got a little slower on Wine 7.0 and got severely more slower when I tested with Wine 7.22 before I installed Wine 8.0-rc2. ⬤ Settings: RX580 locked to 300Mhz core clock and 300Mhz memory clock Quality: Low Resolution: 1280x720 Fullscreen: Unchecked ⬤ Information: Lutris was used to easily switch between Wine versions. Scene 2 is where the screen was moving across the bridge looking at the boat. You can switch scenes with in the Unigine Benchmark by using the "Backspace" and "Enter" keyboard keys. Unigine Heaven Benchmark 4.0 Results: -------------------- Wine staging 8.0-rc2 DX11 to OpenGL Scene 2: 41 FPS (41 FPS with WINEDEBUG=-all) Scene 3: 24 FPS (24 FPS with WINEDEBUG=-all) Wine staging 8.0-rc2 DX11 to Vulkan (winetricks renderer=vulkan) Scene 2: 26 FPS (with WINEDEBUG=-all) Scene 3: 15 FPS (with WINEDEBUG=-all) Wine staging 8.0-rc2 DX11 to Vulkan (DXVK 2.0) (./setup_dxvk.sh install) Scene 2: 84 FPS (with WINEDEBUG=-all) Scene 3: 104 FPS (with WINEDEBUG=-all) - Wine staging 8.0-rc2 DX9 to OpenGL Scene 2: 90 FPS (with WINEDEBUG=-all) Scene 3: 97 FPS (with WINEDEBUG=-all) Wine staging 8.0-rc2 DX9 to Vulkan (winetricks renderer=vulkan) CRASHES with an error dialog when starting benchmark Wine staging 8.0-rc2 DX9 to Vulkan (DXVK 2.0) (./setup_dxvk.sh install) Scene 2: 57 FPS (with WINEDEBUG=-all) Scene 3: 67 FPS (with WINEDEBUG=-all) - Wine staging 8.0-rc2 OpenGL to OpenGL Scene 2: 91 FPS (with WINEDEBUG=-all) Scene 3: 105 FPS (with WINEDEBUG=-all) -------------------- Wine staging 7.22 DX11 to OpenGL Same performance problem as wine 8.0-rc2 -------------------- Wine staging 7.0 DX11 to OpenGL Scene 2: 61 FPS (74 FPS with WINEDEBUG=-all) Scene 3: 32 FPS (61 FPS with WINEDEBUG=-all) - Wine staging 7.0 DX9 to OpenGL Scene 2: 88 FPS (with WINEDEBUG=-all) Scene 3: 83 FPS (with WINEDEBUG=-all) -------------------- Wine staging 6.0 DX11 to OpenGL Scene 2: 88 FPS (88 FPS with WINEDEBUG=-all) Scene 3: 48 FPS (71 FPS with WINEDEBUG=-all) - Wine staging 6.0 DX9 to OpenGL Scene 2: 88 FPS (with WINEDEBUG=-all) Scene 3: 78 FPS (with WINEDEBUG=-all) -------------------- Wine staging 5.1 DX11 to OpenGL Scene 2: 71 FPS (71 FPS with WINEDEBUG=-all) Scene 3: 48 FPS (55 FPS with WINEDEBUG=-all) -------------------- Wine staging 4.0 DX11 to OpenGL Scene 2: 75 FPS (84 FPS with WINEDEBUG=-all) Scene 3: 41 FPS (64 FPS with WINEDEBUG=-all) -------------------- Wine staging 3.0 DX11 to OpenGL Scene 2: 48 FPS (61 FPS with WINEDEBUG=-all) Scene 3: 27 FPS (44 FPS with WINEDEBUG=-all) The Unigine Benchmark Launcher opened very quickly with wine 3.0 -------------------- ⬤ Information: I had "Output debugging info" "Enabled" in Lutris at first with the DX11 to OpenGL tests and retested with "Output debugging info" "Disabled (default)" in Lutris, which just added the "WINEDEBUG=-all" environmental variable. The Wine 32-bit staging versions 7.0 to 3.0 was downloaded from: https://www.playonlinux.com/wine/binaries/phoenicis/staging-linux-x86/ The Unigine Heaven Benchmark Launcher was closed after starting each benchmark because the Unigine Heaven Benchmark Launcher was decreasing the FPS. ⬤ Conclusion: DirectX11 to OpenGL was the fastest in Wine 6.0 Somewhere between Wine 6.0 and Wine 7.0, Wine's DirectX11 to OpenGL became a bit more slower. Somewhere between Wine 7.0 and Wine 7.22, Wine's DirectX11 to OpenGL became severely more slower. Wine's OpenGL to OpenGL is currently faster than: DXVK (DXVK 2.0) (./setup_dxvk.sh install) Wine's DirectX9/DirectX11 to OpenGL (renderer=gl). Wine's DirectX9/DirectX11 to Vulkan (winetricks renderer=vulkan) Unigine Heaven Benchmark crashes when using DirectX9 to Vulkan (winetricks renderer=vulkan) but not with DXVK's DirectX9 to Vulkan (DXVK 2.0) (./setup_dxvk.sh install). Wine 3.0 Opens the Unigine Heaven Benchmark launcher very quickly. But then with Wine 4.0 and above, the Unigine Heaven Benchmark launcher opens more slower than Wine 3.0. I am using a HDD. ⬤ Warning if not fixed before Wine 8.0 stable gets released: It would be good if this problem is fixed before Wine 8.0 stable get released because Steam's Proton uses stable versions of Wine. If this problem is not fixed by the time Wine 8.0 stable gets released and proton updates to Wine 8.0. anyone using "PROTON_USE_WINED3D=1" on a DirectX11 Steam game can have severely Low FPS while Wine 7.0's DirectX11 to OpenGL is only a little bit more slower than Wine 6.0's DirectX11 to OpenGL right now. -- 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 51

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 January 2024