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

[Bug 56215] New: SpeedWave buttons can't be functional
by WineHQ Bugzilla 20 Jan '24

20 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=56215 Bug ID: 56215 Summary: SpeedWave buttons can't be functional Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cupcapcorn(a)yahoo.co.jp Distribution: --- On Fedora 39 and wine 9.0 I can install SpeedWave (Application to accelerate the speed of wave and mp3 file) and I try to launch this applicantion and it takes long time for window to appear. And so any button can't be functional, but only sliders can be moved. -- 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 45926] New: Windows Sysinternals ProcessExplorer v12-16+ crashes due to missing advapi32.I_QueryTagInformation () stub
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=45926 Bug ID: 45926 Summary: Windows Sysinternals ProcessExplorer v12-16+ crashes due to missing advapi32.I_QueryTagInformation() stub Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. --- snip --- $ WINEDEBUG=+seh,+relay wine ./procexp64.exe >>log.txt 2>&1 ... 002d:Call KERNEL32.LoadLibraryW(1400d20a8 L"advapi32.dll") ret=140080b4a 002d:Ret KERNEL32.LoadLibraryW() retval=7f4d2a1a0000 ret=140080b4a 002d:Call KERNEL32.GetProcAddress(7f4d2a1a0000,1400ecf08 "I_QueryTagInformation") ret=140080b5a 002d:Ret KERNEL32.GetProcAddress() retval=00000000 ret=140080b5a ... 002d:trace:seh:NtRaiseException code=c0000005 flags=0 addr=(nil) ip=0 tid=002d 002d:trace:seh:NtRaiseException info[0]=0000000000000008 002d:trace:seh:NtRaiseException info[1]=0000000000000000 002d:trace:seh:NtRaiseException rax=0000000000000001 rbx=000000014012c9c8 rcx=0000000000000000 rdx=0000000000000003 002d:trace:seh:NtRaiseException rsi=000000014012c9c0 rdi=000000014012c9d0 rbp=0000000000000000 rsp=000000000023f9b8 002d:trace:seh:NtRaiseException r8=000000000023f9e0 r9=000000014012c9c8 r10=0000000000000000 r11=0000000000000246 002d:trace:seh:NtRaiseException r12=0000000140126560 r13=0000000000000000 r14=000000000000000a r15=0000000140000000 002d:trace:seh:RtlVirtualUnwind type 1 rip 14006377a rsp 23f9c0 002d:trace:seh:dump_unwind_info **** func 63720-637a6 --- snip --- Disassembly at crash site (running under x64dbg): --- snip --- 0000000140063720 | mov qword ptr ss:[rsp+8],rbx | 0000000140063725 | mov qword ptr ss:[rsp+10],rbp | 000000014006372A | mov qword ptr ss:[rsp+18],rsi | 000000014006372F | push rdi | 0000000140063730 | sub rsp,30 | 0000000140063734 | mov rsi,rcx | 0000000140063737 | mov rcx,qword ptr ds:[rcx] | 000000014006373A | mov rbx,r9 | 000000014006373D | mov rdi,r8 | 0000000140063740 | mov rbp,rdx | 0000000140063743 | test rcx,rcx | 0000000140063746 | je procexp64.14006375B | 0000000140063748 | call qword ptr ds:[1400D0958] | 000000014006374E | mov qword ptr ds:[rbx],0 | 0000000140063755 | mov dword ptr ds:[rdi],0 | 000000014006375B | lea r8,qword ptr ss:[rsp+20] | 0000000140063760 | mov edx,3 | 0000000140063765 | xor ecx,ecx | 0000000140063767 | mov dword ptr ss:[rsp+20],ebp | 000000014006376B | mov qword ptr ss:[rsp+28],0 | 0000000140063774 | call qword ptr ds:[14012CC68] | NULL *boom* 000000014006377A | test eax,eax | 000000014006377C | jne procexp64.140063791 | 000000014006377E | mov rdx,qword ptr ss:[rsp+28] | 0000000140063783 | mov ecx,dword ptr ds:[rdx] | 0000000140063785 | mov dword ptr ds:[rdi],ecx | 0000000140063787 | mov rcx,qword ptr ds:[rdx+8] | 000000014006378B | mov qword ptr ds:[rbx],rcx | 000000014006378E | mov qword ptr ds:[rsi],rdx | 0000000140063791 | mov rbx,qword ptr ss:[rsp+40] | 0000000140063796 | mov rbp,qword ptr ss:[rsp+48] | 000000014006379B | mov rsi,qword ptr ss:[rsp+50] | 00000001400637A0 | add rsp,30 | 00000001400637A4 | pop rdi | 00000001400637A5 | ret | --- snip --- Using the "find references to address" method for 0x14012CC68 one comes across this: --- snip --- 0000000140080B4A | lea rdx,qword ptr ds:[1400ECF08] | "I_QueryTagInformation" 0000000140080B51 | mov rcx,rax | 0000000140080B54 | call qword ptr ds:[1400D0968] | 0000000140080B5A | lea rcx,qword ptr ds:[1400ECF30] | L"wow64cpu" 0000000140080B61 | mov qword ptr ds:[14012CC68],rax | --- snip --- which corresponds to the trace log snippet earlier. At one point Wine might implement service process tags as well for mapping service hosting threads with their owner service. Service tags were introduced with Windows Vista. The tag is contained in the TEB of every thread (sub-process tag) and is used in threads owned by service processes as a way to link them with their owning service name. https://github.com/processhacker/processhacker/blob/master/phlib/svcsup.c#L… --- snip --- PPH_STRING PhGetServiceNameFromTag( _In_ HANDLE ProcessId, _In_ PVOID ServiceTag ) { static PQUERY_TAG_INFORMATION I_QueryTagInformation = NULL; PPH_STRING serviceName = NULL; TAG_INFO_NAME_FROM_TAG nameFromTag; if (!I_QueryTagInformation) { I_QueryTagInformation = PhGetDllProcedureAddress(L"advapi32.dll", "I_QueryTagInformation", 0); if (!I_QueryTagInformation) return NULL; } memset(&nameFromTag, 0, sizeof(TAG_INFO_NAME_FROM_TAG)); nameFromTag.InParams.dwPid = HandleToUlong(ProcessId); nameFromTag.InParams.dwTag = PtrToUlong(ServiceTag); I_QueryTagInformation(NULL, eTagInfoLevelNameFromTag, &nameFromTag); if (nameFromTag.OutParams.pszName) { serviceName = PhCreateString(nameFromTag.OutParams.pszName); LocalFree(nameFromTag.OutParams.pszName); } return serviceName; } --- snip --- https://github.com/processhacker/processhacker/blob/2bb718f36a702fde6cb346e… --- snip --- _Must_inspect_result_ DWORD WINAPI I_QueryTagInformation( _In_opt_ LPCWSTR pszMachineName, _In_ TAG_INFO_LEVEL eInfoLevel, _Inout_ PVOID pTagInfo ); --- snip --- $ sha1sum ProcessExplorer.zip 97d882b15890471ea9942c80997c180fbfcbba26 ProcessExplorer.zip $ du -sh ProcessExplorer.zip 1.9M ProcessExplorer.zip $wine --version wine-3.17-39-gc96eba60e3 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 3

