wine-bugs

wine-bugs@winehq.org

1 participants
158776 discussions

[Bug 54610] New: fusion:asmcache - 32-bit calls to InstallAssembly(..., NULL) crash on Windows
by WineHQ Bugzilla 06 Mar '23

06 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54610 Bug ID: 54610 Summary: fusion:asmcache - 32-bit calls to InstallAssembly(..., NULL) crash on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: fusion Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com fusion:asmcache - 32-bit calls to InstallAssembly(..., NULL) crash on Windows: asmcache.c:846: this is the last test seen before the exception 19e4:asmcache: unhandled exception c0000005 at 0095C478 See https://test.winehq.org/data/patterns.html#fusion:asmcache The crash only happens in the 32-bit w11pro64 tests which represents 100% of the cases where the test actually runs: * The only VM that has the needed fusion dll is w11pro64. * The dll was installed by running the dotnetfx-1.1.exe installer [1] which is only available in 32-bit format. Thus only the 32-bit dll is available and the 64-bit test is skipped. The crash happens in the following call: hr = IAssemblyCache_InstallAssembly(cache, 0, L"wine.dll", NULL); But skipping this call just moves the crash to the next InstallAssembly() call. It's not clear whether the crash is caused by the NULL RefData pointer: the crash still happens if I pass a non-NULL but pretty empty FUSION_INSTALL_REFERENCE structure (in particular szNonCannonicalData == NULL). [1] https://wiki.winehq.org/Wine_TestBot_VMs#fusion.2C_msvcr71 -- 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 41013] New: Sourceinsight: the 'Window' menu click no response
by wine-bugs＠winehq.org 06 Mar '23

06 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=41013 Bug ID: 41013 Summary: Sourceinsight: the 'Window' menu click no response Product: Wine Version: 1.8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robert.hu(a)intel.com Distribution: --- Created attachment 55180 --> https://bugs.winehq.org/attachment.cgi?id=55180 'Window' menu list jump to top left The menu of 'Window' click has no responses. But other menu can work. My workaround is to click its adjacent menu item then arrow key to move to 'Window' menu. But even so, it appears to left top of the window. See attachment. -- 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 2

[Bug 23064] New: Sourceinsight: no response clicking menu, untill firstly right-click in main window area
by wine-bugs＠winehq.org 06 Mar '23

06 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=23064 Summary: Sourceinsight: no response clicking menu, untill firstly right-click in main window area Product: Wine Version: 1.2-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dwwwww(a)hotmail.com OS: RHEL 4 Wine, 1.2-rc2 Open sourceinsight, click the menus, no response. But it works after right click in main window area. -- 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 11

[Bug 54632] New: advapi32:registry causes scrobj:scrobj to crash when run without elevated privileges on Windows 8
by WineHQ Bugzilla 06 Mar '23

06 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54632 Bug ID: 54632 Summary: advapi32:registry causes scrobj:scrobj to crash when run without elevated privileges on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: scrobj Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry causes scrobj:scrobj to crash when run without elevated privileges on Windows 8: scrobj.c:767: Test failed: DllInstall failed: 80004005 scrobj.c:771: Test failed: RegQueryValueA failed: 2 scrobj.c:771: Test failed: Unexpected value "F", expected "WineTest object" scrobj.c:772: Test failed: RegQueryValueA failed: 2 scrobj.c:772: Test failed: Unexpected value "F", expected "*\scrobj.dll" scrobj.c:773: Test failed: RegQueryValueA failed: 2 scrobj.c:773: Test failed: Unexpected value "F", expected "WineTest.1.23" scrobj.c:774: Test failed: RegQueryValueA failed: 2 scrobj.c:774: Test failed: Unexpected value "F", expected "WineTest" scrobj.c:804: Test failed: Could not get class factory: 80040154 scrobj.c:804: this is the last test seen before the exception 0dbc:scrobj: unhandled exception c0000005 at 00403A9A See https://test.winehq.org/data/patterns.html#scrobj:scrobj This crash does not happen when running scrobj:scrobj on its own. I determined that the source of interference is advapi32:registry. It is the combination of test_reg_open_key() and test_classesroot() in registry.c that causes the crash. More specifically this call in test_classesroot(): res = RegCreateKeyExA( HKEY_LOCAL_MACHINE, "Software\\Classes\\WineTestCls", 0, NULL, REG_OPTION_NON_VOLATILE, KEY_ALL_ACCESS, NULL, &hklm, NULL ); -- 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 50281] New: fsync patch for wine 6.0-rc1 (without staging)
by WineHQ Bugzilla 06 Mar '23

