- wine-bugs - winehq.org

[Bug 21940] New: Rise of Legends Demo crashes with null pointer reference in msxml3?
by wine-bugs＠winehq.org 07 Jul '23

07 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=21940 Summary: Rise of Legends Demo crashes with null pointer reference in msxml3? Product: Wine Version: 1.1.40 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: msxml3 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Once you get past bug 19539, you have to choose to ignore two BHG errors; the game then starts and runs (though I got no sound). Trying to play a campaign crashed for me quickly with an msxml3 error (which is funny, since I had done winetricks msxml3, and winecfg shows the override, but the backtrace still shows Wine's msxml3): Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x7362be22). Backtrace: =>0 priv_from_xmlDocPtr+0x6(doc=(nil)) [dlls/msxml3/domdoc.c:127] in msxml3 1 xmldoc_add_ref+0x1d(doc=(nil)) [dlls/msxml3/domdoc.c:160] in msxml3 2 init_xmlnode+0x26(This=0x3fb63f8, node=0x7e222980, outer=0x3fb6418, dispex_data=0x73666dec) [dlls/msxml3/node.c:1714] in msxml3 3 create_element+0x6c(element=0x7e222980) [dlls/msxml3/element.c:797] in msxml3d 4 create_node+0x9d(node=0x7e222980) [dlls/msxml3/node.c:1736] in msxml3 5 queryresult_nextNode+0xdf(iface=0x3ff1120, nextItem=0x32ad60) [dlls/msxml3/queryresult.c:267] in msxml3 6 xmlnode_selectSingleNode+0xd3(iface=0x1e9510, kqueryString="TRIBE_MASK", resultNode=0x32ad60) [dlls/msxml3/node.c:1542] in msxml3 7 in legends (+0x6f34c) (0x0032b2dc) ... 0x7362be22 priv_from_xmlDocPtr+0x6 [dlls/msxml3/domdoc.c:127] in msxml3: movl 0x0(%eax),%eax 127 return doc->_private; -- 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 33

[Bug 52361] New: Spaceforce: Only a few columns of pixels are drawn when video plays
by WineHQ Bugzilla 07 Jul '23

07 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52361 Bug ID: 52361 Summary: Spaceforce: Only a few columns of pixels are drawn when video plays Product: Wine Version: 7.0-rc4 Hardware: x86-64 URL: https://www.fileplanet.com/archive/p-45836/Spaceforce- Rogue-Universe-Demo OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: jeremielapuree(a)yahoo.fr Distribution: Ubuntu Created attachment 71547 --> https://bugs.winehq.org/attachment.cgi?id=71547 console output with msvideo and avifile channels enabled At first sight, it looks the video are completely black. It is not the case. One can see at the very left of the screen one (?) column of pixels drawn when video plays. -- 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 55198] New: QuickBooks SS 2009 installer crash
by WineHQ Bugzilla 07 Jul '23

07 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55198 Bug ID: 55198 Summary: QuickBooks SS 2009 installer crash Product: Wine Version: 8.11 Hardware: x86-64 URL: https://web.archive.org/web/20210307180900/http://dlm3 .download.intuit.com/SBD/QuickBooks/2009/R1/QuickBooks SimpleStartDirect2009.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Blocks: 34028, 34029, 34040 Distribution: Ubuntu Created attachment 74793 --> https://bugs.winehq.org/attachment.cgi?id=74793 Wine 8.11 backtrace Immediately following what appears to be a successful installation of QuickBooks Simple Start 2009, a cmd prompt opens and there is immediately a crash. Backtrace: =>0 0x7b012187 RaiseException+0x42(code=<is not available>, flags=<is not available>, count=<is not available>, args=<is not available>) [/usr/src/packages/BUILD/dlls/kernelbase/debug.c:350] in kernelbase (0x0237f634) 1 0x00de2bda RpcRaiseException+0x2a(exception=0x6a6) [/usr/src/packages/BUILD/dlls/rpcrt4/rpcrt4_main.c:214] in rpcrt4 (0x0237f654) 2 0x00da9932 in rpcrt4 (+0x9932) (0x0237f694) 3 0x6e466a98 remote_CloseHandle+0xb8(handle=0x3) [/usr/src/packages/BUILD/dlls/msi/i386-windows/winemsi_c.c:2877] in msi (0x0237f824) 4 0x6e40ce50 MsiCloseHandle+0xa0(handle=<couldn't compute location>) [/usr/src/packages/BUILD/dlls/msi/handle.c:302] in msi (0x0237f854) 5 0x100106cc in msifd08.tmp (+0x106cc) (0x0237f934) 6 0x6f504251 (0x00000000) I installed MFC80 as the console log complains loudly without it (though the installation continues apparently without issue). The crash occurs regardless. Unfortunately I don't know what it is trying to do at this point. 2997111 pts/7 S 0:05 QuickBooksSimpleStartDirect2009.exe /qb /s 2997117 ? Ss 0:14 /opt/wine-devel/bin/wineserver 2997121 ? Ssl 0:00 C:\windows\system32\services.exe 2997127 pts/7 Sl 0:00 C:\windows\system32\explorer.exe /desktop 2997136 ? Ssl 0:01 C:\windows\system32\winedevice.exe 2997159 ? Ssl 0:00 C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted 2997164 ? Ssl 0:00 C:\windows\system32\plugplay.exe 2997173 ? Ssl 0:31 C:\windows\system32\winedevice.exe 2997192 pts/7 S 0:00 C:\windows\system32\conhost.exe --unix --width 238 --height 63 --server 0x10 2997219 pts/7 Sl 0:02 C:\users\test\Temp\FSE\QBooks\setup.exe 2997270 ? Ssl 0:14 C:\windows\system32\msiexec.exe /I C:\users\test\Temp\FSE\QBooks\QuickBooks.msi /lv* C:\users\test\Temp\QuickBooks_09.log QB_LICENSENUM=4999-8780-2611-708 QB_PRODUCTNUM=450-165 ISW_PRODUCTNUM=309691 ISW_LICENSENUM=160710205397039 CDSKU=CDATOMLIMITED MEDIAPACKAGEPATH=\QBooks\ 2997274 ? Ssl 0:05 C:\windows\system32\msiexec.exe -Embedding 416 2998870 ? Ss 0:00 winedbg --auto 428 136 2998872 ? Ss 0:00 C:\windows\system32\conhost.exe --server 0x2c 2999260 pts/7 R+ 0:00 ps -x This never used to occur so tried Wine 7.0 but it crashes in a different way (in Mono). Tried dotnet20 with Wine 7.0 and it crashes in yet another way. Given the amount of time needed to install this app (/qb /s isn't very effective) a bisect will take quite some time... As I cannot figure out how to work around this, marking related bugs as blocked. Will update when I know more. -- 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 34040] New: QuickBooks SS 2008 R1 crashes multiple times on second run
by wine-bugs＠winehq.org 07 Jul '23

07 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=34040 Bug #: 34040 Summary: QuickBooks SS 2008 R1 crashes multiple times on second run Product: Wine Version: 1.6-rc5 Platform: x86-64 URL: http://dlm.download.intuit.com/SBD/QuickBooks/2008/R1/ QuickBooksSimpleStartDirect2008.exe OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 45237 --> http://bugs.winehq.org/attachment.cgi?id=45237 wine-1.6-rc5 console output Running QB 2008 a second time after setting up a company file and closing the application will cause multiple crashes that are caught by the application itself. To get this far: 1. winetricks -q dotnet20 msxml4 (Bug 34028 and Bug 34029) 2. Install. 3. Run and set up a company file and save it. 4. Exit application. 5. Run application. Tried msxml3 but this simply causes the application to hang. NOTE: Native msxml3 cannot be installed before the first run as this appears to also cause Bug 34028. Tried vcrun2005 too but it made no difference. -- 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 5

[Bug 34028] New: QuickBooks SS 2008 R1 fails to load due to licence error
by wine-bugs＠winehq.org 07 Jul '23

07 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=34028 Bug #: 34028 Summary: QuickBooks SS 2008 R1 fails to load due to licence error Product: Wine Version: 1.6-rc5 Platform: x86-64 URL: http://download.microsoft.com/download/C/C/0/CC0BD555- 33DD-411E-936B-73AC6F95AE11/IE8-WindowsXP-x86-ENU.exe OS/Version: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: msxml4 AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 45219 --> http://bugs.winehq.org/attachment.cgi?id=45219 wine-1.6-rc5 console output QuickBooks SS 2008 R1 fails to load due to a "Could not initialize license properties" error. fixme:msxml:domdoc_setProperty Ignoring property L"NewParser", value {VT_I2: -1} fixme:msxml:domdoc_setProperty Ignoring property L"NewParser", value {VT_BOOL: ffffffff} [...] fixme:msxml:domdoc_get_parseError (0x1aa674)->(0x32f2dc): creating a dummy parseError Workaround is "winetricks msxml4". -- 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 9

[Bug 55153] New: comdlg32:filedlg sometimes crashes on Windows 7
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55153 Bug ID: 55153 Summary: comdlg32:filedlg sometimes crashes on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comdlg32:filedlg sometimes crashes on Windows 7: comdlg32:filedlg start dlls/comdlg32/tests/filedlg.c 0ef8:filedlg: unhandled exception c0000005 at 766523AD comdlg32:filedlg:0ef8 done (-1073741819) in 5s 56B See https://test.winehq.org/data/patterns.html#comdlg32:filedlg Where c0000005 == STATUS_ACCESS_VIOLATION The first crash happened on 2023-02-28 and there has been a bit over 1.5 per month since. -- 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 55200] New: MSVC cl.exe misbehaving (buggy/inconsistent behaviour) wrt include paths since "ntdll: Default to Windows 10"
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55200 Bug ID: 55200 Summary: MSVC cl.exe misbehaving (buggy/inconsistent behaviour) wrt include paths since "ntdll: Default to Windows 10" Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st Regression SHA1: 69154f0329aec4fb64886a0689da198b5323dcde Distribution: --- Background: I package MSVC with Wine wrapping, so that people can compile software using MSVC on Unix systems - see https://github.com/mstorsjo/msvc-wine. Since Wine 8.1, specifically commit 69154f0329aec4fb64886a0689da198b5323dcde "ntdll: Default to Windows 10", cl.exe in Wine started misbehaving with respect to how it finds headers in some include paths. The misbehaviour isn't entirely consistent and only appears in some fairly specific cases. (When compiling a project of the size of LLVM, with ~3000 compiled translation units, the bug appears in 3 of these translation units.) I've managed to reproduce the situation with a fairly minimal testcase. To reproduce, first install a fresh version of msvc-wine: $ git clone https://github.com/mstorsjo/msvc-wine $ cd msvc-wine $ ./vsdownload.py --dest $HOME/msvc2022-17.6 --accept-license $ ./install.sh $HOME/msvc2022-17.6 Then set up a minimal mock source project structure: $ mkdir -p msvc-include-bug/subdir $ touch msvc-include-bug/subdir/header.h $ echo '#include "subdir/header.h"' > msvc-include-bug/subdir/file.cpp Now test preprocessing file.cpp to see that it manages to find the header. Bypass the msvc-wine wrapper scripts and call it with wine manually: $ . $HOME/msvc2022-17.6/bin/x64/msvcenv.sh # Set up the INCLUDE/LIB/WINEDLLOVERRIDES env vars as necessary $ WINEDEBUG=-all wine64 $HOME/msvc2022-17.6/vc/tools/msvc/14.36.32532/bin/Hostx64/x64/cl.exe -P -Fipreproc.cpp -I$(pwd)/msvc-include-bug/subdir -I$(pwd)/msvc-include-bug z:$(pwd)/msvc-include-bug/subdir/file.cpp Microsoft (R) C/C++ Optimizing Compiler Version 19.36.32532 for x64 Copyright (C) Microsoft Corporation. All rights reserved. file.cpp This runs successfully, as reference example. Now update file.cpp to include <corecrt_wio.h> before "subdir/header.h": $ echo '#include <corecrt_wio.h>' > msvc-include-bug/subdir/file.cpp $ echo '#include "subdir/header.h"' >> msvc-include-bug/subdir/file.cpp Rerun the same compilation command: $ . $HOME/msvc2022-17.6/bin/x64/msvcenv.sh $ WINEDEBUG=-all wine64 $HOME/msvc2022-17.6/vc/tools/msvc/14.36.32532/bin/Hostx64/x64/cl.exe -P -Fipreproc.cpp -I$(pwd)/msvc-include-bug/subdir -I$(pwd)/msvc-include-bug z:$(pwd)/msvc-include-bug/subdir/file.cpp Microsoft (R) C/C++ Optimizing Compiler Version 19.36.32532 for x64 Copyright (C) Microsoft Corporation. All rights reserved. file.cpp z:/home/martin/msvc-include-bug/subdir/file.cpp(2): fatal error C1083: Cannot open include file: 'subdir/header.h': No such file or directory For some unknown reason, the extra set of headers included by <corecrt_wio.h> make cl.exe no longer find "subdir/header.h" even though -I$(pwd)/msvc-include-bug is passed to the compiler. The bug only appears when both $(pwd)/msvc-include-bug and $(pwd)/msvc-include-bug/subdir are added to the include path. $(pwd) expanding to an absolute unix path should be resolvable as an drive-relative (implicitly relative to z:) within Wine. Now if we clarify the include paths, that previously were set up as -I$(pwd)/... into fully absolute windows paths as -Iz:$(pwd)/..., then the test succeeds again: $ WINEDEBUG=-all wine64 $HOME/msvc2022-17.6/vc/tools/msvc/14.36.32532/bin/Hostx64/x64/cl.exe -P -Fipreproc.cpp -Iz:$(pwd)/msvc-include-bug/subdir -Iz:$(pwd)/msvc-include-bug z:$(pwd)/msvc-include-bug/subdir/file.cpp Microsoft (R) C/C++ Optimizing Compiler Version 19.36.32532 for x64 Copyright (C) Microsoft Corporation. All rights reserved. file.cpp Before the relevant Wine commit, this bug didn't appear at all in this case. It's probably easy to work around this issue within msvc-wine by rewriting -I arguments with absolute paths into Windows absolute paths like z:/... - but it's curious why this is needed now when it wasn't needed before, and MSVC cl.exe itself is acting very inconsistent here - it's only needed in this very precise setup. (For context, for future self: When compiling LLVM, this bug currently hits three files under llvm/lib/Target/AArch64/MCTargetDesc - AArch64WinCOFFObjectWriter.cpp, AArch64MCTargetDesc.cpp and AArch64TargetStreamer.cpp.) -- 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 0

[Bug 54135] New: JGlossator v5.0: Hovering textboxes not displaying
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54135 Bug ID: 54135 Summary: JGlossator v5.0: Hovering textboxes not displaying Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: metcalsr(a)gmail.com Distribution: --- Created attachment 73666 --> https://bugs.winehq.org/attachment.cgi?id=73666 +mshtml Application features hover-over translations for text in the search box. This is not only an important QoL feature, but often provides alternative translations which aid significantly in understanding the text. These hovering boxes break under wine. -- 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 11

[Bug 55024] New: Sims 4 Studio window flickering
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55024 Bug ID: 55024 Summary: Sims 4 Studio window flickering Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryu.ketsueki(a)outlook.com Distribution: --- This is something that was happening before for a while now but it was tolerable. Now it's unusable. Sims 4 Studio updated to the (Star) release, as in the 3.2.0.6 and it's actually usable now. The application doesn't freeze when trying to render anything 3D, which was apparently an issue on Sims 4 Studio itself, as even in a virtual machine, it had the exact same error. Could only get around it by a dual boot with Windows. Not anymore. Sims 4 Studio runs relatively well and I can create and modify game packages normally. That was until recently, when the flickering got so much worse. I'll explain what is happening. The window would hang frames for a bit and flicker them instead of completely update to the newest frame. Now it doesn't hang anymore. Instead, the window appears completely black, except when hovering over buttons or menus, when the window flash its content for a split second and goes black again. This is still on top of the flickering of before, so it still hangs frames but still goes black constantly, making the application unusable. Now, to my knowledge, Sims 4 Studio requires .NET 6.0 to launch at all. I had to install it to make it work, even when it was usable. Maybe this is related Mono or .NET itself, I don't know. I did observe a behavior that may be connected to what is going on. When the window is flashing black, the center of the window has a square showing the correct content but it's following the Windows 10/11 spinning wheel, so only this loading wheel shows correctly. The behavior persists even when the wheel is gone -- 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 55193] New: user32:sysparams - test_WM_DISPLAYCHANGE() fails on Windows 8
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55193 Bug ID: 55193 Summary: user32:sysparams - test_WM_DISPLAYCHANGE() fails on Windows 8 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:sysparams - test_WM_DISPLAYCHANGE() fails on Windows 8: sysparams.c:2473: Test failed: ChangeDisplaySettingsExW returned -1 sysparams.c:2504: Tests skipped: bpp 8: ChangeDisplaySettingsExW returned -1 sysparams.c:2504: Tests skipped: bpp 16: ChangeDisplaySettingsExW returned -1 sysparams.c:2505: Test failed: bpp 16: ChangeDisplaySettingsExW returned -1 sysparams.c:2504: Tests skipped: bpp 24: ChangeDisplaySettingsExW returned -1 sysparams.c:2505: Test failed: bpp 24: ChangeDisplaySettingsExW returned -1 sysparams.c:2523: Test failed: ChangeDisplaySettingsExW returned -1 See https://test.winehq.org/data/patterns.html#user32:sysparams Where -1 == DISP_CHANGE_FAILED (so not very helpful) This is systematic and impacts the two TestBot Windows 8 VMs. Also this check does not make sense: broken( DISP_CHANGE_FAILED && bpp == 8 ) and given that we get this res value for all bpps, maybe it should be: broken( res == DISP_CHANGE_FAILED ) -- 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 55195] New: wininet:http - test_http_connection() sometimes fails with a SENDING_REQUEST status on Windows
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55195 Bug ID: 55195 Summary: wininet:http - test_http_connection() sometimes fails with a SENDING_REQUEST status on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wininet:http - test_http_connection() sometimes fails with a SENDING_REQUEST status on Windows: http.c:4126: Testing reading compressed content from cache http.c:376: Test failed: unexpected status 30 (INTERNET_STATUS_SENDING_REQUEST) http.c:376: Test failed: unexpected status 31 (INTERNET_STATUS_REQUEST_SENT) http.c:376: Test failed: unexpected status 40 (INTERNET_STATUS_RECEIVING_RESPONSE) http.c:376: Test failed: unexpected status 41 (INTERNET_STATUS_RESPONSE_RECEIVED) http.c:376: Test failed: unexpected status 50 (INTERNET_STATUS_CLOSING_CONNECTION) http.c:376: Test failed: unexpected status 51 (INTERNET_STATUS_CONNECTION_CLOSED) http.c:3665: Test failed: expected status 30 (INTERNET_STATUS_SENDING_REQUEST) 1 times, received 2 times http.c:3666: Test failed: expected status 31 (INTERNET_STATUS_REQUEST_SENT) 1 times, received 2 times http.c:3667: Test failed: expected status 40 (INTERNET_STATUS_RECEIVING_RESPONSE) 1 times, received 2 times http.c:3668: Test failed: expected status 41 (INTERNET_STATUS_RESPONSE_RECEIVED) 1 times, received 2 times http.c:5908: Testing InternetReadFileExW with IRF_ASYNC flag... See https://test.winehq.org/data/patterns.html#wininet:http Sometimes some of the 41, 50 and 51 status failures do not happen. These failures go back to at least 2022-11-29 and have happened a bit over once per month since, impacting all Windows versions. But there have been months with no failure too, and lately it has mostly been happening on Windows 8: * 2022-11-29 win22H2_fgtb-w10pro64-rx550-64 * 2023-03-10 win21H1_newtb-w10pro64-32 * 2023-03-20 win7_newtb-w7pro64-64 * 2023-03-28 win22H2_fgtb-w10pro64-32 * 2023-04-06 win7_newtb-w7u-pt-PT * 2023-04-28 win21H1_newtb-w10pro64-ru-64 * 2023-05-22 win21H1_newtb-w10pro64-fr-64 * 2023-06-08 win81_newtb-w8adm * 2023-07-04 win81_newtb-w864-64 * 2023-07-04 win81_newtb-w8 -- 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 55192] New: user32:sysparams - test_SPI_SETWALLPAPER() fails to restore the '(None)' wallpaper
by WineHQ Bugzilla 05 Jul '23

05 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55192 Bug ID: 55192 Summary: user32:sysparams - test_SPI_SETWALLPAPER() fails to restore the '(None)' wallpaper 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:sysparams - test_SPI_SETWALLPAPER() fails to restore the '(None)' wallpaper: sysparams.c:2442: Test failed: ***warning*** failed to restore the original value: rc=0 err=2 sysparams.c:346: Test failed: Wrong value in registry: Control Panel\Desktop Wallpaper '' instead of '(None)' See https://test.winehq.org/data/patterns.html#user32:sysparams Where 2 == ERROR_FILE_NOT_FOUND This is systematic and specific to the w7u VM. The way I understand it that VM does not have a wallpaper but instead of returning the like of an empty string, SPI_GETDESKWALLPAPER returns '(None)' (maybe this is even the registry value). Anyway when we try to restore the value, SPI_SETDESKWALLPAPER checks that the '(None)' file exists and fails. To investigate: * Is '(None)' the actual registry value? * Do our other VMs really all have a wallpaper? Is that why none of them returns '(None)'? * If another Windows version has no wallpaper does SPI_GETDESKWALLPAPER return 'None' or is that specific to Windows 7? * To fix the test, check whether the oldvalue file exists and set the wallpaper to an empty string if not? Or bypass SPI_SETDESKWALLPAPER to set the registry directly in that case? -- 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 55171] New: Wine app does not run on openSUSE Leap
by WineHQ Bugzilla 04 Jul '23

04 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55171 Bug ID: 55171 Summary: Wine app does not run on openSUSE Leap Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: niltongmedeiros(a)gmail.com Distribution: --- The Wine app does not run on openSUSE Leap 15.5 KDE 5.103.0, does not appear in the menu, downloaded and installed from the Discover store. How can I proceed? -- 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 47067] New: Font is too wide in RPGMaker game Hello Charlotte
by wine-bugs＠winehq.org 04 Jul '23