[Bug 31076] New: WinDirStat problem after clicking on file in graphical analysis
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=31076 Bug #: 31076 Summary: WinDirStat problem after clicking on file in graphical analysis Product: Wine Version: 1.5.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: computergeoffrey(a)zoho.com Classification: Unclassified Created attachment 40789 --> http://bugs.winehq.org/attachment.cgi?id=40789 Exception details "WinDirStat encountered an error and must be closen down." after clicking on a file in the graphical output window. Download here: http://windirstat.info/download.html See also attachment. -- 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 34

[Bug 31145] New: WinDirStat right clicking on a directory and selecting properties says "invalid parameter"
by wine-bugs＠winehq.org 20 Jan '24

20 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=31145 Bug #: 31145 Summary: WinDirStat right clicking on a directory and selecting properties says "invalid parameter" Product: Wine Version: 1.5.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: computergeoffrey(a)zoho.com Classification: Unclassified After analysis of a directory, right clicking on a directory (doesn't matter which, as long it's in the "scope" of the analysis) and selecting properties shows the error message "invalid parameter". -- 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 22

[Bug 56212] New: Crash on using Vulkan under wow64 with wayland
by WineHQ Bugzilla 19 Jan '24

19 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=56212 Bug ID: 56212 Summary: Crash on using Vulkan under wow64 with wayland Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: yaroslav.isakov(a)gmail.com Distribution: --- Hello! I'm testing new features of Wine, namely WoW64 mode, Wayland driver, and Vulkan (as it's the only way to run games on Wayland ATM), but it crashes with errors mentioning wine_vkAllocateMemory. The good example is SuperTuxKart (it's the only free pure vulkan game with 32-bit support I found) - when I run i686 binary (version 1.4) with --render-driver=vulkan, it crashes with tons of messages: 0120:fixme:vulkan:wine_vkAllocateMemory Using VK_EXT_external_memory_host 0140:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 02000000 0140:err:vulkan:wine_vkAllocateMemory NtAllocateVirtualMemory failed 013c:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 02000000 When I'm trying to run game via dxvk, it fails with similar message: 0148:fixme:vulkan:wine_vkAllocateMemory Using VK_EXT_external_memory_host 0148:fixme:vulkan:wine_vkAllocateMemory Not found compatible memory type Same game, amd64 binary with vulkan - works (also, no problems running dxvk with 64-bit game, too). -- 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 51446] New: VICE X64.exe crashing (from within C64forever from cloanto)
by WineHQ Bugzilla 19 Jan '24

19 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=51446 Bug ID: 51446 Summary: VICE X64.exe crashing (from within C64forever from cloanto) Product: Wine-staging Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marcok(a)web.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70295 --> https://bugs.winehq.org/attachment.cgi?id=70295 Backtrace hi! >From within c64forever x64.exe is crashing. See attached report -- 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 56163] New: Unigine Sanctuary is badly broken with OGL/WineD3D (only works with Gallium Nine)
by WineHQ Bugzilla 19 Jan '24

19 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=56163 Bug ID: 56163 Summary: Unigine Sanctuary is badly broken with OGL/WineD3D (only works with Gallium Nine) Product: Wine Version: 9.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- Created attachment 75862 --> https://bugs.winehq.org/attachment.cgi?id=75862 Unigine Sanctuary CLI output OpenGL Hi all Here follows a bug report about the Unigine Sanctuary benchmark which is unfortunately broken with OpenGL/WineD3D. I have tested this recently with Wine 9.0-rc4 and it works stable only when Gallium Nine is used. At the CLI there is a "Failed to load libGL: libGL.so.1" information present. See the CLI output file for more details. For me, the OGL path was always broken while the D3D10 mode had worked (with some flaws) at some point with Wine 8.x. The D3D11 renderer was not intensively tested because the corresponding D3D11 support was incomplete in earlier Wine / WineD3D releases. And finally, there is an additional strange problem concerning the native "openal32.dll" file present which can lead to a hard system hang. This never occurred on Wine builds which had an in-built "openal32.dll" file. Will open a separate issue report about that. This was tested under Kubuntu 22.04 LTS with Mesa 24.0-git2401110600.813b19-oibaf-j (git-813b193 2024-01-11 jammy-oibaf-ppa). The system is an old iMac 12,2 containing an Radeon HD 6770M GPU which is using the r600 Mesa driver. Note, the Unigine Sanctuary benchmark can still be downloaded from the original website: https://benchmark.unigine.com/sanctuary -- 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 21

