- Wine-bugs - list.winehq.org

[Bug 52330] New: iZotope software authorization process fails
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

https://bugs.winehq.org/show_bug.cgi?id=52330 Bug ID: 52330 Summary: iZotope software authorization process fails Product: Wine-staging Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frech(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71492 --> https://bugs.winehq.org/attachment.cgi?id=71492 journalctl log during authorization process Authorizing iZotope software will result in an error. According to the iZotope Support, the attempt is visible, but the local application did not recognize that. Also 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 20

[Bug 49393] New: Gag game crash
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

https://bugs.winehq.org/show_bug.cgi?id=49393 Bug ID: 49393 Summary: Gag game crash Product: Wine Version: 5.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: axet(a)me.com Distribution: --- Hello! I'm trying to run 'Gag' game. And it's crashing winmm reading at zero memory address. I've tested few wine versions 5.0.0 .. 5.10 and all have same issue. https://en.wikipedia.org/wiki/GAG_The_Impotent_Mystery If you want trying to run the game, you gonna need start X server with 16-bit display like this: Xephyr :1 -ac -screen 800x600x16 & Crash output: 5.10 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7db6). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7db6 ESP:016cf7c0 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:00ca3e08 ECX:016cf760 EDX:000001d0 ESI:00000000 EDI:014afb1c Stack dump: 0x016cf7c0: 009b38b8 639ec090 00000001 00000000 0x016cf7d0: 00ca3e24 00000000 00000000 639d85b5 0x016cf7e0: 00ca3ed4 00000008 000000e8 7ea09ea0 0x016cf7f0: 00000001 016cf810 016cf8cc 016cf820 0x016cf800: 0000001c 7ffc4000 0000003f 00ca0cf0 0x016cf810: 00ca0cf0 016cf830 639efe20 00ca3e08 Backtrace: =>0 0x639d7db6 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8688 EntryPoint+0xffffffff() in winmm (0x00ca3ed4) 2 0x639da5b9 EntryPoint+0xffffffff() in winmm (0x016cf918) 3 0x7ea1bd0c in user32 (+0x9bd0b) (0x016cf918) 4 0x7ea1c35d in user32 (+0x9c35c) (0x016cf968) 5 0x7ea1e5a3 in user32 (+0x9e5a2) (0x016cf9b8) 6 0x7e9db0f2 in user32 (+0x5b0f1) (0x016cfa28) 7 0x7e9dd6c7 in user32 (+0x5d6c6) (0x016cfe48) 8 0x7e9e32df in user32 (+0x632de) (0x016cfea8) 9 0x639d9949 EntryPoint+0xffffffff() in winmm (0x016cff5c) 0x639d7db6 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) 5.0.0 Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x639d7b36). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:639d7b36 ESP:0127f700 EBP:00000001 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:0089e300 ECX:0127f6a0 EDX:0089e678 ESI:00000000 EDI:0105fb0c Stack dump: 0x0127f700: 0089c3c8 639eb090 00000001 00000000 0x0127f710: 0089e31c 00000000 00000000 639d8335 0x0127f720: 0089e3cc 00000008 000000e8 0127f750 0x0127f730: 0000000c 00030038 0127f768 7e925c50 0x0127f740: 7ea78cc0 7ffc4000 0000003f 0089c9f0 0x0127f750: 0089c9f0 0127f770 639eee20 0089e300 Backtrace: =>0 0x639d7b36 EntryPoint+0xffffffff() in winmm (0x00000001) 1 0x639d8408 EntryPoint+0xffffffff() in winmm (0x0089e3cc) 2 0x639da339 EntryPoint+0xffffffff() in winmm (0x0127f858) 3 0x7e93863c in user32 (+0xa863b) (0x0127f858) 4 0x7e938cad in user32 (+0xa8cac) (0x0127f8a8) 5 0x7e93b113 in user32 (+0xab112) (0x0127f8f8) 6 0x7e8f635e in user32 (+0x6635d) (0x0127f968) 7 0x7e8f8a7f in user32 (+0x68a7e) (0x0127fe38) 8 0x7e8fedca in user32 (+0x6edc9) (0x0127fe98) 9 0x639d96c9 EntryPoint+0xffffffff() in winmm (0x0127ff4c) 0x639d7b36 EntryPoint+0xffffffff in winmm: cmpw $1,0x0(%eax) -- 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 42027] New: Xilinx Vivado 2014.4 installer fails: systeminfo is a stub
by wine-bugs＠winehq.org 06 Mar '26