06 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=50281 Bug ID: 50281 Summary: fsync patch for wine 6.0-rc1 (without staging) Product: Wine Version: 6.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: michael.scott(a)quest-arts.co.uk Distribution: --- Created attachment 68830 --> https://bugs.winehq.org/attachment.cgi?id=68830 fsync patch that applies to vanilla wine 6.0-rc1 I have created a new fsync patch that can apply directly to wine 6.0-rc1 without needing esync from staging. I have tested this patch applied to the latest wine sources (6.0-rc1) as of 7th December 2020 using Star Citizen 3.11. I have included it here for you to review for your convenience to review whether to include it in a future wine version. Current testing from myself and others in the Star Citizen LUG org when using fsync enabled wine and kernels are resulting in a much smoother experience. -- 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 27

[Bug 54631] New: msi:package causes wscript.exe:run to time out when run without elevated privileges on Windows 8
by WineHQ Bugzilla 06 Mar '23

06 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54631 Bug ID: 54631 Summary: msi:package causes wscript.exe:run to time out when run without elevated privileges on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wscript Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com msi:package causes wscript.exe:run to time out when run without elevated privileges on Windows 8: wscript.exe:run start programs/wscript/tests/run.c run.c:400: running RUN.JS test... wscript.exe:run:026c done (258) in 120s 35B See https://test.winehq.org/data/patterns.html#wscript.exe:run This timeout does not happen when running wscript.exe:run on its own. I determined that the source of interference is msi:package and that the timeout is caused by a Windows prompt: Script: C:\Users\winetest\Documents\tests\test.JS Line: 19 Error: Automation server can't create object Code: 800A01AD Source: Microsoft JScript runtime error The timeout happens when waiting for the child process in run_script_file() in run.c. That makes sense: the child process is stuck displaying the Windows prompt: WaitForSingleObject(pi.hProcess, INFINITE); And the timeout is caused by the combination of test_appsearch() and test_complocator() in package.c: remove either of those two and the timeout does not happen anymore. More specifically, if leaving test_appsearch() unmodified, any call to set_component_path() in test_complocator() triggers the timeout, because of this call: RegCreateKeyExA(HKEY_LOCAL_MACHINE, prodpath, 0, NULL, 0, access, NULL, &hkey, NULL); Note that creating the comppath key does not cause the wscript.exe:run timeout. -- 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 54604] New: improved file browser
by WineHQ Bugzilla 05 Mar '23

05 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54604 Bug ID: 54604 Summary: improved file browser Product: Wine-staging Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gizmo_1979(a)yahoo.it CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74135 --> https://bugs.winehq.org/attachment.cgi?id=74135 file browser it would be handy if the completion of the names if you type in the file name field was implemented in the file open window called by the programs as it happens in any system more modern than windows 95... -- 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 54620] New: advapi32:registry causes mshtml:htmldoc to time out when run without elevated privileges on Windows 8
by WineHQ Bugzilla 05 Mar '23

05 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54620 Bug ID: 54620 Summary: advapi32:registry causes mshtml:htmldoc to time out when run without elevated privileges on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry causes mshtml:htmldoc to time out when run without elevated privileges on Windows 8: htmldoc.c:6220: put_href L"about:replace"... htmldoc.c:6503: open... htmldoc.c:6503: open... mshtml:htmldoc:0744 done (258) in 120s 899B See https://test.winehq.org/data/patterns.html#mshtml:htmldoc This timeout does not happen when running mshtml:htmldoc on its own. I determined that the source of interference is advapi32:registry and that the timeout is caused by a UAC prompt: A website wants to open web content using this program on your computer. This program will open outside of Protected mode. Internet Explorer's Protected mode helps protect your computer. If you do not trust this website, do not open this program. Name: Microsoft Edge Publisher: Microsoft Corporation This happens in the IHTMLWindow2_open() call in test_open_window() in htmldoc.c: hres = IHTMLWindow2_open(window, url, name, NULL, VARIANT_FALSE, &new_window); So this issue is very similar to the ieframe:ie one described in bug 54613. -- 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 15480] New: Saving files in Word/Excel creates useless .lnk files
by wine-bugs＠winehq.org 04 Mar '23