04 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47067 Bug ID: 47067 Summary: Font is too wide in RPGMaker game Hello Charlotte Product: Wine Version: 4.6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 64246 --> https://bugs.winehq.org/attachment.cgi?id=64246 Screenshot on Wine The font in the game is too wide, meaning long lines are cut off. Already tried winetricks allfonts, which doesn't help. To reproduce, just download the game, run Game.exe and click Start in the mainmenu. -- 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 6

[Bug 53230] New: user32:win - test_activateapp() fails randomly with fvwm
by WineHQ Bugzilla 04 Jul '23

04 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53230 Bug ID: 53230 Summary: user32:win - test_activateapp() fails randomly with fvwm Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:win - test_activateapp() fails randomly with fvwm. The failures themselves change quite a bit from one run to the next, depending on where in the function the failures start. It looks a bit like a race condition between the test and the window manager. Here is a relatively complete set: win.c:10976: Test failed: Expected foreground window 0, got 01DE007C win.c:10982: Test failed: Expected foreground window 001A013C, got 01DE007C win.c:10992: Test failed: Expected foreground window 001A013C, got 00000000 win.c:10999: Test failed: Expected foreground window 001A013C, got 01DE007C win.c:11001: Test failed: GetActiveWindow() = 00000000 win.c:11001: Test failed: GetFocus() = 00000000 win.c:11003: Test failed: Received WM_ACTIVATEAPP(0), did not expect it. win.c:11011: Test failed: Expected foreground window 001A013C, got 00000000 win.c:11013: Test failed: GetActiveWindow() = 00000000 win.c:11013: Test failed: GetFocus() = 00000000 win.c:11021: Test failed: Received WM_ACTIVATEAPP(1), did not expect it. https://test.winehq.org/data/patterns.html#user32:win The failures don't seem to depend on the locale or bitness. However they only happen in the TestBot VMs which happen to run fvwm (with a specially curated configuration file) and don't happen on my box which runs KDE for instance. -- 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 55188] New: Total Commander v10.52 in copy mode does not allow you to switch between other applications while remaining on top of windows.
by WineHQ Bugzilla 04 Jul '23