06 Mar '26

https://bugs.winehq.org/show_bug.cgi?id=42027 Bug ID: 42027 Summary: Xilinx Vivado 2014.4 installer fails: systeminfo is a stub Product: Wine Version: 2.0-rc1 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: jack.lovell(a)ukaea.uk Created attachment 56490 --> https://bugs.winehq.org/attachment.cgi?id=56490 Log output until the installer crashes. When trying to run the Xilinx Vivado 2014.4 web installer, the program crashes shortly after startup. A look at the log output suggests the installer is calling systeminfo and piping the output to findstr to get the OS version. However, systeminfo is a stub, and so outputs nothing to stdout. I plan to file the findstr stub as a separate bug 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.

3 11

[Bug 59140] New: Bug avec le logiciel pronote pendant sa mise à jour
by bugs＠winehq.org 06 Mar '26

06 Mar '26

http://bugs.winehq.org/show_bug.cgi?id=59140 Bug ID: 59140 Summary: Bug avec le logiciel pronote pendant sa mise à jour Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: p.gerbaud(a)free.fr Distribution: --- Created attachment 79960 --> http://bugs.winehq.org/attachment.cgi?id=79960 Détails de l'erreur du programme J'ai voulu mettre mon logiciel à jour mais une fenètre Wine Debugger s'est ouverte, ainsi que la fenètre des Détails de l'erreur du programme (voir fichier joint) Je sui novice (2 mois) sur Linux Mint, merci pour votre aide -- 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 57415] New: ROMCenter crash after creating database > IO Exception cannot locate resource images/defaultsystemicon.png
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

https://bugs.winehq.org/show_bug.cgi?id=57415 Bug ID: 57415 Summary: ROMCenter crash after creating database > IO Exception cannot locate resource images/defaultsystemicon.png Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: augusto7744(a)aol.com Distribution: --- Hello. Thanks for reading my topic. Ubuntu 24.04.1 and WINE 9.18 ( version 9.21 crash some softwares related with the bug https://bugs.winehq.org/show_bug.cgi?id=57306 so not tested with that version ). ROMCenter 4.1.1 32 bits. An rom manager software using database hash. When is done the creation of database happen an crash showing the error message below and close the software. IO Exception cannot locate resource images/defaultsystemicon.png Seeing in some sites is as if is related with net framework. Some WINE previous versions the software run perfectly without errors. Perhaps is related with wine-mono ? Have an nice week. -- 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 59492] New: Wine 11.3: Application renders partial viewport (Splashtop RMM)
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

