January 2023 - Wine-bugs - list.winehq.org

[Bug 38642] New: Geometry Wars crashes when changing screen resolution
by wine-bugs＠winehq.org 25 Feb '23

25 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=38642 Bug ID: 38642 Summary: Geometry Wars crashes when changing screen resolution Product: Wine Version: 1.7.43 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: ben(a)xnode.org Distribution: --- The game opens and works fine, but if you try and change the fullscreen resolution, the game crashes out with a Wine page-fault pop-up message: Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x00429ec7). Unfortunately I cannot get more info on this right now as I've switched to Wine-Staging to test some other things. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 8

[Bug 53135] New: kernel32:locale fails in Wine in Japanese
by WineHQ Bugzilla 25 Feb '23

25 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53135 Bug ID: 53135 Summary: kernel32:locale fails in Wine in Japanese 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 fails in Wine in Japanese: locale.c:3359: Test failed: qsort using lstrcmpA failed for element 6 locale.c:3359: Test failed: qsort using lstrcmpA failed for element 7 locale.c:3359: Test failed: qsort using lstrcmpA failed for element 8 locale.c:3359: Test failed: qsort using lstrcmpA failed for element 9 locale.c:3359: Test failed: qsort using lstrcmpA failed for element 10 locale.c:3367: Test failed: qsort using CompareStringA failed for element 6 locale.c:3367: Test failed: qsort using CompareStringA failed for element 7 locale.c:3367: Test failed: qsort using CompareStringA failed for element 8 locale.c:3367: Test failed: qsort using CompareStringA failed for element 9 locale.c:3367: Test failed: qsort using CompareStringA failed for element 10 locale.c:3375: Test failed: qsort using sort keys failed for element 6 locale.c:3375: Test failed: qsort using sort keys failed for element 7 locale.c:3375: Test failed: qsort using sort keys failed for element 8 locale.c:3375: Test failed: qsort using sort keys failed for element 9 locale.c:3375: Test failed: qsort using sort keys failed for element 10 https://test.winehq.org/data/patterns.html#kernel32:locale A bisect shows that these failures started with the commit below: commit d8c973ad95ba5e8a9a51df0dd9be587950179ec3 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon May 30 22:38:28 2022 +0200 kernelbase: Reimplement CompareStringEx using the sortkey generation code. 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 29028] New: Starcraft crashes on exit
by wine-bugs＠winehq.org 25 Feb '23

25 Feb '23

http://bugs.winehq.org/show_bug.cgi?id=29028 Bug #: 29028 Summary: Starcraft crashes on exit Product: Wine Version: 1.3.31 Platform: x86 OS/Version: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: amasterov(a)gmail.com Classification: Unclassified After upgrading wine to 1.3.31 Starcraft crashes on exit. wine 1.3.30 has not this problem. After choosing exit in game menu I get black screen in 640x480 resolution (I switch to nvidia-settings with Alt-Tab and set up correct resolution after this). In console there are this lines: fixme:advapi:SetSecurityInfo stub fixme:win:EnumDisplayDevicesW ((null),0,0x33f3d8,0x00000000), stub! err:seh:setup_exception_record stack overflow 844 bytes in thread 0024 eip 0041efcc esp 00240fe4 stack 0x240000-0x241000-0x340000 err:ntdll:RtlpWaitForCriticalSection section 0x62385d40 "time.c: TIME_tz_section" wait timed out in thread 0027, blocked by 0024, retrying (60 sec) err:seh:raise_exception Unhandled exception code c0000194 flags 0 addr 0x6231354f I've tried regression testing with git bisect and get this result: 496b438ede825fc00daac7a5869e045ae583cec9 is the first bad commit commit 496b438ede825fc00daac7a5869e045ae583cec9 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Tue Sep 27 09:31:59 2011 -0500 wined3d: Remove d3d8/9 palette support. :040000 040000 8b95a8e0e4e7524170ba43bc2ffe369359b9811d 7c427ec5a0816aa5da25718cee9c70e0d3605214 M dlls :040000 040000 a6ee1c817b1f21634ddad86780fad5cfe9c4fb29 fe57de377c4cf96d0f48c4560d0db321b7b28e91 M include There was slightly different errors on the screen during testing, but I did "git bisect bad" on every crash on exit. With what WINEDEBUG flags should I run wine to provide any additional information about this issue? -- 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 12

[Bug 19017] New: DirectX Hardware presenting Problem
by wine-bugs＠winehq.org 24 Feb '23