04 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55188 Bug ID: 55188 Summary: Total Commander v10.52 in copy mode does not allow you to switch between other applications while remaining on top of windows. Product: Wine-staging Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 93.duke.xperia(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Total Commander v10.52 in copy mode does not allow you to switch between other applications while remaining on top of windows. This is observed on Ubuntu 22.04.2 / Ubuntu MATE 22.04.2 / Linux Mint 21.1 Cinnamon In Ubuntu MATE 22.04.2, it can only be minimized through the taskbar, but in Linux Mint 21.1 Cinnamon, it cannot be minimized through the taskbar. This does not happen on Xubuntu 22.04.2 and KDEneon Total Commander download https://www.ghisler.com/download.htm -- 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 55158] New: Mouse input is broken at "POSTAL: Brain Damaged"
by WineHQ Bugzilla 03 Jul '23

03 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55158 Bug ID: 55158 Summary: Mouse input is broken at "POSTAL: Brain Damaged" Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru Distribution: --- Created attachment 74723 --> https://bugs.winehq.org/attachment.cgi?id=74723 Output log of application. At game "POSTAL: Brain Damaged" (GOG version) reaction to mouse moving is wrong, looking around with mouse is impossible. Cursor at menu works normally. -- 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 49229] New: Regression Requiem: Rise of the Reaver mouse issue since Release v5.0-rc3
by WineHQ Bugzilla 03 Jul '23

03 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49229 Bug ID: 49229 Summary: Regression Requiem: Rise of the Reaver mouse issue since Release v5.0-rc3 Product: Wine-staging Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ergoschnuffel(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- radeon/amdgpu (same behaviour) X11 on openbox Game: Requiem: Rise of the Reaver (http://www.playrequiem.com/) Use case: windowed multi client (transfer of items, shop open in the background etc.) issues: - need to click once to activate the game window and then it operates normally, before it was a direct click through (activate game window and action in the game) - mouse cursor gets trapped in game window A while moving the mouse to game window B and activating game window B (game window A/B overlapping a bit since monitor resolution). My issues started between Release v5.0-rc2 and Release v5.0-rc3 (update of the raw input patches?) and are still on going. -- 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 55186] New: Visual Pinball 8.1.1 doesn't display table when it's not cached
by WineHQ Bugzilla 03 Jul '23

03 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55186 Bug ID: 55186 Summary: Visual Pinball 8.1.1 doesn't display table when it's not cached Product: Wine Version: 8.11 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: --- Program download: https://archive.org/download/Visual_Pinball_2020-06-20/Visual%20Pinball%20M… Table download: http://weltenschule.de/pinball/Boomerang1.4emu.zip - Use wine-8.11 - Create new 32bit WINEPREFIX - "winetricks whs57 oleaut32", work around bug 8780 and vbscript issues - Run VPinball.exe - Preferences -> Video Options -> Uncheck "Cache Rendered Table" - File -> Open -> Select table - Press F5 - Close the "Visual Pinball Player" window again - Press F5 again A lot of textures are now missing. This is probably a d3d issue, though not 100% sure. -- 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 0

[Bug 55183] New: Can't run terabox.exe
by WineHQ Bugzilla 03 Jul '23

03 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55183 Bug ID: 55183 Summary: Can't run terabox.exe Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thidcon(a)gmail.com Distribution: --- Created attachment 74774 --> https://bugs.winehq.org/attachment.cgi?id=74774 The file describes the feedback resulting from running terabox.exe (https://data.nephobox.com/issue/terabox/PCTeraBox/TeraBox_1.20.0.6.exe) run from the terminal. I'm using wine-8.11 (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.

1 10

[Bug 45772] New: Neo Manager needs 'pnputil.exe /a'
by wine-bugs＠winehq.org 02 Jul '23

02 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45772 Bug ID: 45772 Summary: Neo Manager needs 'pnputil.exe /a' Product: Wine Version: 3.15 Hardware: x86 URL: http://support.renlearn.com/techkb/download/NEOManager 3_9_3USPC.zip OS: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: pnpmgr Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Continued from bug 45735. The installer runs `PnPUtil /a C:\Windows\Inf\AsUSBDrv.inf` to install its drivers. This fails since Wine doesn't implement pnputil.exe. Relevant part of wine log: Z:\home\hazel\Downloads\NEOManager3_9_3USPC>PnPUtil /a C:\Windows\Inf\AsUSBDrv.inf Can't recognize 'PnPUtil /a C:\Windows\Inf\AsUSBDrv.inf' as an internal or external command, or batch script. hazel@watership:~/Downloads$ sha1sum NEOManager3_9_3USPC.zip a844ab468a2c2034c0404f7fc655b7746c410d11 NEOManager3_9_3USPC.zip hazel@watership:~/Downloads$ du -sh NEOManager3_9_3USPC 70M NEOManager3_9_3USPC -- 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 55173] New: building error: Can't find identifier during alsa building stage.
by WineHQ Bugzilla 02 Jul '23

02 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=55173 Bug ID: 55173 Summary: building error: Can't find identifier during alsa building stage. Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ale.schenberg(a)yandex.com Distribution: --- Created attachment 74754 --> https://bugs.winehq.org/attachment.cgi?id=74754 console output while building Hello. While building the "alsamidi.o" file, an error due to an undeclared identifier shows up. The error happens in the "alsa_midi_init" function. More details are in the attached 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.

1 1

[Bug 28678] New: DirectDraw primary buffer is obscured by transparent window
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=28678 Bug #: 28678 Summary: DirectDraw primary buffer is obscured by transparent window Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: octavian.voicu(a)gmail.com Classification: Unclassified Created attachment 36852 --> http://bugs.winehq.org/attachment.cgi?id=36852 Screenshot showing the obscured dialog. When trying to exit from the game The Longest Journey (either via menu option or pressing Alt+F4), a dialog box is shown with Yes/No options. The application uses DirectDraw for rendering. The dialog box and mouse cursor are rendered on an offscreen surface (dialog has an image as the background and buttons use a custom implementation afaics), which is then blitted to the primary buffer (happens like this when you force single buffer mode; with double buffering it could be slightly different, but the overall effect is the same). The dialog is a parent of the main application window, uses the standard dialog window class (atom #32270 or 8000 in hex) and has the WS_POPUP and WS_EX_TRANSPARENT window styles. Window receives a WM_ERASEBKGND message, which is handled by the default dialog proc by painting the background in the standard window background color (gray in this case). When primary buffer is blitted to the d3d surface (ddraw_surface_update_frontbuffer which uses OpenGL), the rendering of the dialog is masked by the window boundaries and the gray rectangle remains. Dialog is interactable and you can click the buttons (if you can do that without seeing where the mouse is). The question is: how can we make the primary buffer draw over WS_EX_TRANSPARENT child windows, as it works on native? Removing the WS_EX_TRANSPARENT style from the dialog window (on runtime, using WinSpy++ 1.7) makes native's behavior identical to current wine behavior (only a gray rectangle is visible). -- 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 30

[Bug 54638] New: amazon music does not let wineserver quit (on shutdown)
by WineHQ Bugzilla 01 Jul '23

01 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54638 Bug ID: 54638 Summary: amazon music does not let wineserver quit (on shutdown) Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: wine(a)stegm.de Distribution: --- amazon music does not let wineserver quit (on shutdown). That results in waiting for systemd to kill wineserver after 2 minutes. Or wineserver -k must be run as user before shutdown. -- 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 43054] New: FlightUnlimited II crashes during map load, Unhandled page fault on read access to 0x00000039 at address 0x41f87f ( thread 0009)
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=43054 Bug ID: 43054 Summary: FlightUnlimited II crashes during map load, Unhandled page fault on read access to 0x00000039 at address 0x41f87f (thread 0009) Product: Wine Version: 2.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haakobja(a)gmail.com Distribution: --- Created attachment 58220 --> https://bugs.winehq.org/attachment.cgi?id=58220 Log from FlightUnlimitedII I recently installed Flight Unlimited II through Wine. After successfully loading the menus (the game needs quartz.dll override, if not it crashes during intro), I tried to play. Only to experience an error stating "Unhandled page fault on read access to 0x00000039 at address 0x41f87f (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000039 in 32-bit code (0x0041f87f)" being thrown in my face. -- 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 9

[Bug 36211] New: Sybase PowerDesigner 16.5 'pdshell16.exe' (.NET 4.x WPF app) reports scripting error, needs VBScript_AddTypeLib implementation
by wine-bugs＠winehq.org 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=36211 Bug ID: 36211 Summary: Sybase PowerDesigner 16.5 'pdshell16.exe' (.NET 4.x WPF app) reports scripting error, needs VBScript_AddTypeLib implementation Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says ... Prerequisite: 'winetricks -q dotnet40 vb6run' You might need to navigate the main menu items multiple times until the sub-menu popup shows up (another bug). Main menu, select 'File' -> 'New Model' -> 'XML Model' -> 'XML Model Diagram' A message box is shown, telling "scripting error occurred" Unfortunately this isn't reproducible every time. There seem to be multiple Wine bugs in this app, influencing each other :| --- snip --- fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() --- snip --- Source: http://source.winehq.org/git/wine.git/blob/9eed654e054520888429fb7ea1c9d8cc… --- snip --- 447 static HRESULT WINAPI VBScript_AddTypeLib(IActiveScript *iface, REFGUID rguidTypeLib, 448 DWORD dwMajor, DWORD dwMinor, DWORD dwFlags) 449 { 450 VBScript *This = impl_from_IActiveScript(iface); 451 FIXME("(%p)->()\n", This); 452 return E_NOTIMPL; 453 } --- snip --- $ sha1sum PowerDesigner165_DMR.exe c74e4cfd99500d9e3e32713b302ea35bc3f911fb PowerDesigner165_DMR.exe $ du -sh PowerDesigner165_DMR.exe 810M PowerDesigner165_DMR.exe $ wine --version wine-1.7.17-148-g2e5cb7a Regards -- 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 6

[Bug 8780] Multiple applications using native vbscript/jscript override need oleaut32.CreateTypeLib implementation (Visual Studio 20XX, Future Pinball, ...)
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=8780 --- Comment #35 from Nikolay Sivov <bunglehead(a)gmail.com> --- (In reply to Fabian Maurer from comment #33) > Isn't that acceptable until it we find a program that requires it being that > old format? There are patches that provide some writing support for this format, at https://github.com/wine-staging/wine-staging/tree/master/patches/widl-SLTG_…. -- 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 0

[Bug 8780] Multiple applications using native vbscript/jscript override need oleaut32.CreateTypeLib implementation (Visual Studio 20XX, Future Pinball, ...)
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=8780 --- Comment #34 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Fabian Maurer from comment #33) > Isn't that acceptable until it we find a program that requires it being that > old format? Bug 3689 is about a Microsoft program which basically ships a modified copy of oleaut32.dll that expects stdole32.tlb to be in SLTG format. That might not extend to CreateTypeLib(), but if it's happened once... -- 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 0

[Bug 8780] Multiple applications using native vbscript/jscript override need oleaut32.CreateTypeLib implementation (Visual Studio 20XX, Future Pinball, ...)
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=8780 --- Comment #33 from Fabian Maurer <dark.shadow4(a)web.de> --- Isn't that acceptable until it we find a program that requires it being that old format? -- 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 0

[Bug 8780] Multiple applications using native vbscript/jscript override need oleaut32.CreateTypeLib implementation (Visual Studio 20XX, Future Pinball, ...)
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=8780 --- Comment #32 from Nikolay Sivov <bunglehead(a)gmail.com> --- It should create SLTG typelibs I believe, so the patch is wrong. -- 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 0

[Bug 8780] Multiple applications using native vbscript/jscript override need oleaut32.CreateTypeLib implementation (Visual Studio 20XX, Future Pinball, ...)
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=8780 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #31 from Fabian Maurer <dark.shadow4(a)web.de> --- Also affects Visual Pinball, see the forum thread: https://forum.winehq.org/viewtopic.php?t=37788 Is there plans to have this upstreamed? -- 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 0

[Bug 55168] New: BUSY 21 Installer silently exists with Windows version set to Win10
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55168 Bug ID: 55168 Summary: BUSY 21 Installer silently exists with Windows version set to Win10 Product: Wine Version: 8.10 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: --- Workaround is "winetricks winxp" -- 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 55147] New: Enter key isn't working in my VB6 Application
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55147 Bug ID: 55147 Summary: Enter key isn't working in my VB6 Application Product: Wine Version: 8.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: vikasy.enjay(a)gmail.com Distribution: --- The Application is successfully installed in a 32 bit prefix but when i run the application then on a certain form where Enter Key and Backspace keys are used for moving to next and previous text fields respectively, it doesn't work. And when i run the same application in windows Enter key and Backspace key works perfectly on the same form to move to next text field and backspace key to previous field respectively. Thank you for your attention to this matter your assistance will be valued. -- 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 54888] New: Transparent window are displayed as black background window on wine
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54888 Bug ID: 54888 Summary: Transparent window are displayed as black background window on wine Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bcjon07(a)gmail.com Distribution: --- Some transparent windows are displayed as black background window. Here is a simple WPF window program that can reproduce this issue. On Windows, all parts are transparent except for the graphics and text in the middle, but it has a black background on Wine. It achieves transparency only by adding the following code to the window constructor (the main point is that WindowChrome is used instead of AllowTransparent): WindowStyle = WindowStyle.None; ResizeMode = ResizeMode.NoResize; Background = Brushes.Transparent; WindowChrome.SetWindowChrome(this, new WindowChrome { GlassFrameThickness = new Thickness(-1) }); Download link of the demo program: https://drive.google.com/file/d/1MCrnb1N6cLUzVoX_vO4tFO4qlS_qhAwi/view?usp=… Other clues: Transparent windows implemented using AllowTransparent are valid on Wine, while those implemented using WindowChrome are invalid. On Windows, transparent forms implemented using WindowChrome are frequently used due to better performance(usually). According to my pre investigation, AllowTransparent seems to be implemented using GDI, but WindowChrome mainly uses the DWM API System architecture: x86_64 Ubuntu 20.04 wine 8.6 wine-mono 7.4.0 -- 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 54197] New: cuda-z and warpem fail in wine-staging 7.22 and later
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54197 Bug ID: 54197 Summary: cuda-z and warpem fail in wine-staging 7.22 and later Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 73728 --> https://bugs.winehq.org/attachment.cgi?id=73728 screenshot of running cuda-z one wine-staging 7.22 cuda-z fails to run in wine-staging 7.22 and later. It reports the error "CUDA not found. Please update the nvidia-driver.". cuda-z runs fine under wine-staging 7.21 (and earlier) on the same machine with the same nvidia driver. The application "WarpEM" can be also not used anymore because it does not find any GPU. I suspect that disabling the nvcuda-support patches in wine-staging [1] is the reason for this breakage. I believe bug #54102 is related, but the bug report says that this occured already in v7.21. But this issue is not reproducible to me in 7.21 only in 7.22. [1] https://gitlab.winehq.org/wine/wine-staging/-/commit/6c3797b3e8dba19698328c… [2] https://bugs.winehq.org/show_bug.cgi?id=54102 -- 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 55011] New: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55011 Bug ID: 55011 Summary: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: nvcuda Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- M of WarpEM gets stuck very early and eventually crashes. The following steps are needed to reproduce this: 1) install WarpEM according to [1] into wine-staging between v7.17 and v7.21, or wine-8.9 with nvidia-libs. (do not try with wine-staging 7.22 or later, because that has cuda support disabled). This has been testing this with "Shared WoW64" configuration of Wine. Trying to use Wine with the "new WoW64 approach" using -enable-archs=i386,x86_64 did also not work for me, because it failed much earlier when trying to install Cuda/WarpEM. 2) Data (5.5TB!) for testing is available from here [1]. Download and unpack Warpem_test.tar.gz to a directory that is accessible from wine. The screenshots Step1-7 should help to understand how M is supposed to be used. 3) Start M.exe. In my case, I do this ulimit -s 655360 wine $WINEPREFIX/drive_c/Warp/M.exe or vglrun wine $WINEPREFIX/drive_c/Warp/M.exe 4) Within M, do the following steps (see also Step1-7 in [2]): - Step 1: In the GUI window click "LOAD EXISTING FROM FILE" - Step 2: select ...\M_j33\Gag_c2_processing.population - Step 3: Upper right corner Refine button. - Step 4: Click refine - Step 5+6: workers are now testing the memory - Step 7: Eventually (after several minutes), one of the works crash, and there is no further progress. On Windows, this finishes and a new screen appears for the next step. This is not the case here. It gets stuck, and and eventually I stopped wine with <ctrl-C>. A log file is also available [2], but it is too large (1.1 GB) to be included here. If you have suggestions with WINEDEBUG filter should be used, let me know. [1] https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620&iTestin… [2] https://pub.ista.ac.at/~schloegl/warpem-test-data/ -- 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 54480] New: GPU Caps Viewer does not report any CUDA devices
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54480 Bug ID: 54480 Summary: GPU Caps Viewer does not report any CUDA devices Product: Wine-staging Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: danielyhwong(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- wine version 8.1 does not report any cuda devices in Caps viewer 1.58.01 $ deviceQuery deviceQuery Starting... CUDA Device Query (Runtime API) version (CUDART static linking) Detected 2 CUDA Capable device(s) CUDA https://i.imgur.com/zbTiqfC.png OpenCL https://i.imgur.com/jvu8nde.png -- 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 55159] New: [ms-mpi] mpiexec is unable to connect to the smpd service
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55159 Bug ID: 55159 Summary: [ms-mpi] mpiexec is unable to connect to the smpd service Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: christian.friedl(a)gmx.at Distribution: Ubuntu Created attachment 74727 --> https://bugs.winehq.org/attachment.cgi?id=74727 Output of `smpd.exe -d` and `mpiexec -d -hosts 1 127.0.0.1 notepad` Running applications with MS-MPI does not work. In order to circumvent https://bugs.winehq.org/show_bug.cgi?id=50341 I started smpd.exe manually with: $ wine 'C:\Program Files\Microsoft MPI\Bin\smpd.exe' -d In a second shell I ran mpiexec: $ wine mpiexec -d -hosts 1 127.0.0.1 notepad The problem is that mpiexec.exe could not connect to smpd.exe because both kerberos and ntlm authentication fail. I have the version 2:4.15.13+dfsg-0ubuntu1.1 of the winbind package installed. The installed MS-MPI version is v10.1.2. Logs including the debug channels `+kerberos,+ntlm,+secur32,+wininet,+seh,+tid` are 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.

1 4

[Bug 55162] New: Halo 2: Installer shows empty ie-window
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55162 Bug ID: 55162 Summary: Halo 2: Installer shows empty ie-window Product: Wine Version: 8.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: odecif(a)gmail.com Distribution: --- Created attachment 74732 --> https://bugs.winehq.org/attachment.cgi?id=74732 console log, 32bit with ie6 installed, after starting "Startup.exe" I do not know why the previous bug was closed in 2015 (https://bugs.winehq.org/show_bug.cgi?id=17543), but the same error still persists today. When executing "Startup.exe" on the CD in a clean 32-bit (and 64-bit as well) prefix a blue windows pops up dislaying absolutely nothing presented (see image). If I install ie6 (winetricks ie6) an error pops up (see image). Attached is a stacktrace of what exists in the console after executing "Startup.exe" from wineconsole with ie6 installed. Br Bob -- 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 55163] New: compact.exe missing
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55163 Bug ID: 55163 Summary: compact.exe missing Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sakul8826(a)gmail.com Distribution: --- Hello, I wanted to use "compact.exe," which is a part of the default Windows 10 installation. I selected "Windows 10" in winecfg, and it appears that compact.exe is missing. I need this program to compress my content (cars, apps, etc.) in Assetto Corsa's Content Manager to reduce their size. I have very limited storage available, and this program (compact.exe) would be extremely helpful. I believe it should be relatively simple to implement this since we could use a Linux compression and decompression tool. Are there any plans to implement this? Thank you in advance. Best regards, Tim Gromeyer -- 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 37664] New: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680
by wine-bugs＠winehq.org 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37664 Bug ID: 37664 Summary: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rickardj42(a)gmail.com Distribution: --- Created attachment 50128 --> https://bugs.winehq.org/attachment.cgi?id=50128 Screenshot of the error message In MediaCoder x64 0.8.33 build 5680 attempting to select GPU encoder causes error "No supported acceleration hardware detected", dispite the presence of an NVidia GeForce 750ti in my system. Attempting to force GPU encoding using CUDA encoder results in Error (14) on all items(general encoder error). -- 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 55157] New: Net6 x64 app: unable to allocate more than ~1GB of contiguous memory, OutOfMemory exception
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55157 Bug ID: 55157 Summary: Net6 x64 app: unable to allocate more than ~1GB of contiguous memory, OutOfMemory exception Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: korshunov(a)macroscop.com Distribution: --- A "big" net6 app may throw an OutOfMemory exception at some point in time. It was found that the exception occurs when the size of byte array is increased and exception is repeatable 100% - it always fails when byte array resized from 26mb to 53mb. Since big app is hard to debug, a simple test app was written, all it tries to do is to resize array x2 in a loop. Test app fails with dotnet OutOfMemory exception 100% of the time, but in the test app the "limit" at which it fails is different, about ~1gb or "Failed at resizing from 534773760 to 1069547520". Here's the code of the test app: var array = new byte[1023]; while (true) try { Array.Resize(ref array, array.Length * 2); } catch (Exception ex) { Console.WriteLine($"Failed at resizing from {array.Length} to {array.Length * 2}\r\n" + ex); return; } Test app is built for "AnyCPU, x64 preferred". Net6 runtime (6.0.16) is installed via winetricks. For the tests, x86 version of net6 runtime has been uninstalled, so the test app is guaranteed to run in x64. Test app is available via the link below. What I've already tried: - wine 8.11 staging - fails with OutOfMemory exception, "Failed at resizing from 534773760 to 1069547520". WINEDEBUG output available through the link below. - wine 8.0 with patch from https://bugs.winehq.org/show_bug.cgi?id=52396 - fails with same error. WINEDEBUG output available through the link below. - running app with wine64, used clean prefix - same error. - wine 7.13 - fails with same error. - wine 8.11, but test app built for netFramework46 - no OutOfMemory, fails when overflowing integer, "Failed at resizing from 2139095040 to -16777216" which is expected, but it shows that it gets to 2gb mark for the array. I consider this as "working fine". WINEDEBUG output available through the link below. - WineGE with multiple versions from 6.14 to 8.8, consisting of Proton and WineGE patches - net6 app working fine with every wineGE version tested, just as netFramework Test app - created prefix with wine 8.11, run test app, then run test app with WineGE in the same exact prefix - wine fails with OutOfMemory while wineGE executes app normally. - made different net6 app, which just allocates a single array of ~1.5 GB (new byte[1_500_000_000]) - app fails with OutOfMemory every time. It fails at about 1GB (950mb works, while 1050mb does not) Tests were done on three different virtual machines (ubuntu22, centos7, debian9) with different amount of RAM (4-8 GB, swap is 2.5GB). Wine 8.11 is installed on Ubuntu 22 with 4GB RAM. What caught my attention in the logs was the message "find_free_block created new sub-heap xxx of 0x400000 bytes" (4GB, all of the RAM), which mentioned in "net6" logs 1 time, and not mentioned in "netFramework46" logs. What else can I try to fix this or to provide more information? Links to a WINEDEBUG output (wine8.11-net6, wine8.11-netFramework46, "wine 8.0 with patch"-net6), logs taken with command WINEDEBUG=+timestamp,+seh,+heap,+virtual,+pid wine Tests_autoresize/Tests_net6.exe >>wine811_tshvp_net6_resize.log 2>&1 https://drive.google.com/drive/folders/1fgr0J6dKBvBOHWrfYC0UCrflxiAYOjZ2?us… -- 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 55044] New: dnSpy 6.2.0 crashes on start with a stackoverflow
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55044 Bug ID: 55044 Summary: dnSpy 6.2.0 crashes on start with a stackoverflow Product: Wine Version: 8.9 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: --- This is introduced in https://github.com/dnSpyEx/dnSpy/releases/download/v6.2.0-rc1/dnSpy-net-win… Version 6.1.9 works: https://github.com/dnSpyEx/dnSpy/releases/download/v6.1.9/dnSpy-net-win64.z… -- 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 55098] New: wine 8.10 32-bit build fails with clang-16
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55098 Bug ID: 55098 Summary: wine 8.10 32-bit build fails with clang-16 Product: Wine Version: 8.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: randrik(a)mail.ru Distribution: --- I tried to build new wine with llvm/clang 16.0.6 and gcc 11.2 (on Slackware 15.0 i586 upgraded manually from earlier vesrions). Kernel is x86_64 but al userland is i586/i686 Build via slackbuild fails like this: (will attach end of build log as attach) -- 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 54739] New: oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54739 Bug ID: 54739 Summary: oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine 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:typelib - The 64-bit test_register_typelib_64() crashes in Wine: typelib.c:7057: Test failed: got 00000002 typelib.c:8195: Test failed: got wrong return code: 2, side: 0200 typelib.c:8231: Test failed: got: 80040155, side: 0200 typelib.c:8235: Test failed: got: 80040154, side: 0200 Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000000428dc1). [...] Backtrace: =>0 0x00000000428dc1 in oleaut32_test (+0x28dc1) (0x0000000050e538) 1 0x000000004460c8 in oleaut32_test (+0x460c8) (0x000000621080c0) 2 0x0000000050dbeb in oleaut32_test (+0x10dbeb) (0x00000000ab4415) 3 0x0000000050d447 in oleaut32_test (+0x10d447) (0000000000000000) 4 0x0000007b629409 BaseThreadInitThunk+0x9(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\kernel32\thread.c:61] in kernel32 (0000000000000000) 5 0x00000170061213 __wine_pop_frame(entry=000000000050D3E0, arg=00000000003F0000) [Z:\home\winetest\tools\testbot\var\wine\include\wine\exception.h:277] in ntdll (0000000000000000) 6 0x00000170061213 RtlUserThreadStart+0x83(entry=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:295] in ntdll (0000000000000000) 0x00000000428dc1 oleaut32_test+0x28dc1: mov (%rcx), %rax See https://test.winehq.org/data/patterns.html#oleaut32:typelib Where: 2 == ERROR_FILE_NOT_FOUND 0x80040154 == REGDB_E_CLASSNOTREG 0x80040155 == REGDB_E_IIDNOTREG -- 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 50938] New: Stop alt key from getting stuck on alt-tab
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50938 Bug ID: 50938 Summary: Stop alt key from getting stuck on alt-tab Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sojuz151(a)gmail.com Distribution: --- When you use alt-tab shortcut to switch to another window and then switch back in, application will at no point receive alt key up signal. User needs to press alt again to make this key unstuck. This behevior is observed in Plasma and in lxde, both of them use alt-tab for windows switching. Behaviour on windows: alt key is not stuck in down position after alt-tabing out of any application How to test: this can be observed in any keyboard testing program. I used switch hitter for testing. Is it really a bug? Maybe not. Still very annoying in full-screen games. -- 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 49787] New: Java fails to start with "Could not create the Java Virtual Machine" - "Could not reserve enough space for object heap"
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=49787 Bug ID: 49787 Summary: Java fails to start with "Could not create the Java Virtual Machine" - "Could not reserve enough space for object heap" Product: Wine Version: 5.16 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: --- You can download java from https://jdk.java.net/java-se-ri/7 (just unpack) To reproduce, just go into "bin" and run "wine java -Xmx1024M -version". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 49551] New: the installer tries to run Java 2 version 1.3.1 but failed
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=49551 Bug ID: 49551 Summary: the installer tries to run Java 2 version 1.3.1 but failed Product: Wine Version: 1.8.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pritishparihar95(a)gmail.com Distribution: --- Created attachment 67691 --> https://bugs.winehq.org/attachment.cgi?id=67691 Installanywhere windows for reference Installing Software Parashar Light Profession 7.0.1 After InstallAnywhere window no window comes up, I tried to find error code fron winedbg Error code: WineDbg starting on pid 001c 0x7b85f870: subl $8,%esp Invalid address (0x7b85f87a) for breakpoint 0, disabling it Process of pid=001c has terminated -- 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 7767] Zero G Software 'InstallAnywhere' installers crash or silently exit (Rosetta Stone, Reading Counts, World Religions, Parashara's Light Professional 7.0.1)
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=7767 Damjan Jovanovic <damjan.jov(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Fixed by SHA1| |f70fc9cbfc1b91864d99c6b3a52 | |7a77ad0106ad7 Resolution|--- |FIXED --- Comment #17 from Damjan Jovanovic <damjan.jov(a)gmail.com> --- My merge request was merged: https://gitlab.winehq.org/wine/wine/-/merge_requests/3111 Resolving fixed :-). Thank you for your bug report and tests. -- 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 0

[Bug 54860] New: mf:mf - test_media_session_events() sometimes gets an unexpected refcount in Wine
by WineHQ Bugzilla 27 Jun '23

27 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54860 Bug ID: 54860 Summary: mf:mf - test_media_session_events() sometimes gets an unexpected refcount in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mf:mf - test_media_session_events() sometimes gets an unexpected refcount: * The most recent Windows failure happened on 2023-04-06 w10pro64v2004: mf.c:2382: Test failed: Release returned 2 mf.c:2384: Test failed: Release returned 3 mf.c:2386: Test failed: Release returned 2 mf.c:2388: Test failed: Release returned 1 * The oldest Wine failure happened on 2023-04-11 and the refcount is always 1 in that case. mf.c:2558: Test failed: Release returned 1 See https://test.winehq.org/data/patterns.html#mf:mf Despite the line number changes these refcount failures happen in the same location. There have been some commits on 2023-04-10 and 11 so it looks like they may have moved the failure(s) from Windows to Wine (which would be progress), which is why I'm only mentioning Wine in the summary. -- 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 55148] New: Sometime application works perfectly and sometime it doesn't function properly (VB6 Application)
by WineHQ Bugzilla 27 Jun '23

27 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55148 Bug ID: 55148 Summary: Sometime application works perfectly and sometime it doesn't function properly (VB6 Application) Product: Wine Version: 8.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: amits.enjay(a)gmail.com Distribution: --- The installation of the application has been successfully completed in a 32-bit wineprefix using winetricks components. However, when I start or run the application, it sometimes works perfectly, but other times it doesn't function properly. Example:- --> When I register a user in the registration form, an API is called to send an OTP and verify the user.This sometime works and sometime it crashes the application --> Sometimes, the application functions perfectly, but after certain processes like user registration, creating user data, or submitting a form, the application crashes or may not work properly. Your assistance will be valued. -- 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 55145] New: widl crashes when interface is empty
by WineHQ Bugzilla 26 Jun '23

