wine-bugs March 2022

wine-bugs@winehq.org

1 participants
4039 discussions

[Bug 33621] New: [UWIN] ksh93 from UWIN generates a lot of fixme warnings
by wine-bugs＠winehq.org 11 May '22

11 May '22

http://bugs.winehq.org/show_bug.cgi?id=33621 Bug #: 33621 Summary: [UWIN] ksh93 from UWIN generates a lot of fixme warnings Product: Wine Version: 1.5.30 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: simon.toedt(a)gmail.com Classification: Unclassified Running ksh93 (Korn Shell 93) from the UWIN (Unix emulation on Windows) toolkit generates a lot of "fixme" warnings and the shell is generally not useable. The goal is to use WINE for automated testing without having to fire up a full blown Windows system each time in VMware or real iron. Steps to test: 1. Install UWIN: > wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…' > wine uwin-base.2013-02-08.win32.i386.exe 2. Run Windows/UWIN version of ksh93: wine64 'C:\Program Files/UWIN/usr/bin/ksh.exe' fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000000, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:advapi:LsaOpenPolicy ((null),0x23f980,0x00000001,0x23f950) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netbios:NetServerEnum Stub ((null) 100 0x23f440 -1 0x23fbb8 0x23fbc8 24 (null) (nil)) fixme:netapi32:NetGetDCName ((null), (null), 0x23f448) stub! fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0xf70850,symt:0xfce150) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x20e2370,symt:0x2140480) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e98,symt:0x2970264) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2943cb0,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e90,symt:(nil)) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x36b3448,symt:0x378fa1c) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743718,symt:0x37781b4) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743658,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x37425a0,symt:0x3754e38) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work as described in bug 33619. IMO the most pressing problems are: 1. fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. 2. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented 3. fixme:netapi32:NetUserGetInfo Level 3 is not implemented 4. fixme:ntdll:NtSetInformationToken unimplemented class 4 5. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented -- 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 10

[Bug 52684] New: Command and Conquer Generals (and C&C Zero Hour) have no ground textures
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=52684 Bug ID: 52684 Summary: Command and Conquer Generals (and C&C Zero Hour) have no ground textures Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: bender647(a)yahoo.com Regression SHA1: 1632b8e7a419ebf256c4a356a58d505ef918f2fe Distribution: Slackware Introduced in wine-7.3 with commit 1632b8e7a419ebf256c4a356a58d505ef918f2fe, the C&C Generals game engine does not draw ground textures. The ground (or water) area is black. Reverting to wine-7.2, or applying this commit as a reverse-patch on wine-7.4 will fix the issue. The commit was found by bisecting the git tree. This symptom appears in older bug reports but the fixes there do not appear to work now. Tested on two platforms, but both were Intel i915 graphics. If necessary, I can get access to an Nvidia platform. To reproduce: 1. A free demo is available for download to run the game: https://www.moddb.com/downloads/start/111369 (https://www.moddb.com/games/cc-generals/downloads/command-conquer-generals-…). 2. Install in 32-bit prefix. 3. Run with `wine start generals.exe -nologo` and the game engine will be seen running behind the main menu. The ground will be blank if the bug is present. Verified to affect: https://appdb.winehq.org/objectManager.php?sClass=version&iId=4881 https://appdb.winehq.org/objectManager.php?sClass=version&iId=35407 Likely also: https://appdb.winehq.org/objectManager.php?sClass=version&iId=1717 -- 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 24

[Bug 45098] New: FrostPunk: multiple graphical glitches
by wine-bugs＠winehq.org 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=45098 Bug ID: 45098 Summary: FrostPunk: multiple graphical glitches Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)embed.me.uk Distribution: --- Created attachment 61268 --> https://bugs.winehq.org/attachment.cgi?id=61268 FrostPunk log With patch posted in https://bugs.winehq.org/show_bug.cgi?id=45080 the game sucessfully starts however there are severe graphical glitches which render it unplayable. Log attached. -- 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 15

[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 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 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 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

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 March 2022