24 Feb '23

http://bugs.winehq.org/show_bug.cgi?id=19017 Summary: DirectX Hardware presenting Problem Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: fr.fr(a)vr-web.de Created an attachment (id=21920) --> (http://bugs.winehq.org/attachment.cgi?id=21920) Log output of the Game Balls (in Appdb is a link for a Download) Device is not Found It seams DirectX in Wine has a Problem with presenting Hardware devices -- 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 32

[Bug 48339] New: RadiAnt DICOM Viewer cannot export series to WMV movie
by WineHQ Bugzilla 24 Feb '23

24 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=48339 Bug ID: 48339 Summary: RadiAnt DICOM Viewer cannot export series to WMV movie Product: Wine Version: 5.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: bozkar(a)gmail.com Distribution: --- Movie export to wmv does not work under Wine 5.0~rc1-staging in RadiAnt DICOM Viewer 5.5.0 64 bit As far as I tested RadiAnt on wine it never did. Console output: 01cc:fixme:wmvcore:WMProfileManager_LoadProfileByData (0000000000C24D40)->(L"<profile version=\"589824\" storageformat=\"1\" name=\"radiant\" description=\"\"><streamconfig majortype=\"{73646976-0000-0010-8000-00AA00389B71}\" streamnumber=\"2\" streamname=\"Video Stream\"inputname=\"Video409\" bitrate=\"20000000\" bufferwindow=\"3000\" reliabletransport=\"0\" deco"... 0000000007913480) I suppose that wmv export is probably not implemented currently, at least in this profile. To reproduce: Open any example CT series in RadiAnt DICOM viewer, export series, pick "wmv", directory, and click save, nothing happens. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 53774] New: WinZip 7
by WineHQ Bugzilla 23 Feb '23

23 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53774 Bug ID: 53774 Summary: WinZip 7 Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: blueguitar1978(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- WinZip 7: crashes when extracting a zip archive -- 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 32235] New: Soldiers heroes of World War II crashes on startup
by wine-bugs＠winehq.org 22 Feb '23

22 Feb '23

http://bugs.winehq.org/show_bug.cgi?id=32235 Bug #: 32235 Summary: Soldiers heroes of World War II crashes on startup Product: Wine Version: 1.5.16 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: paulthetall(a)gmail.com Classification: Unclassified Created attachment 42522 --> http://bugs.winehq.org/attachment.cgi?id=42522 Crash log Soldiers Heroes of World War 2 crash on startup see crash log. It says a out of memory notification, so maybe a memory leak or something? I use the GOG.com version in this test. Hope you guys can ind out what is going on. If you need andy extra debug extensions let me know so I can provide it. Many thanks in advance! -- 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 40

[Bug 54169] New: ntoskrnl.exe:ntoskrnl - test_pnp_devices() sometimes fails on Windows and Linux
by WineHQ Bugzilla 21 Feb '23