26 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55145 Bug ID: 55145 Summary: widl crashes when interface is empty Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 74712 --> https://bugs.winehq.org/attachment.cgi?id=74712 test.idl See testcase -- 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 0

[Bug 55074] New: Multiple apps fail to show anything after launch (Steam, Ubisoft Connect)
by WineHQ Bugzilla 26 Jun '23

26 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55074 Bug ID: 55074 Summary: Multiple apps fail to show anything after launch (Steam, Ubisoft Connect) Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Regression SHA1: c2c9112bf8896d49a6af1ca1f73e563c5a7f909c Distribution: --- Just zombie process. Coming to previous commit makes them work again. -- 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 29

[Bug 53928] New: ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -1
by WineHQ Bugzilla 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=53928 Bug ID: 53928 Summary: ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -1 Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alandms123(a)gmail.com Distribution: --- Created attachment 73486 --> https://bugs.winehq.org/attachment.cgi?id=73486 wine.log OS: Arch Linux x86_64 Kernel: 6.0.8-arch1-1 nvidia drivers: 520.56.06-2 mesa: 22.2.3-1 WM: dwm cpu: i5-11400h dgpu: rtx 3050 laptop igpu: intel uhd graphics (tgl gt1) The only application I tried with was The Elder Scrolls Online. Basically with these versions of wine (6.16, 6.23, 7.0, 7.19, 7.20, 7.21) when using PRIME render offload (prime-run or setting the environment variables manually) a black screen will appear, killing the game processes or wine will not make X display anything again, the only way is switching to another tty and killing X from there. I did tried bisecting for a regression but couldn't go far, for example compiling 6.1-6.23 fails with something like conflicting types for ‘ldap_connect’. Also as I don't know which debug channel to provide the debug details the logs doesn't say much besides: 016c:err:system:ChangeDisplaySettingsExW Changing L"\\\\.\\DISPLAY1" display settings returned -1. The only versions which works, are the wine-tkg (https://github.com/Frogging-Family/wine-tkg-git/releases/tag/7.6.r12.g51472…) and ge-proton (https://github.com/GloriousEggroll/wine-ge-custom/releases/tag/GE-Proton7-33) If I can figure how to solve the conflicting types for ‘ldap_connect’, I'll try bisecting. -- 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 55046] New: ALT-TAB broken with virtual desktop and capture mouse (regression: 8.9 -> 8.10)
by WineHQ Bugzilla 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55046 Bug ID: 55046 Summary: ALT-TAB broken with virtual desktop and capture mouse (regression: 8.9 -> 8.10) Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de Distribution: --- This commit broke ALT-TAB out fullscreen windows when running with virtual desktop and "Automatically capture the mouse in full-screen windows" both turned on. https://gitlab.winehq.org/wine/wine/-/commit/47e208e9ec91b3ac0aca7042778ff7… The mouse will stay attached to the Wine virtual desktop window. ALT-TAB actually brings windows into foreground and into focus. But you can not move the mouse out of the virtual desktop window. And even when another window is directly overlapping the virtual desktop window, clicks in the other window will not be registered. Tested with SuperTuxKart or Diablo IV. https://supertuxkart.net/ Specifically this deleted line was needed for ALT-TAB to work correctly. if (ret) user_driver->pClipCursor( &new_rect, FALSE ); -- 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 55132] New: Shoujo-tachi wa Kouya o Mezasu: (Japanese) text does not display in settings utility
by WineHQ Bugzilla 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55132 Bug ID: 55132 Summary: Shoujo-tachi wa Kouya o Mezasu: (Japanese) text does not display in settings utility Product: Wine Version: 8.10 Hardware: x86-64 URL: http://minatosoft.com/koya/download/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pernegger(a)gmail.com Distribution: --- Created attachment 74685 --> https://bugs.winehq.org/attachment.cgi?id=74685 wine 8.10 terminal output Note: The trial version is free to download, see URL. Any of the mirrors / DOWNLOAD links will do. No need to install, just run from the lower-level directory. The settings utility--run Launcher.exe, select the middle option in the top row--is missing most of the Japanese text in the UI. All the elements that look a bit like tabs should be labelled. It seems to work if the label is in Latin letters, but Japanese is broken. See screenshots. The tooltips that appear at the bottom work fine as well. Setting LANG/LC_ALL to ja_JP.UTF-8 doesn't help. Terminal output is attached but unhelpful. Since it's so quick and easy to reproduce it's probably quicker if someone who knows what they're doing gives it a quick whirl anyway. -- 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 37166] New: Multiple apps fail to detect removable (USB) disk devices (PNP device manager '{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}' device class GUID registry data missing)(TomTom, iTunes, Rufus)
by wine-bugs＠winehq.org 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37166 Bug ID: 37166 Summary: Multiple apps fail to detect removable (USB) disk devices (PNP device manager '{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}' device class GUID registry data missing)(TomTom, iTunes, Rufus) Product: Wine Version: 1.7.25 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, continuation of bug 7711 and potentially others to avoid them being recycled over and over again. GUID '{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}' -> GUID_DEVINTERFACE_DISK MSDN: http://msdn.microsoft.com/en-us/library/windows/hardware/ff545824%28v=vs.85… Additionally the apps usually expect GUID '{F18A0E88-C30C-11D0-8815-00A0C906BED8}' class too -> GUID_DEVINTERFACE_USB_HUB http://msdn.microsoft.com/en-us/library/windows/hardware/ff545982%28v=vs.85…: Example trace log with 'Rufus': --- snip --- $ WINEDEBUG=+tid,+seh,+relay,+setupapi wine ./rufus-1.4.10.exe >>log.txt 2>&1 ... 0023:Call setupapi.SetupDiGetClassDevsA(004448fc,00000000,00000000,00000012) ret=0040ef60 0023:trace:setupapi:SetupDiGetClassDevsExW {f18a0e88-c30c-11d0-8815-00a0c906bed8} (null) (nil) 0x00000012 (nil) (null) (nil) 0023:warn:setupapi:SetupDiGetClassDevsExW unsupported flags 00000002 0023:trace:setupapi:SetupDiCreateDeviceInfoListExW {f18a0e88-c30c-11d0-8815-00a0c906bed8} (nil) (null) (nil) ... 0023:Call advapi32.RegOpenKeyExW(80000002,7e2e3bc0 L"System\\CurrentControlSet\\Control\\DeviceClasses",00000000,00020019,0077e944) ret=7e2bf207 0023:Ret advapi32.RegOpenKeyExW() retval=00000002 ret=7e2bf207 0023:trace:setupapi:SETUPDI_EnumerateInterfaces 0x1e2408, {f18a0e88-c30c-11d0-8815-00a0c906bed8}, (null), 00000012 ... 0023:Ret setupapi.SetupDiGetClassDevsA() retval=001e2408 ret=0040ef60 ... 0023:Call setupapi.SetupDiEnumDeviceInfo(001e2408,00000000,0077ec91) ret=0040efd3 0023:trace:setupapi:SetupDiEnumDeviceInfo 0x1e2408 0 0x77ec91 0023:Ret setupapi.SetupDiEnumDeviceInfo() retval=00000000 ret=0040efd3 0023:Call setupapi.SetupDiDestroyDeviceInfoList(001e2408) ret=0040ef91 0023:trace:setupapi:SetupDiDestroyDeviceInfoList 0x1e2408 ... 0023:Ret setupapi.SetupDiDestroyDeviceInfoList() retval=00000001 ret=0040ef91 ... 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec24,004448b2 "USBSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec24 "USBSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec28,004448ba "UASPSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec28 "UASPSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec2c,004448c3 "VUSBSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec2c "VUSBSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.CM_Get_Device_ID_List_SizeA(0077ec30,004448cc "ETRONSTOR",00000002) ret=0040f260 0023:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0x77ec30 "ETRONSTOR" 0x00000002: stub 0023:Ret setupapi.CM_Get_Device_ID_List_SizeA() retval=00000000 ret=0040f260 0023:Call setupapi.SetupDiGetClassDevsA(0044490c,00000000,00000000,00000012) ret=0040f350 0023:trace:setupapi:SetupDiGetClassDevsExW {53f56307-b6bf-11d0-94f2-00a0c91efb8b} (null) (nil) 0x00000012 (nil) (null) (nil) 0023:warn:setupapi:SetupDiGetClassDevsExW unsupported flags 00000002 0023:trace:setupapi:SetupDiCreateDeviceInfoListExW {53f56307-b6bf-11d0-94f2-00a0c91efb8b} (nil) (null) (nil) ... 0023:Call advapi32.RegOpenKeyExW(80000002,7e2e3bc0 L"System\\CurrentControlSet\\Control\\DeviceClasses",00000000,00020019,0077e944) ret=7e2bf207 0023:Ret advapi32.RegOpenKeyExW() retval=00000002 ret=7e2bf207 0023:trace:setupapi:SETUPDI_EnumerateInterfaces 0x1e2408, {53f56307-b6bf-11d0-94f2-00a0c91efb8b}, (null), 00000012 ... 0023:Ret setupapi.SetupDiGetClassDevsA() retval=001e2408 ret=0040f350 0023:Call setupapi.SetupDiEnumDeviceInfo(001e2408,00000000,0077ec91) ret=0040f3c2 0023:trace:setupapi:SetupDiEnumDeviceInfo 0x1e2408 0 0x77ec91 0023:Ret setupapi.SetupDiEnumDeviceInfo() retval=00000000 ret=0040f3c2 0023:Call setupapi.SetupDiDestroyDeviceInfoList(001e2408) ret=004103c6 0023:trace:setupapi:SetupDiDestroyDeviceInfoList 0x1e2408 ... 0023:Ret setupapi.SetupDiDestroyDeviceInfoList() retval=00000001 ret=004103c6 ... 0023:Call KERNEL32.OutputDebugStringA(004640d4 "0 devices found\r\n") ret=004164fb ... 0023:Ret KERNEL32.OutputDebugStringA() retval=00000000 ret=004164fb ... --- snip --- $ sha1sum rufus-1.4.10.exe 031309c159429544a4e8bec0373d474c8e705c3e rufus-1.4.10.exe $ du -sh rufus-1.4.10.exe 1.4M rufus-1.4.10.exe $ wine --version wine-1.7.25 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 21