04 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=15480 Summary: Saving files in Word/Excel creates useless .lnk files Product: Wine Version: 1.1.5 Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrew(a)etc.gen.nz Hi, In Word and Excel 2003 when we save files then a .lnk file is created in the same directory as the source file. These files are useless for two reasons: 1) They're in the same directory as the original .doc or .xls files which have Word and Excel associated with them respectively. 2) On a standard Debian Lenny machine running Gnome the .lnk files aren't recognised by any apps and won't cause Word or Excel to run. I've searched around the place to see if we can turn this "feature" off, but haven't found anything. Is this possible? If not, could this please be added. -- 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 31

[Bug 54141] New: console: pressing ctrl+4 in any console application terminates it
by WineHQ Bugzilla 04 Mar '23

04 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54141 Bug ID: 54141 Summary: console: pressing ctrl+4 in any console application terminates it 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: taviso(a)gmail.com Distribution: --- Reproduce: $ wine cmd.exe Z:\home\taviso> [Now press Ctrl+4] I think all of the Ctrl+Number keys don't work (oddly, except Ctrl+2), but Ctrl+4 is especially annoying because it immediately terminates the application. I was trying to use a Windows console application, but didn't have much luck because of the missing keybindings. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 53501] New: Test Drive Unlimited not working
by WineHQ Bugzilla 04 Mar '23

04 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53501 Bug ID: 53501 Summary: Test Drive Unlimited not working Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ds000001(a)outlook.de Distribution: --- Created attachment 72860 --> https://bugs.winehq.org/attachment.cgi?id=72860 Lutris and Wine Hello, I try to run Test Drive Unlimited DVD 1.66 version with Wine. My system: CPU: 3700X GPU: 6700XT RAM: 32 GB Wine: 7.15 installed through pacman and using Lutris 0.5.10.1-2 for easier management of all WINEPREFIX's WINEPREFIX: - 32 Bit and complete new - Through winecfg set as Win XP - No additional packages installed - ESync, Fsync and DXVK not enabled - Virtual window mode enabled with 1080p resolution, that way it is easier for me to see, if something happens or not - no additional modules installed with Winetricks If I try to start the game, the configured Wine desktop appears, the disc drive starts to spin and after that nothing happens. Output from "lutris -d" and enabled diagnostics for the WINEPREFIX gave me the output from tdudebug1.txt. Enabled debug with "WINEDEBUG=warn+all" and tried to start the game through the wine command. Got the log tdudebug2.txt out of this. Any ideas what I am doing 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 4