21 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=54169 Bug ID: 54169 Summary: ntoskrnl.exe:ntoskrnl - test_pnp_devices() sometimes fails on Windows and Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntoskrnl.exe:ntoskrnl - test_pnp_devices() fails on Windows 10 with test signing turned on: ntoskrnl.c:1801: Test failed: failed to create device, error 0xe0000207 ntoskrnl.c:1805: Test failed: failed to create set hardware ID, error 0x57 ntoskrnl.c:1808: Test failed: failed to register device, error 0x57 ntoskrnl.c:1813: Test failed: got error 0x57 ntoskrnl.c:1817: Test failed: failed to install device, error 0xe000020b ntoskrnl.c:1822: Test failed: got error 0x57 ntoskrnl.c:1823: Test failed: got flags 0x10 ntoskrnl.c:1824: Test failed: got type 0 ntoskrnl.c:1546: Test failed: failed to get interface, error 0x103 ntoskrnl.c:1547: Test failed: wrong class {deadbeef-29ef-4538-a5fd-b69573a362c0} ntoskrnl.c:1549: Test failed: got flags 0x1 ntoskrnl.c:1563: Test failed: got 0 bus arrival messages ntoskrnl.c:1569: Test failed: failed to get interface, error 0x103 ntoskrnl.c:1570: Test failed: wrong class {deadbeef-29ef-4538-a5fd-b69573a362c0} ntoskrnl.c:1579: Test failed: got 0 bus arrival messages ntoskrnl.c:1580: Test failed: got 0 bus removal messages ntoskrnl.c:1585: Test failed: failed to get interface, error 0x103 ntoskrnl.c:1586: Test failed: wrong class {deadbeef-29ef-4538-a5fd-b69573a362c0} ntoskrnl.c:1588: Test failed: got flags 0x1 ntoskrnl.c:1605: Test failed: got 0 child arrival messages ntoskrnl.c:1612: Test failed: failed to get device, error 0x103 ntoskrnl.c:1613: Test failed: wrong class {4d36e97d-e325-11ce-bfc1-08002be10318} ntoskrnl.c:1616: Test failed: failed to get device ID, error 0x57 ntoskrnl.c:1617: Test failed: got ID "\x08" ntoskrnl.c:1621: Test failed: got error 0x57 ntoskrnl.c:1637: Test failed: got error 0x57 ntoskrnl.c:1639: Test failed: got flags 0x69f1b90b ntoskrnl.c:1640: Test failed: got type 0 ntoskrnl.c:1645: Test failed: got error 0x57 ntoskrnl.c:1650: Test failed: got error 0x57 ntoskrnl.c:1654: Test failed: got error 0x57 ntoskrnl.c:1655: Test failed: got type 0 ntoskrnl.c:1656: Test failed: got size 0 ntoskrnl.c:1662: Test failed: got error 0x57 ntoskrnl.c:1663: Test failed: got type 0 ntoskrnl.c:1664: Test failed: got size 0 ntoskrnl.c:1669: Test failed: got error 0x57 ntoskrnl.c:1670: Test failed: got type 0 ntoskrnl.c:1671: Test failed: got size 0 ntoskrnl.c:1676: Test failed: got error 0x57 ntoskrnl.c:1688: Test failed: failed to open child: 0xc0000034 ntoskrnl.c:1692: Test failed: got error 6 ntoskrnl.c:1693: Test failed: got id -559038737 ntoskrnl.c:1694: Test failed: got size 0 ntoskrnl.c:1699: Test failed: failed to open child: 0xc0000034 ntoskrnl.c:1703: Test failed: got error 6 ntoskrnl.c:1711: Test failed: got 0 child arrival messages ntoskrnl.c:1712: Test failed: got 0 child removal messages ntoskrnl.c:1715: Test failed: got error 6 ntoskrnl.c:1718: Test failed: got 0xc0000034 ntoskrnl.c:1722: Test failed: got error 6 ntoskrnl.c:1728: Test failed: got 0 child arrival messages ntoskrnl.c:1729: Test failed: got 0 child removal messages ntoskrnl.c:1833: Test failed: failed to remove device, error 0x57 ntoskrnl.c:1836: Test failed: expected failure ntoskrnl.c:1837: Test failed: got error 0 ntoskrnl.c:1857: Test failed: failed to open service, error 1060 ntoskrnl.c:291: Test failed: expected SERVICE_STOPPED, got 0 See https://test.winehq.org/data/patterns.html#ntoskrnl.exe:ntoskrnl This happens a couple of times per month, mostly in the 64-bit w1064-tsign tests. However this also happened on: * 2022-07-04 w7u-pt-PT despite it not having test signing turned on. * 2022-10-24 master: this is the first known instance of these failures in Wine. * 2022-12-01 lastestmaster: these failures seem to have been systematic on this Wine test configuration. Unlike on Windows, none of the official Wine test configurations seem to be having this 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 4

[Bug 53144] New: kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7
by WineHQ Bugzilla 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=53144 Bug ID: 53144 Summary: kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - test_kill_on_exit() sometimes fails on Windows 7: debugger.c:2122: Test failed: NtSetInformationDebugObject failed c0000008 debugger.c:2144: Test failed: NtSetInformationDebugObject failed c0000008 https://test.winehq.org/data/patterns.html#kernel32:debugger 0xc0000008 == STATUS_INVALID_HANDLE Sometimes only the second failure happens. -- 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 45057] New: "Wine Stable" is not optimized for your Mac.
by wine-bugs＠winehq.org 20 Feb '23

20 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=45057 Bug ID: 45057 Summary: "Wine Stable" is not optimized for your Mac. Product: Wine Version: unspecified Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sephirothfanatic(a)gmail.com As of macOS High Sierra 10.13.4, Apple has issued a warning that 32 bit apps are not going to work anymore and apps should be upgraded to 64 bit to "increase compatibility"; siting this article: https://support.apple.com/en-us/HT208436 -- 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 26