March 2022 - Wine-bugs - list.winehq.org

[Bug 52482] New: Invisible UI in installer of Lightroom Classic 2021/2022
by WineHQ Bugzilla 24 Apr '22

24 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52482 Bug ID: 52482 Summary: Invisible UI in installer of Lightroom Classic 2021/2022 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: mikrutrafal(a)protonmail.com Distribution: --- Created attachment 71775 --> https://bugs.winehq.org/attachment.cgi?id=71775 Wine log When trying to install LR Classic 2021/2022, then I see only a white window and a error spam: """ 0178:fixme:mshtml:HTMLWindow2_get_frames (06004AF0)->(00D5F3A0): semi-stub 0178:fixme:mshtml:HTMLWindow2_get_frames (06004AF0)->(00D5F3A0): semi-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 1

[Bug 49111] New: ELWAVE Demo installer crashes on start
by WineHQ Bugzilla 24 Apr '22

24 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=49111 Bug ID: 49111 Summary: ELWAVE Demo installer crashes on start Product: Wine Version: 5.2 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 67087 --> https://bugs.winehq.org/attachment.cgi?id=67087 Wine log The installer crashes as soon as its run, see attached log - that's a full log, not only the backtrace. -- 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 49112] New: ELWAVE doesn't start - detects Wine as VM
by WineHQ Bugzilla 23 Apr '22

23 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=49112 Bug ID: 49112 Summary: ELWAVE doesn't start - detects Wine as VM Product: Wine Version: 5.2 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: --- The program doesn't start, since it refuses to work in a VM but detects Wine as such. Seems to work on older CPUs though, so maybe that's a clue. Reported in the forums: https://forum.winehq.org/viewtopic.php?f=2&t=33826 -- 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 51387] New: Critical Section timeout between "dlls/user32/user_main.c: user_section" and "dlls/winex11.drv/window.c: win_data_section"
by WineHQ Bugzilla 23 Apr '22

23 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51387 Bug ID: 51387 Summary: Critical Section timeout between "dlls/user32/user_main.c: user_section" and "dlls/winex11.drv/window.c: win_data_section" Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: l.arzeni(a)iname.com Distribution: --- Created attachment 70242 --> https://bugs.winehq.org/attachment.cgi?id=70242 application logs Environment: GNU Debian Linux, kernel 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19), Wine 4.0.2, but I tested it and I can reproduce the issue under every release of wine32, from release 1.5 to release 5.0.3, I'm running an old windows application. It works showing a list of records from an ODBC connection, then when a record is clicked, it opens a form for editing the record. It's similar to MS Access, but the application is written in a 4GL db language called clarion. I can share the sources, if needed. The application works fine under "native" windows (tested in all releases of windows, from windows XP to Windows 10). The application looks fine, but hangs after a while, if I run it under wine: env WINEPREFIX=/home/user1/.wine32 wine /srv/data/shared/LicenseManager.exe The log shows that there is a timeout in a critical section, may be a deadlock between: "dlls/user32/user_main.c: user_section" and "dlls/winex11.drv/window.c: win_data_section" This is the relevant lines of the logs: 0024:err:ntdll:RtlpWaitForCriticalSection section 6EDB7C80 "dlls/user32/user_main.c: user_section" wait timed out in thread 0024, blocked by 0114, retrying (60 sec) 0114:err:ntdll:RtlpWaitForCriticalSection section 7DB04220 "dlls/winex11.drv/window.c: win_data_section" wait timed out in thread 0114, blocked by 0024, retrying (60 sec) To solve the issue, I run it with "taskset --cpu-list 0 ", that is: env WINEPREFIX=/home/user1/.wine32 taskset --cpu-list 0 wine /srv/data/shared/LicenseManager.exe But, if I user the taskset, the application GUI artifacts became "dirty" , and I need to close and reopen the window to redraw them properly. Is there any clue to solve this issue, or, at least, to avoid the garbage on the user interface when running under the "taskset" command? Please note: the issue is not "application specific" but, afaik, instead the bug affects all application generated with "clarion" Regards, Luca -- 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 52508] New: EnumDisplayDevices() fails in obscure ways on 32-bit arch when 64-bit Vulkan is present but 32-bit is missing
by WineHQ Bugzilla 23 Apr '22