[Bug 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla 04 Mar '23

04 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=9221 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair(a)hotmail.com -- 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 54562] New: The 64-bit oleaut32:usrmarshal crashes in Wine
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54562 Bug ID: 54562 Summary: The 64-bit oleaut32:usrmarshal 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: --- The 64-bit oleaut32:usrmarshal crashes in Wine: usrmarshal.c:572: Test marked todo: Unexpected refcount 4 Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x00000062138b51). [...] Backtrace: =>0 0x00000062138b51 LPSAFEARRAY_UserUnmarshal+0xa1(pFlags=00000000009AFA10, Buffer=0000000000ABA614, ppsa=0000000000AE24A0) [Z:\home\winetest\tools\testbot\var\wine\dlls\oleaut32\usrmarshal.c:1073] in oleaut32 (0x00000000000014) 1 0x000000621394c4 VARIANT_UserUnmarshal+0x454(pFlags=00000000009AFA10, Buffer=0000000000ABA5D0, pvar=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\oleaut32\usrmarshal.c:575] in oleaut32 (0x000000009af9b0) 2 0x0000000044f9e0 in oleaut32_test (+0x4f9e0) (0x000000009af928) 3 0x0000000045110b in oleaut32_test (+0x5110b) (0x00000000ab44b5) 4 0x0000000050d92b in oleaut32_test (+0x10d92b) (0x00000000ab44b5) 5 0x0000000050d187 in oleaut32_test (+0x10d187) (0000000000000000) 6 0x0000007b6293d9 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) 7 0x00000170061143 __wine_pop_frame(entry=000000000050D120, arg=00000000003F0000) [Z:\home\winetest\tools\testbot\var\wine\include\wine\exception.h:277] in ntdll (0000000000000000) 8 0x00000170061143 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) 0x00000062138b51 LPSAFEARRAY_UserUnmarshal+0xa1 [Z:\home\winetest\tools\testbot\var\wine\dlls\oleaut32\usrmarshal.c:1073] in oleaut32: cmpw (%rcx),%ax 1073 if(*ppsa && (*ppsa)->cDims==wiresa->cDims) See https://test.winehq.org/data/patterns.html#oleaut32:usrmarshal A bisect shows that this crash started with the commit below: commit 27665f35e4da13bac1e4dd8948a65f484c9dadfa Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Sat Feb 11 09:43:30 2023 +0100 ntdll: Implement Low Fragmentation Heap frontend. This implements the reduced fragmentation from the heap frontend, by carving smaller blocks out of larger allocated blocks. The super block and each sub-block are all flagged with BLOCK_FLAG_LFH. The super-block (struct group) uses a standard struct block header, as well as a list entry to be linked in free list, and a free bit map to track free sub-blocks. Sub-blocks reference their super block through the base_offset, instead of the subheap, using the block size as radix. -- 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 54149] New: shlwapi:ordinal - test_SHFormatDateTimeA() fails on the mixed locales configuration
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54149 Bug ID: 54149 Summary: shlwapi:ordinal - test_SHFormatDateTimeA() fails on the mixed locales configuration Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shlwapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- test_SHFormatDateTimeA() fails on the mixed locales configuration: ordinal.c:1765: Test failed: expected (mercredi 14 décembre 2022), got (mercredi 14 decembre 2022) ordinal.c:1773: Test failed: expected (mercredi 14 décembre 2022), got (mercredi 14 decembre 2022) ordinal.c:1787: Test failed: expected (mercredi 14 décembre 2022) got (mercredi 14 decembre 2022) for date part ordinal.c:1801: Test failed: expected (mercredi 14 décembre 2022) got (mercredi 14 decembre 2022) for date part See https://test.winehq.org/data/patterns.html#shlwapi:ordinal All was fine until 2022-12-09. Then on the 11th I let the TestBot rebuild the snapshot [1] to ensure that Internet time synchronization would be disabled to fix random failures in other tests. And on the 12th this test started failing: the date lost its e-acute! Yet the WineTest system information shows that none of the locale settings changed, not even the code page. Before and after they are: SystemDefaultLCID 0411 UserDefaultLCID 040c ThreadLocale 0411 SystemPreferredUILanguages 0412,0409 UserDefaultUILanguage 0412 ThreadUILanguage 0412 Country 231 ACP 932 The test did not change and the binary from the 9th has the same failure. So it is some obscure Windows setting that changed for some unknown reason. Furthermore given that the code page is 932 I would expect the plain 'e' to be the more correct result. Unfortunately there is no record of what the result was before the test started failing. Is it possible for SHFormatDateTimeA() and GetDateFormatA() to use different code pages? [1] It goes like this: that VM has a 'langs' powered-off snapshot with all the locales installed. This snapshot has not changed since 2022-04-24. From this the TestBot produces the 'langs-mx-MX-live' live snapshot using LibvirtTool.pl and SetWinLocale to change the locale settings. -- 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 45756] New: Button not clickable when dpi setting changed in Office 2007 Installer
by wine-bugs＠winehq.org 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=45756 Bug ID: 45756 Summary: Button not clickable when dpi setting changed in Office 2007 Installer Product: Wine Version: 3.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- After upgrading from wine 3.14 to wine 3.15 (self-compiled, 32-bit-only) the push buttons in the office 2007 installer are no longer "clickable". When pushing them with the mouse, nothing happens. Using the keyboard to "push" the buttons works as before. Sometimes the mouse pointer is not even visible inside the installer window. This only happens when changing the screen resolution in winecfg (i.e. to 168 dpi). The windows version is set to Windows XP A bisect shows this commit as the first bad commit: commit 2068b73db5e19e1ce3b54b2a8ecb5a5b99ea19b5 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Aug 27 14:02:43 2018 +0200 user32: Process hardware messages in physical coordinates. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 10