[Bug 34178] New: MiKTeX 2.9 (32-bit) fails to install
by wine-bugs＠winehq.org 25 Jun '23

25 Jun '23

http://bugs.winehq.org/show_bug.cgi?id=34178 Bug #: 34178 Summary: MiKTeX 2.9 (32-bit) fails to install Product: Wine Version: 1.6 Platform: x86-64 URL: http://miktex.org/download OS/Version: Linux Status: NEW Keywords: download, Installer, source Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Blocks: 34172 Classification: Unclassified Noticed this while looking at bug 34172. I tried the 32-bit version, and get a separate, but potentially related issue. Download the installer from http://miktex.org/download Install as normal. Eventually it gives an error during install: ========== The operation could not be completed for the following reason: The operation failed for some reason. Details: C:\Program Files\MiKTeX 2.90\miktex/bin\initexmf.exe ========== austin@aw25 ~ $ sha1sum basic-miktex-2.9.4813.exe e8647f57fe866c00119ca8938785cacfaa5ca826 basic-miktex-2.9.4813.exe austin@aw25 ~ $ du -h basic-miktex-2.9.4813.exe 155M basic-miktex-2.9.4813.exe wine-1.6-178-g7944ca4 -- 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 9

[Bug 41647] New: TFM Music Maker controls are not usable
by wine-bugs＠winehq.org 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=41647 Bug ID: 41647 Summary: TFM Music Maker controls are not usable Product: Wine Version: 1.9.22 Hardware: x86 URL: http://sega4ever.power-heberg.com/Download/tfmmaker152 .rar OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: notasas(a)gmail.com Distribution: --- After starting the program, click "Instruments" tab and try to adjust any of the knobs. Nothing useful noticed in the terminal output. Just a guess it's an issue message handling, so selected user32 component. Tested to be broken on vanilla wine-1.9.22, wine-1.9.22 (Staging) and wine-1.6.2. Works correctly on real Windows 7 and 8.1. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 5

[Bug 33326] New: Sound problem with Game Maker 8.0 games
by wine-bugs＠winehq.org 25 Jun '23

25 Jun '23

http://bugs.winehq.org/show_bug.cgi?id=33326 Bug #: 33326 Summary: Sound problem with Game Maker 8.0 games Product: Wine Version: 1.5.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: georgiev_1994(a)abv.bg Classification: Unclassified When Im starting a game created from Game Maker 8.0 Po it's sound does not start. This is happening with every game Im trying to run. This is caused maybe because of the sound system of Game Maker built games. Here I will give a link just to one game which runs just perfect with Windows OS but not perfect at all with Wine. http://sandbox.yoyogames.com/games/205913/download -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 21

[Bug 55133] New: Shoujo-tachi wa Kouya o Mezasu: crashes on new game
by WineHQ Bugzilla 25 Jun '23

25 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55133 Bug ID: 55133 Summary: Shoujo-tachi wa Kouya o Mezasu: crashes on new game Product: Wine Version: 8.10 Hardware: x86-64 URL: http://minatosoft.com/koya/download/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pernegger(a)gmail.com Distribution: --- Created attachment 74688 --> https://bugs.winehq.org/attachment.cgi?id=74688 wine 8.10 terminal output Note: The trial version is free to download, see URL. Any of the mirrors / DOWNLOAD links will do. No need t install, just run from the low-level directory. The game will crash at a black screen immediately after selecting new game from the main menu. Even if I ctrl-c the process on the terminal, getting rid of the game window requires wineserver -k. Different WINE versions and/or using DXVK may result in different log output and symptoms (i.e. hang instead of crash). Since I've no idea where to start I was hoping someone who does could have a quick look at this, narrow it down a bit at least. -- 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 40119] New: Irfanview 4.x: selection cursor is not correctly aligned
by wine-bugs＠winehq.org 24 Jun '23

24 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=40119 Bug ID: 40119 Summary: Irfanview 4.x: selection cursor is not correctly aligned Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Ulf.Zibis(a)gmx.de Distribution: --- - select an area in an image - correct the selection by dragging the left selection border to another position --> the double-ended arrow cursor ofen is not correctly aligned with the selection border I guess this happens, when the image is zoomed. -- 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 9

[Bug 55113] New: Spam on gitlab
by WineHQ Bugzilla 24 Jun '23

24 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55113 Bug ID: 55113 Summary: Spam on gitlab Product: WineHQ Gitlab Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gitlab-unknown Assignee: wine-bugs(a)winehq.org Reporter: jkfloris(a)dds.nl Distribution: --- Are there any rules or etiquette for gitlab.winehq.org? Some forks contain links to spam or questionable sites. For example: https://gitlab.winehq.org/sapathelect/wine/-/tree/master/loader https://gitlab.winehq.org/quogigrosji/wine/-/tree/master/nls https://gitlab.winehq.org/maesolbevea/vkd3d https://gitlab.winehq.org/biobitata/vkd3d Google finds much more: https://www.google.com/search?q="*.md"+site%3Agitlab.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 2

[Bug 55129] New: Boost throws c++ exception when creating shared memory
by WineHQ Bugzilla 24 Jun '23