23 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52508 Bug ID: 52508 Summary: EnumDisplayDevices() fails in obscure ways on 32-bit arch when 64-bit Vulkan is present but 32-bit is missing Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: jacek(a)codeweavers.com, zzhang(a)codeweavers.com Distribution: --- FWIW, this is easy to trigger by running 32-bit ddraw:ddraw1. I'm fine with calling this case "user error", but the problem is, it's not that hard to be missing Vulkan drivers for one architecture, while debugging this took way too long. It'd be nice to at least have some way of printing a message. The basic problem is that when Vulkan is present we retrieve the PCI IDs from it, but when it's absent we set them to zero. As a result we end up creating two different sets of registry entries, but only the 64-bit one gets populated via initialize_display_settings(). EnumDisplayDevices() tries to access it and finds the GPU entries empty. This does lead me to ask: can we avoid querying GPUs in each process? Can we just let explorer.exe manage them and get our information from there? CC'ing Jacek and Zhiyi as both having worked closely with this code. -- 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 24574] New: RAR Password Recovery Magic initial (registration) window is empty and doesn't allow any interaction
by wine-bugs＠winehq.org 22 Apr '22

22 Apr '22

http://bugs.winehq.org/show_bug.cgi?id=24574 Summary: RAR Password Recovery Magic initial (registration) window is empty and doesn't allow any interaction Product: Wine Version: 1.3.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: t.artem(a)mailcity.com Created an attachment (id=31036) --> (http://bugs.winehq.org/attachment.cgi?id=31036) The initial window Download and install, try to run. -- 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 16

[Bug 52640] New: Steam does not display anything when using the Vulkan renderer (stack overflow from official Vulkan loader calling into dxgi)
by WineHQ Bugzilla 22 Apr '22

22 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52640 Bug ID: 52640 Summary: Steam does not display anything when using the Vulkan renderer (stack overflow from official Vulkan loader calling into dxgi) Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Regression SHA1: 24432a24d5e922cbd824b0af8f7b0c66ff2b66e8 Distribution: --- steamwebhelper.exe constantly crashes due to a stack overflow: 05bc:err:winediag:wined3d_dll_init Using the Vulkan renderer. 05bc:fixme:heap:RtlSetHeapInformation 0000000000000000 1 0000000000000000 0 stub 05bc:err:virtual:virtual_setup_exception stack overflow 2000 bytes in thread 05bc addr 0x1700304f0 stack 0x20830 (0x20000-0x21000-0x120000) The problem is that CEF ships the Vulkan loader (vulkan-1.dll), and during the process of initializing Vulkan [wined3d_init_vulkan()], the loader calls CreateDXGIFactory1(), which triggers Wine to initialize itself and subsequently initialize Vulkan, leading to infinite recursion. Fundamentally USE_WIN32_VULKAN can't work with the official (?) Vulkan loader, and so any attempt to use the Vulkan renderer on Windows would fail as well... -- 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 52703] New: regression in wine 7.4-1 - irfanview x64 crash in [AccessCheckByTypeAndAuditAlarmW]
by WineHQ Bugzilla 22 Apr '22

22 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52703 Bug ID: 52703 Summary: regression in wine 7.4-1 - irfanview x64 crash in [AccessCheckByTypeAndAuditAlarmW] Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joo.peter(a)gmail.com Distribution: --- Created attachment 72060 --> https://bugs.winehq.org/attachment.cgi?id=72060 this is the backtrace provided by wine when i_view64.exe crashed I think it is important to have the exact steps on how to reproducate such issue. Maybe it is trivial, but I wrote it down here anyway. 1) Install the lastest Manjaro with Xfce desktop environment from here: https://manjaro.org/downloads/official/xfce I downloaded the manjaro-xfce-21.2.4-220301-linux515.iso file. Using VirtualBox I created a fresh installation. 2) Upgraded the fresh install to its latest stable version: yes | sudo pacman -Scc && sudo pacman -Suu --refresh --refresh 3) Irfanview requires mono too, so install wine and wine-mono: sudo pacman -S --needed wine wine-mono The installed version become: multilib/wine = 7.4-1 community/wine-mono = 7.1.1-1 4) Download IrfanView x64 and its plugins from here https://www.irfanview.com/64bit.htm The following links are the one you need from that page: Download IrfanView-64 English (Version 4.60, ZIP file, 3.13 MB) Download IrfanView-64 PlugIns (Version 4.60, ZIP file, 23.80 MB) Afterwards you have two zip files: iview460_x64.zip iview460_plugins_x64.zip 5) Extract iview460_x64.zip to $HOME/temp/irfanview directory. Extract iview460_plugins_x64.zip into the '$HOME/temp/irfanview/Plugins' directory. 6) Go there and run it manually: wine64 ./i_view64.exe It opens with a crash: Backtrace: =>0 0x000000007b037997 AccessCheckByTypeAndAuditAlarmW+0x36997() in kernelbase (0x000000000000000a) 1 0x000000023d82b176 CharLowerA+0x3182() in user32 (0x000000000000000a) 2 0x000000023d82bd0e CharLowerA+0x3d1a() in user32 (0x000000000011f900) 3 0x000000023d82be0e CharLowerA+0x3e1a() in user32 (0x000000000011f900) 4 0x000000014007e070 in i_view64 (+0x7e070) (0x000000000011f900) 5 0x0000000140109500 in i_view64 (+0x109500) (0x0000000000000000) 6 0x000000007b62bb79 ActivateActCtx+0x1ffc1() in kernel32 (0x0000000000000000) 7 0x000000017005a173 A_SHAFinal+0x38243() in ntdll (0x0000000000000000) The full crash is in the attached backtrace.txt file. The proof that previous version works: 1) remove just wine and wine-mono, but keep their dependencies there sudo pacman -R wine wine-mono 2) download the previous compatible versions manually: wget https://archive.archlinux.org/packages/w/wine/wine-7.3-1-x86_64.pkg.tar.zst wget https://archive.archlinux.org/packages/w/wine-mono/wine-mono-7.1.1-1-any.pk… 3) install them: pacman -U ./wine-7.3-1-x86_64.pkg.tar.zst pacman -U ./wine-mono-7.1.1-1-any.pkg.tar.zst 4) run irfanview again, it starts without crash: wine64 ./i_view64.exe -- 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 18

[Bug 52223] New: activeCodePage utf-8 in application manifest not respected
by WineHQ Bugzilla 22 Apr '22

22 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52223 Bug ID: 52223 Summary: activeCodePage utf-8 in application manifest not respected Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fusion Assignee: wine-bugs(a)winehq.org Reporter: terinjokes(a)gmail.com Distribution: --- Starting[1] with Windows 1903 (Windows 10 May 2019 update), Windows has allowed applications to opt-in to supporting the UTF-8 code page by defining "activeCodePage" in their application manifest. When in this mode, the "ANSI" -A WinAPI functions operate in UTF-8 mode. <activeCodePage xmlns="http://schemas.microsoft.com/SMI/2019/WindowsSettings">UTF-8</activeCodePage> WINE, even when winver is set to "win10", does not respect this application manifest key, resulting in the application starting with a legacy code page. This can cause issues if the user expects to work with files or strings not supported in the active legacy code page. Often characters that cannot be represented in the code page are replaced by question marks. I am using the staging release of 6.22. [1]: https://docs.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-c… Expectation: When an application with activeCodePage set to "UTF-8" in the application manifest calls GetACP(), the number 65001 (CP_UTF8) is returned. Strings returned by WinAPI functions (eg, file paths) are encoded in UTF-8. Strings provided to WinAPI functions are UTF-8 and display appropriately in the UI. Observed: GetACP() returned a number representing a legacy code page (eg, 1252). Strings returned by WinAPI functions are in that code page. Characters that cannot be represented are replaced by question marks. -- 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 44144] New: Complete support for “InstallShield Wizard” ( for a game installation)
by wine-bugs＠winehq.org 22 Apr '22

22 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=44144 Bug ID: 44144 Summary: Complete support for “InstallShield Wizard” (for a game installation) Product: Wine Version: 3.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Markus.Elfring(a)web.de Distribution: --- I have tried to install the game “Civilization IV” once more. The corresponding log messages indicate some details for further considerations. elfring(a)Sonne:~> wine /run/media/elfring/CIVILIZATION4/setup.exe 0038:fixme:heap:RtlSetHeapInformation 0x240000 0 0x23fd00 4 stub 0038:fixme:ole:TMStubImpl_Invoke not implemented on non-i386 004b:err:rpc:I_RpcReceive we got fault packet with status 0x80004005 0035:err:ole:xCall RpcChannelBuffer SendReceive failed, 80004005 0038:fixme:ole:TMStubImpl_Invoke not implemented on non-i386 … 0035:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet … 0035:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33ddf4 L"D:\\data1.hdr" 0038:err:ole:StdMarshalImpl_ReleaseMarshalData could not map object ID to stub manager, oxid=3700000038, oid=2 0038:err:ole:CoReleaseMarshalData IMarshal::ReleaseMarshalData failed with error 0x8001011d 0051:err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-4e00-000034000000} 0050:err:rpc:I_RpcReceive we got fault packet with status 0x80010108 … Now I am curious which other open issues will be still remaining if the situation can be improved for the software “InstallShield Wizard” a bit more also around such programming interfaces. -- 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