[Bug 39113] New: SimplePC_SC.exe does not work
by wine-bugs＠winehq.org 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=39113 Bug ID: 39113 Summary: SimplePC_SC.exe does not work Product: Wine Version: unspecified Hardware: x86 URL: http://downloads.acs.com.hk/utility-tools/en/TOL-PCSC. zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winscard Assignee: wine-bugs(a)winehq.org Reporter: vincent.hardy.be(a)gmail.com Distribution: --- Created attachment 52115 --> https://bugs.winehq.org/attachment.cgi?id=52115 screenshot SimplePC_SC is a programme that tests easily the basic functions of winscard with any smartcard. I file this bug in the hope that a friendly developer starts a real implementation of winscard. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 8

[Bug 53728] New: "Escape from Tarkov" requires "DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" in "DisplayConfigGetDeviceInfo" stub
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53728 Bug ID: 53728 Summary: "Escape from Tarkov" requires "DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" in "DisplayConfigGetDeviceInfo" stub Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: vinni5.2001(a)web.de Distribution: --- Created attachment 73161 --> https://bugs.winehq.org/attachment.cgi?id=73161 Attachments for this report. The video game "Escape from Tarkov" requires the "DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" type to be implemented in the "DisplayConfigGetDeviceInfo" function (dlls/user32/sysparams.c). The game uses that to determine monitor names to list in the ingame settings menu. When it first introduced the use of that function, the lack of it in wine made the whole menu freeze, forcing you to kill the game. That freeze was worked around by the game developers on their end, since it also affected some Windows users, but parts of the issue still remain when running the game in wine. Monitor names in the monitor list in the settings menu are simply blank, making it hard to figure out which entry in the list corresponds to which monitor. See "eft_monitors_blank.png" in "attachments.tar.gz" for reference. Creating a quick and dirty patch to make wine return a string and pretend the function was executed successfully confirms it is using that function to get monitor names and the returned string shows up in the list. See "eft_monitors_names.png" and "dirty-monitor-name-workaround.patch" in "attachments.tar.gz" for reference. I should mention that in case other people wanna test the game, it is not free and makes use of the BattlEye anticheat software, so in order to launch the game with wine, it requires staging, a patch to load the Proton BattlEye Runtime (found here, for example: https://github.com/Frogging-Family/wine-tkg-git/tree/master/wine-tkg-git/wi…), as well as the Proton BattlEye Runtime itself (can be found and installed via Steam by Valve) and the necessary environment variable that points to the Proton BattlEye Runtime ("PROTON_BATTLEYE_RUNTIME"="/path/to/runtime"). It also needs "corefonts", "vcrun2019" and "dotnet48" installed via winetricks. I hope those requirements won't prevent this issue from being looked into, but if they do, I apologize. I was able to put together the quick and dirty patch to confirm it is indeed just a missing or incomplete function, however I lack the programming skills and low-level wine/windows knowledge to implement it properly. 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 4

[Bug 53176] New: KeePassXC needs Windows.Security.Credentials.KeyCredentialManager (UWP)
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53176 Bug ID: 53176 Summary: KeePassXC needs Windows.Security.Credentials.KeyCredentialManager (UWP) Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: mk939(a)ymail.com Distribution: --- Created attachment 72622 --> https://bugs.winehq.org/attachment.cgi?id=72622 stdout and stderr from the terminal while launching the application KeePassXC 2.7.1 (64-bit, Windows) can no longer be started due to a new Windows Hello feature. Older versions prior to Feb 2022 will work as expected. I reproduced this issue on two different machines, each with Wine 7.11 (vanilla). Source code: https://github.com/keepassxreboot/keepassxc/blob/develop/src/winhello/Windo… Specifically, creating a stub for `IsSupportedAsync()` might suffice to disable the feature for this application, assuming a proper implementation on their side: https://github.com/keepassxreboot/keepassxc/blob/develop/src/winhello/Windo… PS: The error mentions "combase", but is not an available choice in the bug report selection box. I am sorry if the selected component 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 6