[Bug 51925] New: TeXLive linux binaries are launched incorrectly from Wine
by WineHQ Bugzilla 18 Jan '24

18 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=51925 Bug ID: 51925 Summary: TeXLive linux binaries are launched incorrectly from Wine Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: oleh.nyk(a)gmail.com Distribution: --- Linux TeXLive binaries can be successfully started, e.g., by WinEdt shell under Wine. Nevertheless, TeXLive components use mktex.opt file to find out the platform they are run on, based on environment variables. As Wine leaves ComSpec variable set, mktex.opt deduces it is on Windows, but cannot find dirs for fonts and metrics, hence puts temporary files in a working directory. Steps to reproduce (assume TeXLive distribution is installed and working): 1. Unpack winedt-1.41e http://ftp.itam.mx/pub/academico/investig/latex/LaTeXWin/winedt16.zip 2. Start winedt.exe and open any LaTeX file 3. Change LaTeX entry in menu to make it start LaTeX in XTerm, e.g. "z:\usr\bin\xterm" -T LaTeX -e /usr/bin/latex "%N%T" 4. Run LaTeX and observe *.tfm files created in the directory with LaTeX document instead of the proper directories for this. Here is a part of the output of "env | sort" in XTerm run from WinEdt: ... CommonProgramFiles=C:\Program Files (x86)\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=SHELTER ComSpec=C:\windows\system32\cmd.exe CPLUS_INCLUDE_PATH=/opt/kde3/lib64/qt3/include DISPLAY=:0.0 FVWM_64=64 ... To avoid this, there should be a way to prohibit Wine to pass some Windows environment variables to Unix binaries. -- 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 43102] New: GTA V keyboard issue
by wine-bugs＠winehq.org 18 Jan '24

18 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=43102 Bug ID: 43102 Summary: GTA V keyboard issue Product: Wine Version: 2.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xsellier(a)gmail.com Distribution: Debian Hey folks, Thank you for you amazing work here. I have a bug when I try to play GTA V. This bug is related to the keyboard. *How to reproduce it* 1. Install wine 2.9 with following components: - d3dcompiler_43 - d3dx11 2. Run winecfg and set the windows version to Windows XP 3. Install steam 4. Install GTA V 5. Run GTA V (login to the social club) 6. Once the game has started do the ALT+TAB trick (https://bugs.winehq.org/show_bug.cgi?id=42330#c18) 7. Press any key of the keyboard (it works flawlessly) 8. Select the Story Mode 9. Once in game, press any key from the keyboard. Now the game is freezing for a 2 second and it will work again. This issue is related to the keyboard, because if you are using a controller (xbox for example) it works without any stutter. But press a key of the keyboard and the freeze is coming (sorry for this one). *Observation* - The sound is still playing - Only the rendering is frozen -- 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 51

[Bug 51565] New: Wine filesystem access time year 2038 problem: functions return ERROR_FILE_NOT_FOUND, STATUS_UNSUCCESSFUL
by WineHQ Bugzilla 18 Jan '24

18 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=51565 Bug ID: 51565 Summary: Wine filesystem access time year 2038 problem: functions return ERROR_FILE_NOT_FOUND, STATUS_UNSUCCESSFUL Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: iam(a)valdikss.org.ru Distribution: --- Wine does not handle directories and files with access time past year 2038. The functions like FindFirstFileA return ERROR_FILE_NOT_FOUND upon accessing the directory for example. How to reproduce: mkdir testdir touch -a -d 'Fri, 06 Aug 2039 15:01:42 +0300' testdir wine cmd.exe /C "dir testdir" Result: 0104:fixme:file:errno_to_status Converting errno 75 to STATUS_UNSUCCESSFUL Volume in drive Z has no label. Volume Serial Number is adda-a790 Directory of Z:\home\valdikss\temp\testdir File not found. -- 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