24 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55129 Bug ID: 55129 Summary: Boost throws c++ exception when creating shared memory Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: dlehman25(a)gmail.com Distribution: --- Created attachment 74681 --> https://bugs.winehq.org/attachment.cgi?id=74681 simple c++ repro case boost uses 2 methods to fetch the boot time to build a path for shared memory. code path is chosen with a #define the 2 methods are: - registry key (default): - BootId and optionally additionally HybridBootAnimationTime - https://github.com/boostorg/interprocess/blob/boost-1.82.0/include/boost/in… - creates a path like: C:/ProgramData/boost_interprocess/01000000/crash - Eventlog - fetches record for event log start - https://github.com/boostorg/interprocess/blob/boost-1.82.0/include/boost/in… - creates a path like: C:/ProgramData/boost_interprocess/1687093260/crash - the event log timestamp is always moments after boot on physical and virtual machines i have access to, although many testbot vms seem to have boot records after the event log start - not sure what the 24 bytes at DataOffset are - seems like overkill to fully implement the event log feature, which generally doesn't seem useful on wine, just for this case it throws a c++ exception if either method fails https://github.com/boostorg/interprocess/blob/boost-1.82.0/include/boost/in… pull request to follow -- 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 55038] New: Please add trixie Debian release to Wine repos
by WineHQ Bugzilla 24 Jun '23

24 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55038 Bug ID: 55038 Summary: Please add trixie Debian release to Wine repos Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Please add trixie distro to the Debian repos for Wine, since Debian trixie was just released. Thanks! -- 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 55125] New: The 64-bit dinput:hotplug sometimes gets timeouts on Windows 10
by WineHQ Bugzilla 24 Jun '23