[Bug 37495] New: AusweisApp2 1.0.0 (german identity card app) needs winscard.SCardEstablishContext implementation
by wine-bugs＠winehq.org 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=37495 Bug ID: 37495 Summary: AusweisApp2 1.0.0 (german identity card app) needs winscard.SCardEstablishContext implementation Product: Wine Version: 1.7.30 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winscard Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, actually it needs much more - the revival of the Wine winscard project. Years ago there were multiple attempts to implement this using pcsc-lite but abandoned later. --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/AusweisApp2 1.0.0 $ WINEDEBUG=+tid,+seh,+relay,+winscard wine ./AusweisApp2.exe --show >>log.txt 2>&1 ... 0029:Call KERNEL32.OutputDebugStringW(01d52780 L"D ReaderManager::onThreadStarted(card/base/ReaderManager.cpp:130) : thread started\n") ret=6674f9f1 ... 0029:Call KERNEL32.OutputDebugStringW(01d53378 L"D ReaderManager::registerPlugIns(card/base/ReaderManager.cpp:242) : Try to register plugins\n") ret=6674f9f1 ... 0029:Call KERNEL32.OutputDebugStringW(01d543f8 L"D ReaderManager::registerPlugIns(card/base/ReaderManager.cpp:247) : Register plugin: QJsonObject({\"IID\":\"governikus.ReaderManagerPlugIn\",\"MetaData\":{\"dependencies\":[],\"name\":\"PcscReaderManagerPlugIn\"},\"className\":\"PcscReaderManagerPlugIn\",\"debug\":false,\"version\":328450}"...) ret=6674f9f1 ... 0029:Call KERNEL32.OutputDebugStringW(01d53bf8 L"D ReaderManager::onThreadStarted(card/base/ReaderManager.cpp:136) : Start plugin: governikus::PcscReaderManagerPlugIn\n") ret=6674f9f1 ... 0029:Call winscard.SCardEstablishContext(00000000,00000000,00000000,01d53260) ret=005015b8 0029:fixme:winscard:SCardEstablishContext (0,(nil),(nil),0x1d53260) stub 0029:Ret winscard.SCardEstablishContext() retval=80100001 ret=005015b8 ... 0029:Call KERNEL32.OutputDebugStringW(01d54868 L"W PcscReaderManagerPlugIn::start(card/pcsc/PcscReaderManagerPlugIn.cpp:70) : SCardEstablishContext: \"SCARD_F_INTERNAL_ERROR\"\n") ret=6674f9f1 ... 0029:Call KERNEL32.OutputDebugStringW(01d546f0 L"W PcscReaderManagerPlugIn::start(card/pcsc/PcscReaderManagerPlugIn.cpp:71) : Not started: Cannot establish context\n") ret=6674f9f1 ... --- snip --- Source: http://source.winehq.org/git/wine.git/blob/8d23d9cbdcc604d7c00e5a1201aac8af… --- snip --- 85 LONG WINAPI SCardEstablishContext(DWORD dwScope, LPCVOID pvReserved1, 86 LPCVOID pvReserved2, LPSCARDCONTEXT phContext) 87 { 88 FIXME("(%x,%p,%p,%p) stub\n", dwScope, pvReserved1, pvReserved2, phContext); 89 SetLastError(ERROR_CALL_NOT_IMPLEMENTED); 90 return SCARD_F_INTERNAL_ERROR; 91 } --- snip --- $ sha1sum AusweisApp2-1.0.0.msi d09f8c6f2cad0a089903a3e31bf96079ae3cfe59 AusweisApp2-1.0.0.msi $ du -sh AusweisApp2-1.0.0.msi 22M AusweisApp2-1.0.0.msi $ wine --version wine-1.7.30 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 19