http://bugs.winehq.org/show_bug.cgi?id=59492 Bug ID: 59492 Summary: Wine 11.3: Application renders partial viewport (Splashtop RMM) Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: noah.bartlett(a)itguysteam.com Distribution: --- Created attachment 80495 --> http://bugs.winehq.org/attachment.cgi?id=80495 Image of what I see, remote desktop was 1080P rendered slightly below 1080P on my desktop When connecting to a remote desktop with a higher resolution than the local window (e.g. 4K remote on 1080p local), Splashtop renders only the top-left portion of the remote desktop that matches the local window resolution in pixels (1:1), leaving the remainder black. Reducing zoom makes the rendered area smaller rather than larger, suggesting the viewport is calculated as window_size × zoom_factor rather than scaling remote content to fit the window. The application works correctly on native Windows. Steps to reproduce: 1. Configure Splashtop RMM client to launch from atera/similar agent 2. Launch Splashtop RMM client under Wine and connect to a remote desktop with resolution higher than the local window 3. Observe that only the top-left portion renders; remainder is black Expected: Remote desktop content scales to fit the local window, renders full desktop I used this guide to get wine to launch splashtop from linux, but this did not modify wine (i think?) and this is occurring on both stable and staging versions of wine. https://community.syncromsp.com/t/splashtop-remote-access-from-linux-workar… Additional testing — winewayland driver: Launching the application with DISPLAY= (unset) and WAYLAND_DISPLAY=wayland-0 to force Wine's native Wayland driver produced identical rendering behaviour, ruling out XRandR/Xinerama coordinate reporting as the direct cause. The partial viewport issue persists regardless of whether the X11 or Wayland graphics driver is used, suggesting the root cause is in a higher-level API (possibly GetSystemMetrics, GetMonitorInfo, or similar?) returning unexpected values on a multi-monitor system where one monitor has negative virtual screen coordinates. I am unsure if there are any logs that can help - but if you'd like to point me to what you need I'm happy to grab them and upload them. Also I'm kind of an idiot so I used claude to help generate a bug report as I don't want to waste anyone's time with a useless bug report that didn't have information that may be needed. I went over everything and it is correct, but any suggestions are claude conjecture so if they make no sense, I apologize. It's just a very strange issue. System info: Arch Linux x86_64 Kernel: 6.18.13-arch1-1 DE: Plasma 6.6.1/Wayland Host: Vostro 15 7510 -- 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 59472] New: FreeArc hangs on startup in new wow64 mode
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

http://bugs.winehq.org/show_bug.cgi?id=59472 Bug ID: 59472 Summary: FreeArc hangs on startup in new wow64 mode Product: Wine Version: 11.3 Hardware: x86-64 URL: https://archive.org/details/FreeArc-0.666-win32bin-Sou rces OS: Linux Status: NEW Keywords: download, testcase, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: arethusa26(a)gmail.com Distribution: --- Created attachment 80459 --> http://bugs.winehq.org/attachment.cgi?id=80459 Largest memory block loop test case executable When running the FreeArc archiver tool on the command line to add a file to an archive with a new wow64 build of Wine, the tool hangs indefinitely with only a banner output string: $ wine freearc/bin/Arc.exe a test.arc empty_file 0124:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 With a old wow64 build of Wine, the tool runs and completes successfully: $ wine freearc/bin/Arc.exe a test.arc empty_file 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... creating archive: test.arc Compressing 1 file, 1,024 bytes. Processed 0% 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... Compressed 1 file, 1,024 => 44 bytes. Ratio 4.2% Compression time: cpu 0.62 secs, real 0.31 secs. Speed 3 kB/s All OK To reproduce the issue with FreeArc, download "FreeArc-portable-0.666-win32.zip" from the URL link and extract the contents of the ZIP file to a directory named "freearc". The Arc.exe binary can be run with the provided command line. When FreeArc is run with new wow64 Wine, there appears to be a thread that is stuck repeatedly calling VirtualAlloc with 0 size: 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 The code involved in the hang appears to be the LargestMemoryBlock::LargestMemoryBlock() constructor in Environment.cpp from the FreeArc sources. It's a (buggy) loop that attempts a binary search for the largest size it can successfully pass to VirtualAlloc. I have extracted the logic to create a standalone test case, which is built with: i686-w64-mingw32-gcc -O2 -Wall -Wl,--large-address-aware -o largest_memory_block.exe largest_memory_block.c On Windows 10, the largest_memory_block.exe test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 7fffffff a = 0 b = 7fffffff Freeing pointer 00000000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 01970000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 7f98ffff b = 7f990001 Freeing pointer 00000000 with VirtualFree Allocating 7f990000 bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7f990000 On new wow64 Wine, the test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7fffffff a = 7fffffff b = ffffffff Freeing pointer 7fff0000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 00900000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 1 b = ffffffff Freeing pointer 003f0000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 a = 1 b = 0 Freeing pointer 00000000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 ... The midpoint computation "c = (a + b) / 2" in the loop overflows when the initial allocation succeeds on Wine and leads to incorrect execution, whereas the initial allocation doesn't appear to succeed on Windows. -- 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 52741] New: Missing chakra.dll to run Minecraft Windows 10 Edition
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