24 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55125 Bug ID: 55125 Summary: The 64-bit dinput:hotplug sometimes gets timeouts on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit dinput:hotplug sometimes gets timeouts on Windows 10 : hid.c:725: Test failed: 0x800: WaitForSingleObject returned 0x102 or hid.c:725: Test failed: WaitForSingleObject returned 0x102 and/or hotplug.c:400: Test failed: MsgWaitForMultipleObjects returned 0x102 See https://test.winehq.org/data/patterns.html#dinput:hotplug Where 0x102 == WAIT_TIMEOUT These failures only happen on w1064-tsign which is a test configuration with test signing enabled. Furthermore only the 64-bit version has these issues. The oldest instance goes back to 2022-12-20 and these failures have happened almost 3 times per month since. -- 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 53682] New: wineboot shows "user_check_not_lock BUG: holding USER lock" on aarch64 since wine-7.14
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=53682 Bug ID: 53682 Summary: wineboot shows "user_check_not_lock BUG: holding USER lock" on aarch64 since wine-7.14 Product: Wine Version: 7.14 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: PuetzKevinA(a)JohnDeere.com Distribution: --- I recently updated our builds to past wine-7.0, and began encountering a wineboot failure on aarch64 > 0040:err:system:user_check_not_lock BUG: holding USER lock(64) > s\system32\rundll32.exe: /home/yukondev/workspace/wine/dlls/win32u/sysparams.c:400: user_check_not_lock: Assertion `0' failed. > 0040:err:seh:call_function_handlers invalid frame 21f410 (0000000000022000-0000000000120000) > 0040:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. After some bisecting, I narrowed this down to being a regression between 7.13 and 7.14, and then further narrowed it to https://source.winehq.org/git/wine.git/commit/d50112b4b6e82782d3924a8dbd443… Somehow the call to KeUserModeCallback( NtUserLoadSysMenu,... ) at https://gitlab.winehq.org/wine/wine/-/blob/d50112b4b6e82782d3924a8dbd443f82… does not properly return. I think that commit is mostly a false lead though, the translation of syscall NtUserCreateWindowEx to a syscall just exposed a latent bug in KeUserModeCallback/__wine_syscall_dispatcher on aarch64, since having NtUserCreateWindowEx be a syscall means KeUserModeCallback can no longer use its "if we have no syscall frame, call the callback directly" simple path https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/unix/signal_ar… What seems to be actually at fault is that, inside of User32LoadSysMenu (the actual function invoked by KeUserModeCallback), is a call to NtUserCreateMenu - which is *also* a syscall. This call doesn't crash, and in fact all of User32LoadSysMenu runs to completion. But when it goes through __wine_syscall_dispatcher, the stack pointer is restored to be `$sp = arm64_thread_data()->syscall_frame` https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/unix/signal_ar… - i.e. it points to &callback_frame, back on the stack of KeUserModeCallback. And this is *not* the bottom of the stack; there's compiler-generated prologue/epilogue to restore various non-volatile registers. 0x0000ffffaa0247b4 <KeUserModeCallback+0>: sub sp, sp, #0x450 0x0000ffffaa0247b8 <KeUserModeCallback+4>: stp x29, x30, [sp] 0x0000ffffaa0247bc <KeUserModeCallback+8>: mov x29, sp 0x0000ffffaa0247c0 <KeUserModeCallback+12>: stp x19, x20, [sp, #16] 0x0000ffffaa0247c4 <KeUserModeCallback+16>: stp x21, x22, [sp, #32] 0x0000ffffaa0247c8 <KeUserModeCallback+20>: str w0, [sp, #56] 0x0000ffffaa0247cc <KeUserModeCallback+24>: str x1, [sp, #48] 0x0000ffffaa0247d0 <KeUserModeCallback+28>: str w2, [sp, #60] 0x0000ffffaa0247d4 <KeUserModeCallback+32>: mov x21, x3 0x0000ffffaa0247d8 <KeUserModeCallback+36>: mov x20, x4 0x0000ffffaa0247dc <KeUserModeCallback+40>: add x19, sp, #0x40 // x19=&callback_frame So any code that runs inside this syscall that uses the first 0x40 bytes of stack is trampling these variables in the frame of KeUserModeCallback. Eventually User32LoadSysMenu returns back into KiUserCallbackDispatcher, which passes it into NtCallbackReturn, which does a __wine_longjmp back into the KeUserModeCallback,and we exit from the __wine_setjmp for the second time (returning 0) and get to `return callback_frame.status` https://gitlab.winehq.org/wine/wine/-/blob/wine-7.17/dlls/ntdll/unix/signal…. But then the epilogue starts peeling off the stack => 0x0000ffffaa024864 <+176>: ldr w0, [sp, #1088] 0x0000ffffaa024868 <+180>: ldp x19, x20, [sp, #16] 0x0000ffffaa02486c <+184>: ldp x21, x22, [sp, #32] 0x0000ffffaa024870 <+188>: ldp x29, x30, [sp] 0x0000ffffaa024874 <+192>: add sp, sp, #0x450 0x0000ffffaa024878 <+196>: ret and the link register $x30 = (void *) 0xffffaa024984 <NtCallbackReturn+104>, rather than 0xffffa8f0ccdc <copy_sys_popup+44> as it was when it was pushed in the prologue. It's overwritten several times along the way, but I don't think any of these call sites are at fault; they are just writing to what they think is their own stack frame, unaware that __wine_syscall_dispatcher adjusted $sp to too-high a value and they are overwriting space that belongs to KeUserModeCallback. The specific places that overwrote this entry on the stack were #0 0x0000ffffa8f37a48 in NtUserCallOneParam (arg=0, code=2) at /home/yukondev/workspace/wine/dlls/win32u/sysparams.c:5357 #1 0x0000ffffaa022cf0 in __wine_syscall_dispatcher () from /opt/wine/bin/../lib/wine/aarch64-unix/ntdll.so which set it to 0xffffaa022cf0 <__wine_syscall_dispatcher+272> #0 insert_menu_item (ret_pos=0x21f538, flags=1024, id=4294967295, handle=0x10042) at /home/yukondev/workspace/wine/dlls/win32u/menu.c:438 #1 NtUserThunkedMenuItemInfo (handle=0x10042, pos=4294967295, flags=1024, method=1, info=0x11f528 <opengl_func_names+680>, str=<optimized out>) at /home/yukondev/workspace/wine/dlls/win32u/menu.c:1297 #2 0x0000ffffaa022cf0 in __wine_syscall_dispatcher () from /opt/wine/bin/../lib/wine/aarch64-unix/ntdll.so which set it to NULL and 0x0000ffffaa023a0c in NtCurrentTeb () at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:1449 1449 { (gdb) bt #0 0x0000ffffaa023a0c in NtCurrentTeb () at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:1449 #1 0x0000ffffaa02493c in ntdll_get_thread_data () at /home/yukondev/workspace/wine/dlls/ntdll/unix/unix_private.h:70 #2 arm64_thread_data () at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:163 #3 NtCallbackReturn (ret_ptr=0x0, ret_len=0, status=65602) at /home/yukondev/workspace/wine/dlls/ntdll/unix/signal_arm64.c:784 #4 0x0000ffffaa022cf0 in __wine_syscall_dispatcher () from /opt/wine/bin/../lib/wine/aarch64-unix/ntdll.so which set it to 0xffffaa02493c <NtCallbackReturn+32>, and then 0xffffaa024978 <NtCallbackReturn+92> , then 0xffffaa024984 <NtCallbackReturn+104> The same sort of thing happens in the x86_64 dispatcher, but there it turns out to be pretty harmless. The key difference is that the function prologue on x86_64 used `push` instructions, and did so prior to the `sub` where it allocated space for locals, so the things popped by the epilogue ended up above callback_frame, rather than below it, and so are not smashed. 0x00007fd17b6dc1d2 <+0>: push %rbp 0x00007fd17b6dc1d3 <+1>: mov %rsp,%rbp 0x00007fd17b6dc1d6 <+4>: push %r14 0x00007fd17b6dc1d8 <+6>: push %r13 0x00007fd17b6dc1da <+8>: push %r12 0x00007fd17b6dc1dc <+10>: push %rdi 0x00007fd17b6dc1dd <+11>: push %rsi 0x00007fd17b6dc1de <+12>: push %rbx 0x00007fd17b6dc1df <+13>: sub $0xa0,%rsp 0x00007fd17b6dc1e6 <+20>: and $0xffffffffffffffc0,%rsp 0x00007fd17b6dc1ea <+24>: sub $0x560,%rsp There is still a 32-byte gap between the $rsp of KeUserModeCallback and &current_frame that is briefly at risk, but 1. This seems to be the register parameter area of the Windows x64 ABI, which is actually volatile space that belongs to the callee even though it's allocated by the caller, so the compiler is not expecting it to survive across function calls (in this case __wine_syscall_dispatcher_return). https://docs.microsoft.com/en-us/cpp/build/stack-usage?view=msvc-170 discusses how this "contains at least 4 entries", i.e. 32 bytes: https://eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64 2. It doesn't actually get smashed, because __wine_syscall_dispatcher subtracts 0x20 from the restored $rsp before actually making the syscall (https://gitlab.winehq.org/wine/wine/-/blob/d50112b4b6e82782d3924a8dbd443f82…). Which is presumably since the SysV ABI does *not* make any such reservation, and so __wine_syscall_dispatcher needs to do so to be following the ms_abi. So together, these mean that on x86_64, it would be OK if __wine_syscall_dispatcher used these 32 bytes between the correct $rsp of KeUserModeCallback and frame->syscall_table (though it doesn't seem to). And the eventual callee gets a $rsp that does *not* overlap with KeUserModeCallback (even though it would be legal for it to do so). I don't know that we have any actual guarantee that callback_frame will be at the bottom, but in practice it seems to be. But on aarch64, there's important stuff below callback_frame, so this doesn't work out. -- 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 29

[Bug 55016] New: xaudio2_8:xaudio2 - test_simple_streaming() crashes on Windows 8+
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55016 Bug ID: 55016 Summary: xaudio2_8:xaudio2 - test_simple_streaming() crashes on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com xaudio2_8:xaudio2 - test_simple_streaming() crashes on Windows 8+: xaudio2.c:339: Test failed: Got hr 0x80004002. xaudio2.c:339: this is the last test seen before the exception 13dc:xaudio2: unhandled exception c0000005 at 00402D6A See https://test.winehq.org/data/patterns.html#xaudio2_8:xaudio2 A bisect shows that the failures started with this commit: commit 14c44d0b0a2fc0ead5bc75615864ff850a44c4d5 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Mon Apr 24 16:59:08 2023 -0500 xaudio2: Use the preprocessor to modify definitions in xaudio2.idl and xaudio2fx.idl. Instead of including the IDLs directly, define a local IDL that #includes them, with XAUDIO2_VER defined, and include that generated header. Get rid of compat.c, and use XAUDIO2_VER to modify the code in the other source files. Build the tests for both xaudio2_7 and xaudio2_8 using PARENTSRC, and use XAUDIO2_VER to select between them. This mirrors the approach taken for d3dcompiler, and makes it easier to test more xaudio2 versions in the future. -- 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 55013] New: user32:monitor - test_EnumDisplayMonitors() sometimes fails on Linux
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55013 Bug ID: 55013 Summary: user32:monitor - test_EnumDisplayMonitors() sometimes fails on Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:monitor - test_EnumDisplayMonitors() sometimes fails on Linux: monitor.c:1613: Test failed: SetThreadDesktop failed, error 0xaa. monitor.c:1614: Test failed: Expected 00000014, got 00000140. See https://test.winehq.org/data/patterns.html#user32:monitor A bisect shows that the failures started with the commit below: commit 5bdbbee6f4a874159f2e527f39f071547c513ee4 Author: Rémi Bernon <rbernon(a)codeweavers.com> AuthorDate: Fri May 26 19:50:57 2023 +0200 winex11: Rely on win32u to reset clipping on display mode change. -- 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 54980] New: Times font missing in font list (several programs)
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54980 Bug ID: 54980 Summary: Times font missing in font list (several programs) Product: Wine Version: 8.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineps.drv Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- After this commit, the font "Times" (one of the Postscript base fonts) is missing: a6cb10bba2d05ceca6ba5b1411c450d38defdbb4 is the first bad commit commit a6cb10bba2d05ceca6ba5b1411c450d38defdbb4 Author: Piotr Caban <piotr(a)codeweavers.com> Date: Mon May 15 17:34:23 2023 +0200 wineps: Don't pass PRINTERINFO structure to unixlib. dlls/wineps.drv/init.c | 5 +- dlls/wineps.drv/unixlib.c | 310 +++++----------------------------------------- dlls/wineps.drv/unixlib.h | 5 +- 3 files changed, 35 insertions(+), 285 deletions(-) This happens in several programs (Framemaker 8, Office 2007). The result is, that in documents which use this font it is replaced (in most cases by "Times New Roman") but this does not work always and not good for font variants like "Times Bold". -- 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 11

[Bug 54442] New: experimental wow64 mode: doesn't show some graphical windows
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54442 Bug ID: 54442 Summary: experimental wow64 mode: doesn't show some graphical windows Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru Distribution: --- Created attachment 73990 --> https://bugs.winehq.org/attachment.cgi?id=73990 SteamSetup.png When I'm building wine with new experimental wow64 mode, it is unable to properly show or render application windows for some applications. I've tried it both on clean prefix and on existing prefix. I've tried Steam setup and Battle.net setup, both failed. With Battle.net setup I see no window, with Steam setup I see black window with some artifacts. When using multilib wine built old way, everything works as usual. Happens both with wine 8.0 and 8.1. OS: Gentoo Linux amd64 (64bit) Graphics: X11 Videocard information: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K1000M/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.161.03 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile Wine build options: ./configure --with-mingw --enable-archs='i386,x86_64' --prefix=/tmp/wineinstall Default wine output: $ WINEPREFIX=/tmp/wineprefix/prefix1 /tmp/wineinstall/bin/wine /tmp/SteamSetup.exe 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0080:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0090:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 010c:err:environ:init_peb starting L"Z:\\tmp\\SteamSetup.exe" in experimental wow64 mode 010c:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 010c:fixme:imm:ImeSetActiveContext (00020046, 1): stub 010c:fixme:imm:ImmReleaseContext (00010052, 00020046): stub 0090:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub 0090:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub -- 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 54848] New: dnsapi:query - test_DnsQuery() fails on Rémi's Wine test machines
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54848 Bug ID: 54848 Summary: dnsapi:query - test_DnsQuery() fails on Rémi's Wine test machines Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dnsapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- dnsapi:query - test_DnsQuery() fails on Rémi's Wine test machines: query.c:66: Test failed: expected record name L"winehq.org", got L"." query.c:67: Test failed: expected record type 1, got 41 query.c:96: Test failed: unexpected CNAME chain See https://test.winehq.org/data/patterns.html#dnsapi:query test_DnsQuery() also has failures on the TestBot's VMs (see bug 54847) but the failures on Rémi's machines are different and not easily explained by the CDN used by winehq.org. They may instead be caused by the cloud environment these machines are running on. These failures happen in new tests that were introduced by this commit: commit 6e2efe54f17e72415b790edf6c9c1f9de5acb9f7 Author: François Gouget <fgouget(a)codeweavers.com> Date: Thu Apr 13 05:51:20 2023 +0200 dnsapi/tests: Test how DnsQuery() handles CNAMEs. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54819 -- 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 54797] New: Lunar Magic 3.33: Crashes with BadWindow unless WINEDEBUG=+all
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54797 Bug ID: 54797 Summary: Lunar Magic 3.33: Crashes with BadWindow unless WINEDEBUG=+all Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xhsdf.misc(a)googlemail.com Distribution: --- Created attachment 74294 --> https://bugs.winehq.org/attachment.cgi?id=74294 warn+all output Starting with Wine 8.4 Lunar Magic crashes on startup with X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 12 (X_ConfigureWindow) Resource id in failed request: 0x60001e8 Serial number of failed request: 600 Current serial number in output stream: 601 It works when WINEDEBUG=+all or trace+all is used, but then it runs very, very slowly. Lunar Magic can be found here: https://fusoya.eludevisibility.org/lm/program.html I'm using up-to-date Archlinux on a Ryzen 7 5700X and Radeon RX 6650 XT running Openbox. -- 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 54751] New: The 64-bit advapi32:registry breaks test_CoGetPSClsid() in ole32:compobj in Wine
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54751 Bug ID: 54751 Summary: The 64-bit advapi32:registry breaks test_CoGetPSClsid() in ole32:compobj in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit advapi32:registry breaks test_CoGetPSClsid() in ole32:compobj in Wine: compobj.c:1449: Test failed: CoGetPSClsid failed with error 0x80040155 compobj.c:1450: Test failed: got clsid {52222222-1234-1234-1234-56789abcdef0} See https://test.winehq.org/data/patterns.html#ole32:compobj A bisect shows that this started with the commit below: commit 3f82f6ff59f4024f67e2d646883cbea223fba84a Author: Sven Baars <sbaars(a)codeweavers.com> Date: Fri Mar 17 16:52:51 2023 +0100 kernelbase: Use open_key() to obtain any existing Wow6432node in create_key(). -- 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 54738] New: msi:action - The 64-bit test_register_class_info() fails in Wine
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54738 Bug ID: 54738 Summary: msi:action - The 64-bit test_register_class_info() fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- msi:action - The 64-bit test_register_class_info() fails in Wine: action.c:6025: Test failed: key not created action.c:6147: Test failed: key not created See https://test.winehq.org/data/patterns.html#msi:action -- 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 48811] New: StarCraft II fails to load in staging, crashes after trying to start a game in stable
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=48811 Bug ID: 48811 Summary: StarCraft II fails to load in staging, crashes after trying to start a game in stable Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Created attachment 66725 --> https://bugs.winehq.org/attachment.cgi?id=66725 Output occurring when the application crashes. Ever since upgrading from 5.3 to 5.4, StarCraft II has ceased working. On staging, this occurs during the loading screen. I am able to get through the Battle.net app OK, but cannot get to my login authenticating. I have tried switching to stable, but when trying to load up a game, I see the same output issue. Selected the dbghelp component because that's the line that comes up in the output at the time of the crash. -- 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 15

[Bug 55088] New: Program crashes when Common Dialog File open function is called
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55088 Bug ID: 55088 Summary: Program crashes when Common Dialog File open function is called Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: schicktmireurescheisse(a)gmail.com Distribution: --- Created attachment 74644 --> https://bugs.winehq.org/attachment.cgi?id=74644 This is the contents of the error message when the program crashes. When the open file button (the blue button with the folder icon in the upper left corner) of "Entgenderer" is clicked, the software instantly crashes. The program does not get as far to display the open file common dialog. Actually, the program is expected to show the file open dialog in order to enable the user to select a text file. The program was written by me. It is a 16 Bit NE binary (therefore, it actually does not use the comdlg32 DLL, but probably its predecessor - but this category fitted best). The sample program can be retrieved via the link https://github.com/Waldwatz/Wine-reveals-the-truth/releases/ and then the Entgenderer2.zip file has to be downloaded. The terminal output after the program has crashed is: wine: Unhandled page fault on read access to FFFFFFFF at address 00003FD6 (thread 0104), 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 7

[Bug 55055] New: Japanese IME fails to clear composition string when deleting the only remaining character
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55055 Bug ID: 55055 Summary: Japanese IME fails to clear composition string when deleting the only remaining character Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: imm32 Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Distribution: --- Created attachment 74617 --> https://bugs.winehq.org/attachment.cgi?id=74617 PoC patch Environment: Linux, LANG=ja_JP.UTF-8, ATOK X3 (XIM) Since Wine 8.9 (and possibly 8.8, but not in 8.7), if XIM input results in a composition string being reduced to zero length, the previous composition string remains displayed until further input. For example, using Japanese: 1) Press 'A' -> composition string "あ" -> program displays "あ" 2) Press backspace -> composition string empty -> program still displays "あ" 3) Press 'I' -> composition string "I" -> program displays "い" In step 2, the program should no longer display a composition string, but the "あ" from step 1 remains displayed until further input in step 3 (at which point the displayed composition string is correct again). I first observed this in Final Fantasy XIV, but it reproduces in Notepad as well. Changing dlls/imm32/ime.c:ImeToAsciiEx() to send WM_IME_ENDCOMPOSITION when compstr->dwCompStrLen is zero (see attached patch) seems to fix the bug without any side effects in FFXIV and Notepad, but I have no idea what other effects this might have, or if there needs to be some sort of deeper state tracking for a proper fix. -- 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 55050] New: Wine stucks when creating prefix
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55050 Bug ID: 55050 Summary: Wine stucks when creating prefix Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: julliard(a)winehq.org Regression SHA1: cc2cfb9b792bee681b96c5859084fd6d4d0bbed7 Distribution: --- wine: created the configuration directory '/home/andrey/.wine' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:err:wineboot:start_services_process Couldn't start services.exe: error 998 -- 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 54993] New: Framemaker 8 crashes in internal search operation
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54993 Bug ID: 54993 Summary: Framemaker 8 crashes in internal search operation Product: Wine Version: 8.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineps.drv Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Framemaker 8 crashes in an search operation (which seems to be not related to printing) with an internal error which in the past was a sign of memory corruption. A Bisect shows this commit: a6cb10bba2d05ceca6ba5b1411c450d38defdbb4 is the first bad commit commit a6cb10bba2d05ceca6ba5b1411c450d38defdbb4 Author: Piotr Caban <piotr(a)codeweavers.com> Date: Mon May 15 17:34:23 2023 +0200 wineps: Don't pass PRINTERINFO structure to unixlib. dlls/wineps.drv/init.c | 5 +- dlls/wineps.drv/unixlib.c | 310 +++++----------------------------------------- dlls/wineps.drv/unixlib.h | 5 +- 3 files changed, 35 insertions(+), 285 deletions(-) Please tell me when you need more info (log file for which component?). I understand thats its not easy to narrow this bug from the given information. Thanks! -- 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 26

[Bug 54742] New: The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54742 Bug ID: 54742 Summary: The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine. To reproduce run the following commands: $ rm -rf ~/.wine # start from a fresh wineprefix $ ./wow64/wine64 wow64/dlls/advapi32/tests/x86_64-windows/advapi32_test.exe registry 2>&1 | grep -E '(Test failed|tests executed)' 0020:registry: 6309 tests executed (156 marked as todo, 0 as flaky, 0 failures), 2 skipped. $ ./wow32/wine wow32/dlls/advapi32/tests/i386-windows/advapi32_test.exe registry 2>&1 | grep -E '(Test failed|tests executed)' registry.c:2837: Test failed: RegOpenKeyExA failed: 2 registry.c:2842: Test failed: RegOpenKeyExA failed: 2 registry.c:2861: Test failed: 00000000: wrong value 32/64 registry.c:2863: Test failed: 00000200: wrong value 32/64 registry.c:2868: Test failed: 00000000: wrong value 64/0 registry.c:2869: Test failed: 00000100: wrong value 64/0 registry.c:2870: Test failed: 00000200: wrong value 64/0 registry.c:3168: Test failed: RegOpenKeyExA failed: 2 registry.c:3174: Test failed: RegOpenKeyExA failed: 2 registry.c:3180: Test failed: RegOpenKeyExA failed: 2 registry.c:3206: Test failed: found equals 0 registry.c:3208: Test failed: found equals 0 registry.c:3210: Test failed: found equals 0 registry.c:3212: Test failed: found equals 1 registry.c:3214: Test failed: wrong number of subkeys: 10 registry.c:3216: Test failed: found equals 1 registry.c:3218: Test failed: found equals 0 registry.c:3220: Test failed: wrong number of subkeys: 10 registry.c:3222: Test failed: found equals 0 0128:registry: 7658 tests executed (74 marked as todo, 0 as flaky, 19 failures), 2 skipped. See https://test.winehq.org/data/patterns.html#advapi32:registry The reason why this failure is only visible with the fg-deb64-wow32 is because this is the only test configuration that runs the 32-bit tests in the same wineprefix as the 64-bit tests. What this shows is that advapi32:registry does not correctly cleans up after itself which has the potential for breaking any test that follows (not just 32-bit ones). -- 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 55051] New: Build regression in wine 8.10 using clang on aarch64 (error in backend: Invalid register name "x18")
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55051 Bug ID: 55051 Summary: Build regression in wine 8.10 using clang on aarch64 (error in backend: Invalid register name "x18") Product: Wine Version: 8.10 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: pierrick.bouvier(a)linaro.org Distribution: --- When compiling wine for aarch64, a build regression appeared in Wine 8.10 when using clang (any version). This is only present when performing make install, which compiles some DLL. Error is that register x18 is used, and clang reports it as an hard error. gcc reports a warning but does not produce an error (warning: call-clobbered register used for global register variable). --- Reproduction steps (from linux-aarch64, debian bookworm): # download llvm-mingw and add to PATH $ ./configure CC="clang" --without-x --without-freetype --prefix=/usr $ make # works $ make install # fails clang -c -o dlls/msvcr110/onexit.o ... fatal error: error in backend: Invalid register name "x18". ... 3. Running pass 'Function Pass Manager' on module 'dlls/msvcrt/onexit.c'. 4. Running pass 'AArch64 Instruction Selection' on function '@_register_onexit_function' --- Bisect pointed this commit: https://github.com/wine-mirror/wine/commit/56cfbf6b860b46768eeae60eef7dfe0a… include: Only enable the non-inline NtCurrentTeb() on the Unix side. This previous commit introduced register x18 for TEB on arm64 (but commit above makes it active): https://github.com/wine-mirror/wine/commit/7f088b0b1387a3b54c438b839046afad… This previous bug already discussed this topic (https://bugs.winehq.org/show_bug.cgi?id=38780) but I'm not sure what the conclusion would be. --- Compiling with CLAGS=-ffixed-x18 silences clang, but I'm not sure it's the right thing to do. gcc works only because it's a warning and not an error. -- 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 55047] New: d3d test_cursor_clipping() fails
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55047 Bug ID: 55047 Summary: d3d test_cursor_clipping() fails Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression, testcase Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: af902c188ebaf7d6dda3b628409d8c390ab410d5 Distribution: --- I can observe this on two different machines, with at least ddraw and d3d8 tests. It happens regardless of whether the virtual desktop is used. The failure looks like this: ddraw:ddraw1: ddraw1.c:14352: Test failed: SetDis.layMode failed, hr 0x80004001 d3d8:device: device.c:10815: Test failed: Adapter 0: Expect clip rect (0,0)-(640,480), got (1,1)-(639,479). It's not quite consistent, though. One machine can reproduce the ddraw1 failure pretty consistently, enough for me to be able to bisect, but the other seems to fail only intermittently. As a result I can't be 100% sure of the bisect result, but it seems to make sense. -- 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 55027] New: Microsoft Office: IME result string may get doubled when edit is done
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55027 Bug ID: 55027 Summary: Microsoft Office: IME result string may get doubled when edit is done Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: firelzrd(a)gmail.com Distribution: --- Created attachment 74582 --> https://bugs.winehq.org/attachment.cgi?id=74582 Bad and Good cases in Excel 2003 The recent (v8.x) IMM32 progress is so remarkable that CJK users may finally think of replacing Windows for using Microsoft Office. However, in Microsoft Office apps (confirmed in 2003) having done editing IME preedit text by hitting Enter key may actually put the result text doubled (see in the attached video). My analysis showed that when: WM_IME_COMPOSITION which has GCS_RESULTREADSTR & GCS_RESULTSTR flags on is sent to complete the edit, and result text is sent, Only in case the problem occurs, right after that: WM_IME_COMPOSITION which has GCS_COMPSTR & GCS_COMPATTR & GCS_RESULTSTR flags on is sent. This behavior indicates that xic_preedit_done() and xim_set_result_string() which I found in xim.c are called sometimes in a wrong order. A: XICCallback preedit_done is called xic_preedit_done is called B: keyboard.c:X11DRV_KeyEvent xim_set_result_string is called A is supposed to be called first, and then B should follow. in the good case A happens, then B happens. in the bad case B happens, then A happens. So I think this problem occurs because XIC callback and X11DRV_KeyEvent are called asynchronously. I think the solution may be: * In xim_set_result_string(), check if XIC preedit context exists, and if so, ppostpone the sending of WM_IME_COMPOSITION until next xic_preedit_done() is called or * Ignore xic_preedit_done() if xim_set_result_string() was called very recently Let me hear what you guys think. Thank you -- 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 55026] New: Expose save_period as a configurable option via winecfg
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55026 Bug ID: 55026 Summary: Expose save_period as a configurable option via winecfg Product: Wine Version: 8.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Wine dumps registry files to the disk every 30 seconds which might not be good for users of SSD/NVMe disks considering it involves completely rewriting them since they are text files, not binary databases as the real Windows registry is where updates are local and small. E.g after installing Microsoft Office the system.reg file can easily blow up to tens of megabytes and it's not that funny having this file being rewritten so often. Would be nice to have this option exposed via winecfg. -- 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 19

[Bug 55123] New: widl crashes when uuid is missing
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55123 Bug ID: 55123 Summary: widl crashes when uuid is missing Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 74678 --> https://bugs.winehq.org/attachment.cgi?id=74678 Minimal Sample See attached sample -- 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 55122] New: oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55122 Bug ID: 55122 Summary: oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11: vartest.c:1999: Test failed: 1: Call succeeded, hres = 00000000 vartest.c:2012: Test failed: 1: returned 80020005 vartest.c:2049: Test failed: 1: returned 80020005 vartest.c:2121: Test failed: 1: Call succeeded, hres = 00000000 vartest.c:2135: Test failed: 1: returned 80020005 See https://test.winehq.org/data/patterns.html#oleaut32:vartest Where 80020005 == DISP_E_TYPEMISMATCH -- 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 55121] New: wintrust:asn - test_encodeSPCPEImage() fails on Windows 11
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55121 Bug ID: 55121 Summary: wintrust:asn - test_encodeSPCPEImage() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wintrust:asn - test_encodeSPCPEImage() fails on Windows 11: asn.c:385: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:398: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:563: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:673: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:696: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:709: Test failed: CryptEncodeObjectEx failed: c0000005 See https://test.winehq.org/data/patterns.html#wintrust:asn Where c0000005 == STATUS_ACCESS_VIOLATION -- 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 53431] New: widl generates enum forward declarations in typedefs which are not valid in C++
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=53431 Bug ID: 53431 Summary: widl generates enum forward declarations in typedefs which are not valid in C++ Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: gfw.kra(a)gmail.com Distribution: --- Hi everyone, I recently discovered an issue with C++ code in headers compiled from winrt idl's using widl. It does not compile when included, when tried using mingw g++ v12.1.0. There’s seems to be issue with how enum typedefs are translated within namespaces. Example: When tried to include windows.media.speechsynthesis.h compiled from windows.media.speechsynthesis.idl in cpp file, the following output is received (compiler output shows headers from mingw, but these look the same when compiled using widl in wine). ``` /usr/x86_64-w64-mingw32/include/windows.foundation.h:90:26: error: use of enum ‘PropertyType’ without previous declaration 90 | typedef enum PropertyType PropertyType; | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.foundation.h:164:18: error: using typedef-name ‘ABI::Windows::Foundation::PropertyType’ after ‘enum’ 164 | enum PropertyType { | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.foundation.h:90:39: note: ‘ABI::Windows::Foundation::PropertyType’ has a previous declaration here 90 | typedef enum PropertyType PropertyType; | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:30: error: use of enum ‘VoiceGender’ without previous declaration 218 | typedef enum VoiceGender VoiceGender; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:476:22: error: using typedef-name ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ after ‘enum’ 476 | enum VoiceGender { | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:42: note: ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ has a previous declaration here 218 | typedef enum VoiceGender VoiceGender; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:822:30: error: using typedef-name ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ after ‘enum’ 822 | enum VoiceGender *value) = 0; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:42: note: ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ has a previous declaration here 218 | typedef enum VoiceGender VoiceGender; ``` windows.media.speechsynthesis.idl has typedef of enum VoiceGender, which is defined later. ``` namespace Windows { namespace Foundation { interface IClosable; } namespace Media { namespace SpeechSynthesis { typedef enum VoiceGender VoiceGender; ``` This is translated to following: ``` #ifdef __cplusplus namespace ABI { namespace Windows { namespace Media { namespace SpeechSynthesis { typedef enum VoiceGender VoiceGender; } } } } #else /* __cplusplus */ typedef enum __x_ABI_CWindows_CMedia_CSpeechSynthesis_CVoiceGender __x_ABI_CWindows_CMedia_CSpeechSynthesis_CVoiceGender; #endif /* __cplusplus */ ``` This typedef is not valid in C++. According to the standard, enum cannot be forward declared using typedef. This could be replaced with just simple enum declaration, but it would need to have type specifier (that goes for definition as well). Best regards. -- 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 36079] New: loader fails to build with clang -faddress=sanitize
by wine-bugs＠winehq.org 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=36079 Bug ID: 36079 Summary: loader fails to build with clang -faddress=sanitize Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48263 --> https://bugs.winehq.org/attachment.cgi?id=48263 make log I tried building wine with clang's address sanitizer enabled, which mostly worked, until the loader: make[1]: Entering directory '/home/austin/wine-gcc49-asan/loader' clang -fsanitize=address -m32 -o wine-preloader -static -nostartfiles -nodefaultlibs -Wl,-Ttext=0x7c400000 preloader.o ../libs/port/libwine_port.a /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../lib32/libpthread.a(pthread_mutex_lock.o): In function `__pthread_mutex_lock': /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:80: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:116: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:146: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:151: undefined reference to `__assert_fail' .. austin@aw25 ~/wine-gcc49-asan $ clang --version clang version 3.3 (tags/RELEASE_33/final) Target: x86_64-pc-linux-gnu Thread model: posix austin@aw25 ~/wine-gcc49-asan $ git describe wine-1.7.17-42-g24c5728 -- 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 55119] New: advapi32:security - test_process_security() fails on GitLab CI's Windows VM
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55119 Bug ID: 55119 Summary: advapi32:security - test_process_security() fails on GitLab CI's Windows VM Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:security - test_process_security() fails on GitLab CI's Windows VM: security.c:3176: Test failed: OpenProcess(PROCESS_VM_READ) should have failed security.c:3178: Test failed: OpenProcess(PROCESS_ALL_ACCESS) should have failed security.c:3209: Test failed: OpenThread(THREAD_SET_THREAD_TOKEN) should have failed See https://test.winehq.org/data/patterns.html#advapi32:security These three failures happen in both the 32- and 64-bit tests but only on gitlab-win10-21h2, the GitLab's Windows VM. -- 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 49797] New: WIDL doesn't tolerate anonymous structs within interfaces
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=49797 Bug ID: 49797 Summary: WIDL doesn't tolerate anonymous structs within interfaces Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- IDLs in Windows SDKs sometimes contain anonymous structs within interfaces. WIDL fails to compile such IDLs. -- 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 55118] New: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55118 Bug ID: 55118 Summary: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode: shlfolder.c:5512: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5513: Test failed: Failed to create window. shlfolder.c:5520: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5521: Test failed: Failed to create window. shlfolder.c:5530: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5531: Test failed: Failed to create window. shlfolder.c:5540: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5541: Test failed: Failed to create window. shlfolder.c:5550: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5551: Test failed: Failed to create window. See https://test.winehq.org/data/patterns.html#shell32:shlfolder Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. See also bug 55117 where shell32:shelldispatch has a similar issue. -- 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 55117] New: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55117 Bug ID: 55117 Summary: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode: shelldispatch.c:1025: Test failed: got 0x80040152 See https://test.winehq.org/data/patterns.html#shell32:shelldispatch Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 55116] New: services.exe:service - service_main() is missing PATHEXT in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55116 Bug ID: 55116 Summary: services.exe:service - service_main() is missing PATHEXT in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- services.exe:service - test_service() is missing PATHEXT in the new WoW mode: service.c:420: Test failed: service: did not find PATHEXT environment variable See https://test.winehq.org/data/patterns.html#services.exe:service This happens during both test_service() and test_kill_service_process(), in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. -- 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 55094] New: Memory Access Violation & Run-Time Error 7 in WINE
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55094 Bug ID: 55094 Summary: Memory Access Violation & Run-Time Error 7 in WINE Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: vikasy.enjay(a)gmail.com Distribution: --- Created attachment 74654 --> https://bugs.winehq.org/attachment.cgi?id=74654 Memory Access Violation & Run-Time Error 7 in WINE Memory Access Violation & Run-Time Error 7 in WINE: I am writing this to seek assistance regarding an issue I encountered while installing and running "Busy Accounting Software" using Wine. Despite my previous unsuccessful attempts, I was eventually able to install the software. However, I am currently facing an ongoing problem when attempting to execute the application. It consistently displays a "Runtime 7 Error and Memory Access Violation" error. Any assistance or troubleshooting steps you can provide would be greatly appreciated. Thank you for your attention to this matter. -- 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 37346] New: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP
by wine-bugs＠winehq.org 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37346 Bug ID: 37346 Summary: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lax.sunny(a)gmail.com Created attachment 49664 --> https://bugs.winehq.org/attachment.cgi?id=49664 Log created by wine on running the app , problem is with database storage and runtime functions Application named busy win very much famous accounting software tried using number of prefixes application installs smoothly when i run the app it starts up normally but crashes on adding a new company or detecting an old DATABASE -- 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 55112] New: Chip's Challenge (Steam version) only shows black screen on Nvidia dGPU (works fine on AMD iGPU)
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55112 Bug ID: 55112 Summary: Chip's Challenge (Steam version) only shows black screen on Nvidia dGPU (works fine on AMD iGPU) Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- Created attachment 74675 --> https://bugs.winehq.org/attachment.cgi?id=74675 Log when running game on Nvidia dGPU The Steam version of Chip's Challenge only shows a black screen when running on my Nvidia dGPU (RTX 3060 Mobile). The game displays fine on my AMD iGPU (Vega). Note: as this version of the game is only available on Steam, it was tested with Proton 8.0. However, due to the age and nature of the game (basic 2D win32), it is very unlikely to be hitting any Proton-specific code paths (there are no mentions of DXVK/etc in the log either.) If needed, I can try more ways to run it in stock Wine Devel, but it's 2AM and I just wanted to at least get the bug report out. -- 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 50079] New: Wine msiexec fails when building inside a windows/mac os x docker container
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50079 Bug ID: 50079 Summary: Wine msiexec fails when building inside a windows/mac os x docker container Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: spam(a)crasu.de Distribution: --- Created attachment 68535 --> https://bugs.winehq.org/attachment.cgi?id=68535 Run with winedebug=msi and strace Sample dockerfile: FROM ubuntu:20.04 RUN export DEBIAN_FRONTEND="noninteractive" \ && dpkg --add-architecture i386 \ && apt-get update \ && apt-get install -y wget winbind xvfb unzip curl jq \ && apt-get remove -y libmysqlclient21 mysql-common \ && apt autoremove -y RUN wget -nc https://dl.winehq.org/wine-builds/winehq.key && apt-key add winehq.key RUN echo 'deb https://dl.winehq.org/wine-builds/ubuntu/ focal main' > /etc/apt/sources.list.d/wine.list RUN export DEBIAN_FRONTEND="noninteractive" \ && apt-get update \ && apt-get install -o APT::Immediate-Configure=false --install-recommends -y winehq-devel RUN useradd -ms /bin/bash wineuser # Install winemono RUN wget https://dl.winehq.org/wine/wine-mono/5.1.1/wine-mono-5.1.1-x86.msi RUN WINEPREFIX=/home/wineuser/.wine su wineuser -c "wine msiexec /i wine-mono-5.1.1-x86.msi && wineserver -w" Eroor message: 0024:err:msi:ACTION_InstallFiles compressed file wasn't installed (L"bin\\libmono-2.0-x86.dll") 0024:err:msi:execute_script Execution of script 0 halted; action L"InstallFiles" returned 1603 I tried different msis (wine gecko, wine mono, ....) they all fail. After serveral tries the installation sometimes does not through an error. But the package is still not fully installed. Reference: https://github.com/Winetricks/winetricks/issues/1525 -- 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 51502] New: Civilization 3 Sound Stutters, loops, and fails (eventually)
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=51502 Bug ID: 51502 Summary: Civilization 3 Sound Stutters, loops, and fails (eventually) Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: bryan(a)varnernet.com Distribution: --- Audio on Civilization III is just not very good. Typical short sounds stutter, playback sounding badly rendered into the target buffer, loop when they shouldn't, etc. The most common problem is for the sound (all of it) to just stop, or just continuously loop a small soundfile that should have been a one-off play at the triggered point in time. Looks like the app is using dsound, along with winmm to mmioOpenA the .wav's. -- 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

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