wine-bugs

wine-bugs@winehq.org

1 participants
158797 discussions

[Bug 50458] New: Tooltips block input in Foobar2000
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=50458 Bug ID: 50458 Summary: Tooltips block input in Foobar2000 Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: debilerpc(a)web.de Distribution: --- **Context:** Like with most media players, Foobar2000's playlist view is essentially a spreadsheet where each line is a track and each column displays a tag or metadata field. If the length of the tag exceeds the width of the column, it gets cut off. You can see the full tag in a tooltip by hovering over it with a mouse in that case. **The problem:** As long as the tooltip is displayed, the app registers neither keyboard nor mouse input. I suspect this problem exists in a variety of [apps](https://bugs.winehq.org/show_bug.cgi?id=16227), not just Foobar2000, but here it is especially annoying. **Expected behavior:** When input is sent, the tooltip should disappear, and Foobar2000 should react to the input. This is what happens under Windows 10. -- 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 52771] New: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52771 Bug ID: 52771 Summary: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The way Wine creates the window for console applications breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win. https://test.winehq.org/data/patterns.html#comctl32:button https://test.winehq.org/data/patterns.html#dinput:keyboard https://test.winehq.org/data/patterns.html#user32:dialog https://test.winehq.org/data/patterns.html#user32:input https://test.winehq.org/data/patterns.html#user32:monitor https://test.winehq.org/data/patterns.html#user32:win These all started failing in Wine on 2022-03-17 with the commit below (also referenced in bug 52761): commit f034084d49b354811096524d472ae5172ac1cebf Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Thu Mar 17 08:27:28 2022 +0100 kernelbase: Handle corner case in CreateProcess. In CreateProcess, if: - parent isn't attached to a console - CreateProcess's flag isn't set with DETACHED_PROCESS nor CREATE_NEW_CONSOLE - child is a CUI program then a console must be allocated for the child. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52048 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The way the TestBot starts the tests in Wine is this [1]: testagentd (Unix, no terminal) \- shell script (sh Unix, no terminal) \- WineTest.pl (perl Unix, no terminal) \- ./wine TestLauncher (Windows CUI, no console) \- unit test (Windows CUI) -> creates a console \- unit test can recurse upon itself (CUI) I will now try to summarize the current understanding of the issue from the wine-devel discussion [2], using the above figure as a reference: 1. testagentd is a daemon so it does not have an associated terminal. 2. When ./wine does not have a terminal it does not create a console window, even when starting a console application. This is so wine can be used for background (batch) tasks without requiring a X session or popping up windows all over the place. 3. But when a Windows application calls CreateProcess() without DETACHED_PROCESS, a console does get created. This is what happens when TestLauncher starts a unit test. 4. While the console object is created synchronously in the wineserver process, the actual window is created asynchronously (by wineconsole). This causes it to pop up while the unit test as already started, which confuses the tests that check the window hierarchy, the focus, etc. There are two ways the above differ from Windows: 1. I believe Windows creates both the console object and the matching window synchronously. So even if the console was created when starting the test unit there should be no failure. 2. On Windows the shell script is replaced by a batch script which triggers the console creation. So the console creation happens a bit earlier which could also mask any window creation delay. The reason why f034084d49b3 made a difference is that before Wine was not creating console windows. [1] More details on the different ways the TestBot starts the tests: https://www.winehq.org/pipermail/wine-devel/2022-April/212550.html [2] March: https://www.winehq.org/pipermail/wine-devel/2022-March/212330.html April: https://www.winehq.org/pipermail/wine-devel/2022-April/212513.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 14

[Bug 45388] New: user32: edit fails on Traditional Chinese and Korean locales
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=45388 Bug ID: 45388 Summary: user32:edit fails on Traditional Chinese and Korean locales Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:edit fails with the following errors on Traditional Chinese and Korean locales: edit.c:1489: Test failed: 0: got 1, 1 edit.c:1510: Test failed: 0: got 1, 1 edit.c:1524: Test failed: 0: got 1, 1 edit.c:1538: Test failed: 0: got 1, 1 See: * Source matching the above https://source.winehq.org/git/wine.git/?a=blob;f=dlls/user32/tests/edit.c;h… * user32:edit WineTest failures https://test.winehq.org/data/tests/user32:edit.html The errors can be reproduced on the newtb-wvistau64-zh-cn TestBot VM, and also happen on fg-win7u64-1spie9-ko. -- 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 3

[Bug 52869] New: kernel32:locale - test_CompareStringA() fails in Wine in Hindi
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52869 Bug ID: 52869 Summary: kernel32:locale - test_CompareStringA() fails in Wine in Hindi Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- test_CompareStringA() started failing in Wine in Hindi recently: locale.c:1884: Test failed: expected CSTR_LESS_THAN, got 2 locale.c:1886: Test failed: expected CSTR_GREATER_THAN, got 2 https://test.winehq.org/data/patterns.html#kernel32:locale A bisect shows this failure started with the commit below: commit 8993e15cfa5b77ac2487239354ffe63bbc5e562d Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Apr 11 17:21:47 2022 +0200 kernelbase: Support UTF-7/8 codepages in get_codepage_table(). 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 4

[Bug 52743] New: regression cannot write to _fdopen'ed stdout
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52743 Bug ID: 52743 Summary: regression cannot write to _fdopen'ed stdout Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xantares09(a)hotmail.com Distribution: --- since wine 7.2, opening stdout with _fdopen and printing into it crashes ``` #include <stdio.h> #include <io.h> #include <fcntl.h> int main() { FILE * m_stdout = _fdopen(_fileno(stdout), "wb"); fprintf(m_stdout, "foo\n"); fclose(m_stdout); return 0; } $ x86_64-w64-mingw32-gcc main.c $ wine a.exe ... wine: Unhandled page fault on read access to 0000000000000050 at address 0000000170059685 (thread 0128), starting debugger... ... ``` For context, this is what qt-xmlpatterns does: https://github.com/qt/qtxmlpatterns/blob/dev/tools/xmlpatterns/main.cpp#L184 -- 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 17

[Bug 52362] New: Powershell Core 7 installer hangs forever on Chinese locale (LC_ALL=zh_Han.UTF-8)
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52362 Bug ID: 52362 Summary: Powershell Core 7 installer hangs forever on Chinese locale (LC_ALL=zh_Han.UTF-8) Product: Wine Version: 7.0-rc3 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.1.5/PowerShell-7.1.5-win-x64.msi OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Hi, someone i was trying to help someone to get this installed and he reported this to me (I couldn`t reproduce it), that the installer hung for him, and in fact he found that it was due to the fact he was running with LC_ALL=zh_Han.UTF-8 I don`t know anything about these chinese locales, but report anyway as could be a bug in wine (?). reproduce: LC_ALL=zh_Han.UTF-8 5ine msiexec /i PowerShell-7.1.5-win-x64.msi A +relay shows it`s looking for files in directory zh-CN which is not there, though there is zn-Han(s) directories. But just copying zh-Han to zh-CN didn`t help either. Anyway, I guess someone with more knowledge about (Chinese) locales would have lots more clues than i have... -- 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 9

[Bug 52149] New: user32:dialog fails in test_DialogBoxParam() on current Windows 10 21H1
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52149 Bug ID: 52149 Summary: user32:dialog fails in test_DialogBoxParam() on current Windows 10 21H1 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:dialog fails in test_DialogBoxParam() on current Windows 10 21H1: dialog.c:1854: Test failed: got 1407 https://test.winehq.org/data/patterns.html#user32:dialog So instead of failing with an error code of 0, the call below fails with ERROR_CANNOT_FIND_WND_CLASS... which makes sense? ret = DialogBoxParamA(GetModuleHandleA(NULL), "TEST_DIALOG_INVALID_CLASS", 0, DestroyDlgWinProc, 0); It's interesting to note that this failure did not happen on the initial Windows 10 21H1 test configurations (2021-08-23). As far as I can tell it's only after KB5006670 was applied (on 2021-10-21) that the test started failing. Unfortunately this is a cumulative update so it may not help narrow down the cause very much. -- 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 52922] New: The Evil Within crashes before entering the main menu using Vulkan renderer
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52922 Bug ID: 52922 Summary: The Evil Within crashes before entering the main menu using Vulkan renderer Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: e7d86d9c6e58e8e133c606099615b0d9e7940132 Distribution: --- wine: Unhandled page fault on read access to 00007F3B54255B28 at address 00007F32CDDE5A09 (thread 0740), starting debugger... -- 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 52887] New: Get-Computerinfo from NoPowershell crashes
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52887 Bug ID: 52887 Summary: Get-Computerinfo from NoPowershell crashes Product: Wine Version: 7.7 Hardware: x86-64 URL: https://github.com/bitsadmin/nopowershell/releases/tag /1.23 OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 72275 --> https://bugs.winehq.org/attachment.cgi?id=72275 patch NoPowershell.exe provides a number of commandlets without the need to install it(https://github.com/bitsadmin/nopowershell/releases/tag/1.23). Prerequisite: winetricks -q dotnet48 The commandlet Get-Computerinfo acts as replacement of systeminfo.exe Source: https://github.com/bitsadmin/nopowershell/blob/master/Source/NoPowerShell/C… Currently fails with: Get-ComputerInfo : System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource) at NoPowerShell.Commands.Management.GetComputerInfo.Execute(CommandResult pipeIn) at NoPowerShell.Program.Main(String[] args) Attached patch fixes it, to run into next bug . Next bugs are some missing props from various classes. After adding them (albeit quickly with some hacks) the cmdlet runs. I attach first three patches, rest follows later. -- 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 52847] New: GetACP() returns CP_UTF8 on some debian VM
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52847 Bug ID: 52847 Summary: GetACP() returns CP_UTF8 on some debian VM Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: eric.pouech(a)orange.fr Distribution: --- wine's tests in kernel32/tests/process.c fail on some Debian VM (Dhivehi:Maldives and Hindi:India) debugging it shows: - conhost (in window.c) aborts at startup because TranslateCharsetInfo( GetACP() ...) fails in Wine - both locale return CP_UTF8 from GetACP() - testing on windows vm (Hindi), show that GetACP() returns 1252 CP - moreover, testing on Win11 TranslateCharsetInfo( CP_UTF8 ) succeeds returning the Win11 values for CP_UTF8 in TranslateCharsetInfo let the kernel32:process run "correctly" (ie no longer showing the specific errors related to TranslateCharsetInfo) -- 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 48045] New: comdlg32:filedlg crashes or times out randomly
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=48045 Bug ID: 48045 Summary: comdlg32:filedlg crashes or times out randomly Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 65586 --> https://bugs.winehq.org/attachment.cgi?id=65586 comdlg32:filedlg: Traces to debug random crash / timeouts. comdlg32:filedlg crashes randomly on all Windows versions from Vista to Windows 8 while Windows 10 (at least 1507, 1709 and 1809) gets random timeouts. https://test.winehq.org/data/tests/comdlg32:filedlg.html When successful comdlg32:filedlg does not print much so the standard reports are pretty much useless to spot the place where the test gets stuck on Windows 10, assuming it gets stuck in a specific place rather than just being slow. As for the crashes, they don't trigger the tests exc_filter() so there is no indication of the last successful ok() call. Turning on 'Report successful tests' may be preventing the crash (or these runs just got lucky). It's possible to reproduce the crash while adding the traces in the attached patch. This is not entirely fruitful as the crashes don't seem to always happen in the same place. test_extension() is the place where most issues happen though: https://testbot.winehq.org/JobDetails.pl?Key=59060 -> wvistau64: Crash in test_extension(). Based on the test_extension_helper() traces, it happened in the loop with i=1 so for "TestFilter (*.abc;)\0*.abc;\0". https://testbot.winehq.org/JobDetails.pl?Key=59086 -> w2008s64+exe: Crash on or after test_extension() return https://testbot.winehq.org/JobDetails.pl?Key=59088 -> wvistau64+exe: Crash in test_DialogCancel() https://testbot.winehq.org/JobDetails.pl?Key=59091 -> wvistau64_fr: Spent 39s in test_null_filename() but no timeout https://testbot.winehq.org/JobDetails.pl?Key=59139 -> wvistau64: Crash in test_null_filename() -> wvistau64_fr: Timeout in test_extension() filedlg.c:1048: filter=[TestFilter (*.ab?) lpstrDefExt=NULL] https://testbot.winehq.org/JobDetails.pl?Key=59151 -> wvistau64: Crash in test_extension() filedlg.c:1048: filter=[TestFilter (*.abc.def)] -> wvistau64_fr: Timeout in or after test_mru() filedlg.c:637: 19 test_ok filedlg.c:904: 29 test_getfolderpath filedlg.c:986: 30 test_mru -> w1064v1809_zh_CN: Two failures in test_extension() filedlg.c:1053: Test failed: TestFilter (*.pt*;*.abc): expected TRUE filedlg.c:1059: Test failed: TestFilter (*.pt*;*.abc): Filename is deadbeef, expected deadbeef.xyz Memory corruption, maybe happening quite early in the test? -- 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 52924] New: Guilty Gear XX #Reload: black screen since wine 5.0
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52924 Bug ID: 52924 Summary: Guilty Gear XX #Reload: black screen since wine 5.0 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: s.guidoni(a)tin.it Distribution: --- Since wine 5.0 the game "Guilty Gear XX ♯Reload" shows a black screen while running. The game starts, the introductory videos are displayed correctly, then the game runs, but the screen is just black, with some blocky piece of graphics flashing now and then across the screen. The sound plays, so one can browse the menu, start a game and so on, but the screen stays black with some bright rectangular shape flashing around. The game is based on DirectX 8.1 and the last wine version that works is 4.21. With wine 4.21, the console output is: 002d:fixme:win:EnumDisplayDevicesW ((null),0,0x33f798,0x00000000), stub! 002f:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 002d:err:quartz:GetClassMediaFile Media class not found 002d:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. With wine 5.0.5, it is: 0033:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0033:fixme:d3d:wined3d_swapchain_init Unimplemented swap effect 0x5. 0035:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 0033:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. With wine 7.6, it is: 012c:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x3. 012c:err:winediag:wined3d_dll_init Using the OpenGL renderer. 012c:fixme:imm:ImeSetActiveContext (0x266c88, 1): stub 012c:fixme:imm:ImmReleaseContext (0002010C, 00266C88): stub 012c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 012c:err:d3d_sync:wined3d_cs_create Forcing serialization of all command streams. 012c:err:d3d_sync:wined3d_cs_create Forcing serialization of all command streams. 012c:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't 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.

1 7

[Bug 52871] New: oleaut32:vartest has failures in Wine in the Arabic and Hebrew locales
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52871 Bug ID: 52871 Summary: oleaut32:vartest has failures in Wine in the Arabic and Hebrew locales Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- oleaut32:vartest has failures in Wine in the Arabic and Hebrew locales: vartest.c:3130: Test failed: VarAbs: expected 0x0,5,1.1, got 0x80020005,8,-1.#IND vartest.c:4073: Test failed: wrong result 80020005 vartest.c:4188: Test failed: wrong result 80020005 vartest.c:4312: Test failed: wrong result 80020005 vartest.c:4444: Test failed: wrong result 80020005 vartest.c:7785: Test failed: VarCmp: 2|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 3|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 4|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 5|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 6|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 7|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 2|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 3|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 4|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 5|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 6|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 7|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 11|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 14|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 17|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 20|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 11|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 14|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 17|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 20|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 22|0x8000, 8|0x8000: Expected 0x2, got 0x0 https://test.winehq.org/data/patterns.html#oleaut32:vartest These failures happen in test_VarAbs(), test_VarFix(), test_VarInt(), test_VarNeg(), test_VarRound() and test_VarCmp() but a bisect shows that they all start with this commit: commit ba43e4cfca97a9bba3e6575af82acbf011685862 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Mar 29 22:11:32 2022 +0200 kernelbase: Reimplement number formatting values in GetLocaleInfoW/Ex using the locale.nls data. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> It should be noted that this commit did fix another set of oleaut32:vartest failures (which were likely introduced by 2cd33e6b0fd6). -- 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 52865] New: windows.media.speech:speech has a Windows 10 1507-specific failure
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52865 Bug ID: 52865 Summary: windows.media.speech:speech has a Windows 10 1507-specific failure Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com IAsyncOperation_SpeechRecognitionCompilationResult_get_Completed() unexpectedly returns a handle on Windows 10 1507: speech.c:979: Test failed: Handler had value 0029FC20. https://test.winehq.org/data/patterns.html#windows.media.speech:speech Unsurprisingly a bisect shows that the failures started with the commit that introduced this new test: commit 4926bb148b049f1b60e57091f4aa87a3957aa69e Author: Bernhard Kölbl <besentv(a)gmail.com> Date: Wed Apr 6 18:28:41 2022 +0200 windows.media.speech: Add tests for IAsyncOperation. Signed-off-by: Bernhard Kölbl <besentv(a)gmail.com> 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 52845] New: Recent versions of chromium have broken sandbox again
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52845 Bug ID: 52845 Summary: Recent versions of chromium have broken sandbox again Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Somewhere between chromium-946247 (commit 4e7609b62147866fb7b226fd6efbe1ae4d2f1aca and chromium-946263 (commit 1bd694702105072e57b980512130a3212675ec19) the sandbox got changes so it doesn't work under wine anymore. Result is a black screen and soon a crash. This affects both 32bit and 64bit chromium. Note: chromium should be located inside the WINEPREFIX, it won't run outside! Nightly versions to test with (chrome-win.zip) https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.h… https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.h… I tried to build from source on my Win11 machine, but those versions don't run under wine at all, even if compiling the same commit as the nightly versions. -- 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 9

[Bug 52554] New: Serbian locale mapping cause crash on multiple installshield wizards
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52554 Bug ID: 52554 Summary: Serbian locale mapping cause crash on multiple installshield wizards Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: lei.pero(a)gmail.com Distribution: --- Since commits: kernelbase: Map LANG_SERBIAN_NEUTRAL in ConvertDefaultLocale(). f51e44c1802338cdd41b38efe2757b642b619d6f ntdll: Map LANG_SERBIAN_NEUTRAL in RtlLocaleNameToLcid(). db3e08770fe9bfb6f06a71761e48a40fe9764058 starting with wine-6.2 - when using locale sr_RS.UTF-8, some (specifically older) installers do crash, for example 3DMark03, preventing installation, passing LANG=en_US.UTF-8 EV works as expected with no crash. Reverting those two specific commits solves the issue. Or changing line in: dlls/ntdll/locale.c from: case MAKELANGID( LANG_SERBIAN, SUBLANG_NEUTRAL ): *lcid = LANG_SERBIAN_NEUTRAL; to: case MAKELANGID( LANG_SERBIAN, SUBLANG_NEUTRAL ): *lcid = MAKELCID( 0x02, SORT_DEFAULT ); solves the issue as well, but that basically renders all those commits useless I assume? On the topic, but unrelated to this bug, I can see changes in dlls/kernel32/nls/srl.nls, with commit: kernel32: Update sr-Latn locale definition. 3b3dfda59951b0f42e297f2b9a31ded04a98d4b4 that doesn't seem right to me, srl.nls should stand for Serbian Latin I assume, srm.nls probably stands for m as Montenegro. So, if I'm correct, addition of srm.nls with commit: kernel32: Add sr-Latn-RS locale definition. db2666e9d20f80968ff6b4b0ea1deae20c3c368b should have changes made to srl.lns. I don't know how this is solved for English for example, since neutral should have a specific code not related to any country where language is used (e.g. US, UK, CA etc.), and the code it seems to be sr_CS as it is changed for sr_RS latin locale, where it shouldn't be changed I assume. -- 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 8

[Bug 51181] New: d3d10core:d3d10core fails systematically on AMD GPUs
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=51181 Bug ID: 51181 Summary: d3d10core:d3d10core fails systematically on AMD GPUs Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_instanced_draw() fails systematically in d3d10core:d3d10core on AMD GPUs (and sometimes there is a crash that follows): d3d10core.c:9275: Test failed: Got 0xfff0f010, expected 0xff80f010 at (160, 0), sub-resource 0. d3d10core.c:9275: Test failed: Got 0xfff0f040, expected 0xff80f040 at (240, 0), sub-resource 0. d3d10core.c:9275: Test failed: Got 0xffaaaacc, expected 0xffbbaacc at (480, 0), sub-resource 0. d3d10core.c:9275: Test failed: Got 0xffaaaa90, expected 0xffbbaa90 at (560, 0), sub-resource 0. Notice how this failure does not happen on the machines that have other GPUs such as cw-gtx560 or QEmu VMs, and how this does not depend on the Windows version or Radeon driver version for that matter: https://test.winehq.org/data/patterns.html#d3d10core:d3d10core So it looks like the test expects fails to account for the Radeon driver results for some reason. The commit that introduced this test is: commit fcd549345d96109179b125d31baf9e9073ecf643 Author: Józef Kucia <jkucia(a)codeweavers.com> AuthorDate: Mon Nov 6 10:55:20 2017 +0100 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Mon Nov 6 19:37:09 2017 +0100 d3d10core/tests: Add test for SV_InstanceID. Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(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 8

[Bug 43995] New: Uplay - Assassin's Creed 4 Black Flag won't start
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=43995 Bug ID: 43995 Summary: Uplay - Assassin's Creed 4 Black Flag won't start Product: Wine-staging Version: 2.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mi.bar.2001(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59652 --> https://bugs.winehq.org/attachment.cgi?id=59652 Terminal log from `wine AC4BFSP.exe` After clicking the "Play" button in Ubisoft Game Launcher (or launching `wine AC4BFSP.exe`), a window pops up informing, that the game is starting, but it disappears and the game doesn't launch. I don't have the Steam version, just the Uplay one. I've set Windows version to XP, wineprefix is 32-bit. Wine version will probably be visible when I post this, but I'm going to mention it just to be safe. Using Wine 2.20 staging -- 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

[Bug 52856] New: kernel32:process fails when Wine has no Unix terminal
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52856 Bug ID: 52856 Summary: kernel32:process fails when Wine has no Unix terminal Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:console fails on the TestBot Wine machines: process.c:1552: Test failed: Opening ConIn process.c:1553: Test failed: Opening ConOut process.c:1556: Test failed: Getting sb info process.c:1557: Test failed: Getting console in mode process.c:1558: Test failed: Getting console out mode process.c:212: 5 failures in child process process.c:1569: Test failed: Getting sb info process.c:1570: Test failed: Getting console in mode process.c:1571: Test failed: Getting console out mode process.c:1582: Test failed: GetLastError: expecting 87 got 12 process.c:1592: Test failed: GetLastError: expecting 87 got 12 process.c:1621: Test failed: Console:SizeX expected 30870, but got 0 process.c:1622: Test failed: Console:SizeY expected 31489, but got 0 process.c:1623: Test failed: Console:CursorX expected 32644, but got 0 process.c:1624: Test failed: Console:CursorY expected 94, but got 0 process.c:1625: Test failed: Console:Attributes expected 0, but got 1 process.c:1626: Test failed: Console:winLeft expected 0, but got 1 process.c:1627: Test failed: Console:winTop expected 4294964424, but got 0 process.c:1628: Test failed: Console:winRight expected 49, but got 0 process.c:1629: Test failed: Console:winBottom expected 30870, but got 0 process.c:1630: Test failed: Console:maxWinWidth expected 31489, but got 0 process.c:1631: Test failed: Console:maxWinHeight expected 11256, but got 0 process.c:1634: Test failed: Console:InputMode expected 0, but got 1 process.c:1635: Test failed: Console:OutputMode expected 7211040, but got 0 process.c:1639: Test failed: Wrong console CP (expected 1252 got 0/0) process.c:1640: Test failed: Wrong console-SB CP (expected 1252 got 0/0) process.c:1645: Test failed: Wrong console mode process.c:1646: Test failed: Wrong console-SB mode https://test.winehq.org/data/patterns.html#kernel32:process The reason is that the TestBot starts Wine from a daemon process which does not have an associated xterm / Konsole / GNOME terminal. This causes Wine to have to allocate a Wine console and that's when things go wrong. A bisect shows that the TestBot is only impacted by this bug since the commit below: commit eff83cd4e00e8ccd4daad05bdd6d76e77664ddd1 Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Mon Apr 11 15:05:09 2022 +0200 kernelbase: Provide a pseudo console environment for initial CUI processes not tied to a Unix tty. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52771 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52761 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52743 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> But as the commit entry shows this commit also fixed a lot of other issues in the TestBot results (not least of which is getting the wow64 WineTest results in an acceptable shape for test.winehq.org). Also this issue has happened before as evidenced by bugs 25284 and 28220. However those bugs are very old (~2014) so the issue may have been fixed and reappeared (the TestBot has not used a Unix terminal to run the Wine tests since at least 2018-06 (date on local-testagentd.service) and probably 2017 or more (f1d368722b65 tools commit)). Bug 28220 does have a more recent and interesting comment by Esme with regards to handle inheritance: https://bugs.winehq.org/show_bug.cgi?id=28220#c3 -- 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 52559] New: kernel32:resource times out since 2021-12-29 at two win10 testbot systems.
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52559 Bug ID: 52559 Summary: kernel32:resource times out since 2021-12-29 at two win10 testbot systems. Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- I wondered because the windows test patterns showed timeouts for the kernel32:resource [1] since some days. I tried a run with verbose timestamps and got [2]. There it shows gaps of ~6 seconds, and it looks like the delay originates from an execution of EndUpdateResourceA [3]. Unfortunately there are a lot calls for this function and therefore the test times out. Searching the net led me to the autohotkey forums where this function was associated with windows defender. Is windows defender active at these VMs? [1] https://test.winehq.org/data/tests/kernel32:resource.html [2] https://testbot.winehq.org/JobDetails.pl?Key=108231&f201=exe32.report#k201 [3] https://source.winehq.org/git/wine.git/blob/781277de62822c2bac23dc892a99665… -- 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 52079] New: oleacc:main crashes randomly on Windows 10 1709+
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52079 Bug ID: 52079 Summary: oleacc:main crashes randomly on Windows 10 1709+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: oleacc Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com oleacc:main crashes randomly on Windows 10 1709+ in both 32- and 64-bit: main.c:1041: Test failed: V_VT(&v) = 0 main.c:1048: Test failed: V_VT(&v) = 0 main.c:1049: Test failed: V_DISPATCH(&v) = 0000000000000000 main.c:1049: this is the last test seen before the exception 1050:main: unhandled exception c0000005 at 0000000000401597 oleacc:main:1050 done (-1073741819) in 0s Test failed: crash (c0000005) https://test.winehq.org/data/patterns.html#oleacc:main Unsurprisingly a bisect shows that the tests started failing with the commit that introduced the test: commit 1a3db363c6b4065af532a8db1e6309be753b1781 Author: Connor McAdams <cmcadams(a)codeweavers.com> Date: Mon Sep 20 18:03:31 2021 +0200 oleacc: Add Client_get_accFocus tests. Signed-off-by: Connor McAdams <cmcadams(a)codeweavers.com> Signed-off-by: Piotr Caban <piotr(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> At the time the crash happened after line 1037 which points to line 1039 as a likely culprit: 1032 /* Set focus to each child window. */ 1033 SetFocus(btn); 1034 hr = IAccessible_get_accFocus(acc, &v); 1035 ok(hr == S_OK, "hr %#x\n", hr); 1036 ok(V_VT(&v) == VT_DISPATCH, "V_VT(&v) = %d\n", V_VT(&v)); 1037 ok(V_DISPATCH(&v) != NULL, "V_DISPATCH(&v) = %p\n", V_DISPATCH(&v)); 1038 1039 hr = IDispatch_QueryInterface(V_DISPATCH(&v), &IID_IOleWindow, (void**)&ow); 1040 ok(hr == S_OK, "got %x\n", hr); That call has been moved to _check_acc_hwnd() and so the crash now happens in the first QueryInterface() call in that function: hr = IUnknown_QueryInterface(unk, &IID_IOleWindow, (void**)&ow); called from check_acc_hwnd((IUnknown*)V_DISPATCH(&v), btn); -- 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 52904] New: kernel32:locale breaks oleaut32:varformat on Wine in the French locale
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52904 Bug ID: 52904 Summary: kernel32:locale breaks oleaut32:varformat on Wine in the French locale Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:locale breaks oleaut32:varformat on Wine in the French locale: varformat.c:642: Test failed: Unexpected hr 0x80020005 for L"0,000 EUR" varformat.c:649: Test failed: Unexpected hr 0x80020005 for L"0,000 EUR" https://test.winehq.org/data/patterns.html#oleaut32:varformat When starting from a clean wineprefix one would normally get "0,000 €" for this test. But if one runs kernel32:locale before the Euro symbol is replaced with "EUR" which is then not recognized as a currency symbol. A bisect shows that the failures started with this commit: commit 78a33f968461fa3a01d3eec837b4c24f353bc00b Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Tue Mar 29 22:12:25 2022 +0200 kernelbase: Reimplement SetLocaleInfoW(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The commit modifies both kernel32 and kernel32:locale, and both parts of the patch are needed to reproduce the failure. -- 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 52867] New: System.Globalization.CultureInfo.GetCultureInfo fails for 'en' value
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52867 Bug ID: 52867 Summary: System.Globalization.CultureInfo.GetCultureInfo fails for 'en' value Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 72261 --> https://bugs.winehq.org/attachment.cgi?id=72261 stacktrace (filing under ntdll, as that where relevant files were before the commit series that most likely broke it) After upgrading to 7.6, still occurring in 7.7, a regression was made - the last published dnSpy version had been running relatively well in its basic functionality (I'm actually not any good with it), other than minor display glitches; now it stacktraces immediately. I believe the stacktrace makes it clear what happens and why I suspect that locale commit series are at fault here. That release of dnSpy embeds its mono environment, so it's not a wine-mono problem. -- 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 9

[Bug 52858] New: kernel32:file fails in Windows 8.1 on the cw-rx460 machine
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52858 Bug ID: 52858 Summary: kernel32:file fails in Windows 8.1 on the cw-rx460 machine 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:file and msvcp140:msvcp140 fail on the cw-rx460 machine: file.c:905: Test failed: Unexpected error 87. file.c:910: Test failed: Unexpected error 87. https://test.winehq.org/data/patterns.html#kernel32:file These are new tests so unsurprisingly the failures are caused by the commit that introduced them: commit 02faaea93b78d5d53976b2955bef7beffa780d02 Author: Paul Gofman <pgofman(a)codeweavers.com> Date: Mon Apr 11 21:44:36 2022 +0300 kernelbase: Reset last error on success in CopyFileExW(). Signed-off-by: Paul Gofman <pgofman(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> It's unclear why the test only fails on this configuration. Also note that msvcp140:msvcp140 fails in a very similar way in the exact same test configuration: see bug 52857. -- 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 51407] New: kernel32:time's test_GetCalendarInfo() fails in Hindi
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=51407 Bug ID: 51407 Summary: kernel32:time's test_GetCalendarInfo() fails in Hindi Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 70263 --> https://bugs.winehq.org/attachment.cgi?id=70263 Broken fix and traces Three GetCalendarInfo() checks fail in Hindi: https://test.winehq.org/data/patterns.html#kernel32:time time.c:728: Test failed: GetCalendarInfoA failed err 87 time.c:731: Test failed: GetCalendarInfoA failed err 87 time.c:738: Test failed: got 0, expected 7 The immediate cause for the failure is that Hindi is one of the few languages for which NLS_IsUnicodeOnlyLcid() returns true. In turn this causes the ANSI GetCalendarInfoA() to return ERROR_INVALID_PARAMETER. The last failure just reflects the fact that the two calls to GetCalendarInfoA() should not have failed. Only Hindi fails and only in Wine. But before declaring this a Wine bug we need to look at Windows. * For some reason probably related to SetWinLocale [1] the system locale of w10pro64_hi is still English. * This causes both the ANSI and Unicode GetCalendarInfo() to return English names (Monday). * Manually setting the system locale to Hindi is possible on Windows 10 2004. What's interesting is the disabled and checked-by-default checkbox in that dialog: [X] Beta: Use Unicode UTF-8 for worldwide language support * And indeed doing that and running the test again results in GetCalendarInfoA() returning UTF-8 strings on Windows! time.c:730: ret=19 sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0" सोमवार time.c:735: ret2=19 sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0" सोमवार time.c:742: ret2=19 sdayname1=L"\0938\094b\092e\0935\093e\0930" * The beta moniker strongly suggests that this is a new option. Indeed selecting Hindi as the system locale was not possible in Windows 8.1 for instance. * This is probably also why SetWinLocale has trouble setting the system locale to Hindi. So the Windows behavior can be summarized as such: * Return localized values for non-Unicode-only locales. * In older Windows versions setting the system locale to a Unicode-only locale is impossible. * In newer Windows versions setting the system locale to a Unicode-only locale is possible and then it uses UTF-8. Commenting out the Hindi line in NLS_IsUnicodeOnlyLcid() fixes the failures in Wine (see attached patch). But this fix is wrong because it causes GetCalendarInfoA() to return question marks instead of intelligible strings. (it also impacts many APIs but that's probably ok based on the Windows behavior) So Wine should do one of the following: 1. Stick to a 'safe' system locale when $LANG is set to a Unicode-only locale. Typically this would be English. 2. Or use UTF-8 when the system locale is a Unicode-only locale. Option 2 would actually make a lot of sense on Unix systems but it is also more likely to break Windows applications. So option 1 may be the safer (and simpler?) option (for now). [1] https://source.winehq.org/git/tools.git/blob/HEAD:/testbot/bin/SetWinLocale… -- 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

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