https://bugs.winehq.org/show_bug.cgi?id=52741 Bug ID: 52741 Summary: Missing chakra.dll to run Minecraft Windows 10 Edition Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bdard.antoine(a)gmail.com Distribution: --- Hello, I am trying to run Windows 10, but there is this weird missing dll (chakra.dll). Could it be added? -- 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 59289] New: GOG-Game "Asterix and Obelix XXXL: The Ram From Hibernia" crashes on start
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

http://bugs.winehq.org/show_bug.cgi?id=59289 Bug ID: 59289 Summary: GOG-Game "Asterix and Obelix XXXL: The Ram From Hibernia" crashes on start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: jmb_tux(a)gmx.net Distribution: --- Created attachment 80222 --> http://bugs.winehq.org/attachment.cgi?id=80222 Screen Dump from Crash Report by AOA.exe I am now using WineHQ Repos - both stable and devel, but currently these are the same. Why is there no 11.0 as devel-version to select? Especially as both, stable and devel, are 11.0 ? But in this case, versions are quite unimportant, as it is the same on 10.0 or 9.0 ... The former 3 "Asterix&Obelix XXL" titles work without problem (Wine 9 like Wine 10), but now the new title no longer used their own engine, but OSome Studio / Microids use with the latest Release on 27.10.2022 Epic's Unreal Engine 5, but it looks this is severely broken. As I am not using Windows, I can not say that it works / don't work on Windows. Unfotunately, GOG is not willing give the slightest support when using Wine. Thus instead of getting info - I can only ask for Refund. Then after some time buy it again, test it, and ask for refund if its is still broken ... When starting it with Wine via "wine AOA.exe" (in 'GOG\ Games' binary path, I directly hear a sound and when it ends, the crash message appears: ~~~ "The UE4-AOA [File:Unknown] [Line: 339]" Direct3DDevice->CreateTexture2D(TextureDesc,SubResourceData,OutTexture2D) failed at D:/P41660/UE427Custom/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11Texture.cpp:534 with error E-INVALIDARG, Size)1920x1080x1 PF=67 Format=(9x99999967), NumMips=1, Flags=D2D11_BIND_SHADER_RESOURCE, Usage:0x0, CPUFlags: 0x0, MiscFlags:0x0, SampleCount:0x1, SampleQuality:0x0, SubresPtr:0x0000000000000000m SubpresPitch:0,SupresSlicePitch:0 [OK] ~~~ (I hope I have no typo - but I have added a screen dump as attatchment.) The same error message shows on an o AMD system Zen 4: Ryzen 9 7900 & RDNA 3: Radeon RX 7800 XT as well as in an o Intel Skylake with Nvidi graphics. So it is not HW relevant ... but while gamers report about many bugs, I have not read about direct crashes on start as happening under Wine. It is the 1st game using 4 Players in locCoop for that series ... and it would be a pity, if this can not be played under Wine at all ... If I am able to reach for Devs/Publisher, I will hint them to this bug report ... and will add any information I might get - especially about changes following WineHQ-Devel. Maybe Wine Devs could hint to the current problem. -- 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 58248] New: Me(Idx) fails to compile
by WineHQ Bugzilla 06 Mar '26

06 Mar '26

http://bugs.winehq.org/show_bug.cgi?id=58248 Bug ID: 58248 Summary: Me(Idx) fails to compile Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: francisdb(a)gmail.com Distribution: --- code: Sub Spinner_Hit(Idx) Me(Idx).IsDropped=True 'Spinner(Idx).IsDropped=True End Sub Wine: /opt/wine-devel/bin/wine cscript test.vbs 0134:fixme:vbscript:make_call_expression Unhandled for expr type 22 0134:fixme:wscript:ActiveScriptSite_OnScriptError () 0134:fixme:wscript:run_script ParseScriptText failed: 80004005 Windows: [Running] cscript //Nologo "c:\Users\me\OneDrive\Bureaublad\test.vbs" [Done] exited with code=0 in 0.097 seconds -- 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