[Bug 54584] New: kernel32:locale - The NtGetNlsSectionPtr() test fails on Windows 11
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54584 Bug ID: 54584 Summary: kernel32:locale - The NtGetNlsSectionPtr() test fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:locale - The NtGetNlsSectionPtr() test fails on Windows 11: locale.c:4978: Test failed: 14: failed 0 See https://test.winehq.org/data/patterns.html#kernel32:locale This means Windows 11 supports a new type of NLS section (14). Also NtGetNlsSectionPtr() returns success so presumably that section type does not take an id parameter. -- 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 54583] New: kernel32:locale - The non-breaking space GetNumberFormatEx() test fails on Windows 11
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54583 Bug ID: 54583 Summary: kernel32:locale - The non-breaking space GetNumberFormatEx() test fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:locale - The non-breaking space GetNumberFormatEx() test fails on Windows 11: locale.c:1820: Test failed: Expected L"-12\00a0345,00", got L"-12\202f345,00" See https://test.winehq.org/data/patterns.html#kernel32:locale So Windows 11 returns a narrow non-breaking space instead of a 'plain' non-breaking space separator when using the French format. The narrow non-breaking space is probably more correct. -- 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 54534] New: dbghelp:dbghelp - The test_loaded_modules() enumeration fails on Windows 10 1607
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54534 Bug ID: 54534 Summary: dbghelp:dbghelp - The test_loaded_modules() enumeration fails on Windows 10 1607 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dbghelp:dbghelp - The test_loaded_modules() enumeration fails on Windows 10 1607: dbghelp.c:517: Test failed: SymLoadModuleExW failed on C:\WINDOWS\System32\bcryptPrimitives.dll: 0 See https://test.winehq.org/data/patterns.html#dbghelp:dbghelp This is the only Windows 10 version which fails. A bisect confirms that this failure was introduced by the commit below: 8be5c10ff893a22330ad94ae18dfb5fa497b09fd Author: Eric Pouech <eric.pouech(a)gmail.com> AuthorDate: Thu Feb 16 10:48:53 2023 +0100 dbghelp/tests: Add tests for 'module' name in EnumLoadedModules() callback. Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> -- 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 43224] New: Freelist scan can result in O(n) time when allocating
by wine-bugs＠winehq.org 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=43224 Bug ID: 43224 Summary: Freelist scan can result in O(n) time when allocating Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: ranma42(a)gmail.com Distribution: --- Created attachment 58517 --> https://bugs.winehq.org/attachment.cgi?id=58517 Micro-benchmark that shows the degenerate behaviour The heap implementation in ntdll can be very inefficient for some allocation patterns. Specifically, it is possible that a freelist contains thousands of entries of a given size and it is scanned while looking for a bigger entry, that will not fit in any of those. This is demonstrated by the attached program. It accepts a size as an argument and will allocate 1000000 elements of that size, deallocate half of them (the "even" ones), then allocate 1000 elements that are just one bit bigger. For most sizes the program terminates in milliseconds, but in my environment it takes several seconds for sizes 16, 32, 48, 64, 80, 88, 96, 112, 120, 128. A possible workaround (that I had implemented in the past, for short-lived applications) is to allocate from a freelist whose entries are all at least as big as the block that is being allocated, but that can cause inefficient memory usage. I noticed that wine includes an implementation of a red-black tree. Would it make sense to organise the free entries as lists in such a tree? That should ensure O(log N) in the worst case. If performance is a concern, it might be possible to use "direct" freelists for small sizes (ensuring that all of the alignment-compatible sizes are covered) and use a tree for bigger sizes. I am willing to work on this, but I need some directions on what is the best path forward (namely, if we should prefer the memory-inefficient but simpler approach of just allocating from "bigger" freelists or if the tree approach is the desired one). The bug https://bugs.winehq.org/show_bug.cgi?id=37773 might be related. -- 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 37146] New: Untis 2015: Crashes while starting
by wine-bugs＠winehq.org 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=37146 Bug ID: 37146 Summary: Untis 2015: Crashes while starting Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: schutthuffe(a)web.de Created attachment 49371 --> https://bugs.winehq.org/attachment.cgi?id=49371 Report generated by wine Installing Untis 2015 seemed to work. Trying to start the program, the following message popped up: "Im Programm untis.exe traten schwerwiegende Fehler auf und es muss beendet werden. Wir entschuldigen uns für die Unannehmlichkeit." The following report is attached. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 18

[Bug 54582] New: kernel32:locale - test_NLSVersion() fails on Windows 10 22H2
by WineHQ Bugzilla 03 Mar '23

03 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54582 Bug ID: 54582 Summary: kernel32:locale - test_NLSVersion() fails on Windows 10 22H2 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:locale - test_NLSVersion() fails on Windows 10 22H2: locale.c:7871: Test failed: IsValidNLSVersion succeeded See https://test.winehq.org/data/patterns.html#kernel32:locale Apparently the point of this set of test is to verify that IsValidNLSVersion() rejects any version different from that returned by GetNLSVersion(). But sometimes that's not the case. Indeed a similar failure happened on Windows 10 2004 back in the day, see bug 51159. In that case IsValidNLSVersion() accepted versions 0x100 lower than the current one, presumably because that version of Windows was keeping compatibility with older NLS versions. That one was fixed by making bigger changes to the version. In this case Windows 10 22H2 accepts NLS versions that are 0x100 greater than the current one. So presumably we can just use a larger increment to get the expected failure. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs