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

[Bug 56212] New: Crash on using Vulkan under wow64 with wayland
by WineHQ Bugzilla Jan. 19, 2024

Jan. 19, 2024

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 Jan. 19, 2024

Jan. 19, 2024

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 Jan. 18, 2024

Jan. 18, 2024

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 Jan. 18, 2024

Jan. 18, 2024

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 Jan. 18, 2024

Jan. 18, 2024

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 Jan. 18, 2024

Jan. 18, 2024

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

[Bug 56201] New: When opening a program SwissManager, the application shows an error and unable to open.
by WineHQ Bugzilla Jan. 18, 2024

Jan. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=56201 Bug ID: 56201 Summary: When opening a program SwissManager, the application shows an error and unable to open. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wmmolema(a)outlook.com Distribution: --- Created attachment 75909 --> https://bugs.winehq.org/attachment.cgi?id=75909 Back Trace File When opening an application SwissManager, an error occurs. Exception EExternalException in Modul ntdll.dll The application then closes. Unable to get it to load. -- 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 54873] New: 32-bit prefixes cannot be used with new wow64 mode
by WineHQ Bugzilla Jan. 18, 2024

Jan. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=54873 Bug ID: 54873 Summary: 32-bit prefixes cannot be used with new wow64 mode Product: Wine Version: 8.6 Hardware: x86-64 OS: Mac OS X Status: NEW Keywords: download, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com austin(a)mac % rm -rf ~/.wine ; WINEARCH=win32 /Applications/Wine\ Devel.app/Contents/Resources/wine/bin/wine winecfg preloader: Warning: failed to reserve range 0000000000010000-0000000000110000 wine: created the configuration directory '/Users/austin/.wine' wine: '/Users/austin/.wine' is a 32-bit installation, it cannot support 64-bit applications. This also happened when testing on my Linux machine. This prevent using 32-bit prefixes. Which means applications that don't support 64-bit windows can't be run (and we won't be able to report running as a Windows version prior to Server 2003/XP). -- 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 29473] New: IconsExtract: Requesting "File Properties" errors-out.
by wine-bugs＠winehq.org Jan. 18, 2024

Jan. 18, 2024

http://bugs.winehq.org/show_bug.cgi?id=29473 Bug #: 29473 Summary: IconsExtract: Requesting "File Properties" errors-out. Product: Wine Version: 1.3.35 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jthomas97411(a)yahoo.com Classification: Unclassified Simply run IconsExtract in Wine, search for icons somewhere, select a found icon, and try to open the file properties for that icon. This is done either by pressing F8 or clicking "File" in the upper-right, and then under the "File" menu press "File Properties". The sole terminal output is this: fixme:exec:SHELL_execute flags ignored: 0x0000000c This is true for IconsExtract version 1.46 and version 1.47. Have not seen any Wine version succeed in displaying the file properties. In Windows, "File Properties" brings up the same exact dialogue as right-clicking the file that contains the icon and clicking "properties." IconsExtract is a free download: http://www.nirsoft.net/utils/iconsext.zip . -- 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 55424] New: user32:cursoricon - test_SetCursor() sometimes fails on w10pro64v2004
by WineHQ Bugzilla Jan. 18, 2024

Jan. 18, 2024

https://bugs.winehq.org/show_bug.cgi?id=55424 Bug ID: 55424 Summary: user32:cursoricon - test_SetCursor() sometimes fails on w10pro64v2004 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:cursoricon - test_SetCursor() sometimes fails on w10pro64v2004: cursoricon.c:2529: Test failed: expected global cursor 00010003 See https://test.winehq.org/data/patterns.html#user32:cursoricon This failure first happened on 2023-06-05, always with the same cursor handle and always on w10pro64v2004: * 2023-06-05 win2004_newtb-w10pro64v2004-32 * 2023-06-07 win2004_newtb-w10pro64v2004-32 * 2023-06-16 win2004_newtb-w10pro64v2004-32 * 2023-06-19 win2004_newtb-w10pro64v2004-32 * 2023-06-28 win2004_newtb-w10pro64v2004-32 * 2023-08-08 win2004_newtb-w10pro64v2004-32 * 2023-08-08 win2004_newtb-w10pro64v2004-64 The 2023-08-08 final screenshots both show a Windows update window that should not be there. Maybe it is 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.

1 3