October 2020 - Wine-Bugs - list.winehq.org

[Bug 18257] New: Quicktime 2 video problems
by wine-bugs＠winehq.org Sept. 20, 2026

Sept. 20, 2026

http://bugs.winehq.org/show_bug.cgi?id=18257 Summary: Quicktime 2 video problems Product: Wine Version: 1.1.20 Platform: PC URL: http://www.oldversion.com/download/quicktime212.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Videos in Quicktime 2 (32-bit) play for about 0.5 seconds and stop. Cycling through the video draws the images but it refuses to play the whole video. Don't know what traces would help here. Tested with latest gitwine too, same problem. wine-1.1.20-36-gdc31d87 Quicktime 2.1.2.59 This is the entire console output: fixme:ole:OleRegisterServer (PlayerFrameClass,0x147100,0x147104,0x400000,1): stub! fixme:ole:OleRegisterServerDoc (1,C:\windows\SAMPLE.MOV): stub -- 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.

3 23

[Bug 45969] New: ArcGIS Pro crashes on start
by wine-bugs＠winehq.org Sept. 20, 2026

Sept. 20, 2026

https://bugs.winehq.org/show_bug.cgi?id=45969 Bug ID: 45969 Summary: ArcGIS Pro crashes on start Product: Wine Version: 3.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 62523 --> https://bugs.winehq.org/attachment.cgi?id=62523 console output To reproduce: 1. Run `winetricks dotnet461`. This is a prerequisite of ArcGIS Pro. 2. Run `wine ArcGISPro_22_163783.exe`. Note that this is a 64-bit program. 3. Run `wine 'C:\Program Files\ArcGIS\Pro\bin\ArcGISPro.exe'`. Console output is attached. $ sha256sum ArcGISPro_22_163783.exe b6acceb36d51cdb1cc283478fd6170b7e51630f127ea4c841fef67d662d40f1e -- 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 18260] New: Quicktime 2 installer exits silently
by wine-bugs＠winehq.org Sept. 18, 2026

Sept. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=18260 Summary: Quicktime 2 installer exits silently Product: Wine Version: 1.1.20 Platform: PC URL: http://www.oldversion.com/download/quicktime212.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Created an attachment (id=20783) --> (http://bugs.winehq.org/attachment.cgi?id=20783) Wine 1.1.20 +relay +seh +tid (last 3MB) Installer from Quicktime 2.1.2 exits silently. Apparently the only available version is from oldversion.com However, I also have a copy that comes with another app that installs fine. It *might* have something to do with the lzexpand DLLs. Failing version prints these lines and then exits: trace:loaddll:NE_FreeModule Unloaded module "LZEXPAND.DLL" : builtin trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\lzexpand.dll16" : builtin trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\lz32.dll" : builtin Whereas the working version prints this line and continues: trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\lz32.dll" : builtin I can upload the working version too if needed. -- 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.

3 36

[Bug 45104] New: OOB read in gdiplus
by wine-bugs＠winehq.org Sept. 18, 2026

Sept. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=45104 Bug ID: 45104 Summary: OOB read in gdiplus Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: robert.gawlik(a)rub.de Distribution: --- Original submitted report can be found here: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1764719 (*) Out-of-bounds read in dlls/gdiplus/metafile.c:2528 (last commit: dd2624a24fba400bf59b9396e496d16c43d399d9): The parameters data, dataSize and recordType are completely user controlled and flow into a memcpy() call in line 2528. If the length of data is less than dataSize, then this results in an out-of-bounds read. 2461 GpStatus WINGDIPAPI GdipPlayMetafileRecord(GDIPCONST GpMetafile *metafile, 2462 EmfPlusRecordType recordType, UINT flags, UINT dataSize, GDIPCONST BYTE *data) 2463 { .... 2471 2472 if (recordType >= 1 && recordType <= 0x7a) 2473 { 2474 /* regular EMF record */ 2475 if (metafile->playback_dc) 2476 { 2477 switch (recordType) 2478 { .... 2520 default: 2521 { 2522 ENHMETARECORD *record = heap_alloc_zero(dataSize + 8); // <== dataSize is completely user controlled 2523 2524 if (record) 2525 { 2526 record->iType = recordType; 2527 record->nSize = dataSize + 8; 2528 memcpy(record->dParm, data, dataSize); // <== data is user controlled, memcpy performs OOB read 2529 2530 if(PlayEnhMetaFileRecord(metafile->playback_dc, metafile->handle_table, 2531 record, metafile->handle_count) == 0) // (record is user controlled => source of many vulnerabilities) 2532 ERR("PlayEnhMetaFileRecord failed\n"); If you need more information (EMF trigger file, etc.) let me know! -- 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 26758] New: Makefile system does not respect AS variable
by wine-bugs＠winehq.org Sept. 18, 2026

Sept. 18, 2026

http://bugs.winehq.org/show_bug.cgi?id=26758 Summary: Makefile system does not respect AS variable Product: Wine Version: 1.3.17 Platform: x86 OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: cdavis(a)mines.edu As part of building Wine DLLs an executables, Winebuild generates assembly files that are then assembled. If an assembler is specified using --as-cmd, that program is used; otherwise the system assembler is used. Wine's build system, unfortunately, does not allow the user to set the assembler to pass to winebuild. The usual way to set the assembler to use is to set the AS variable, but the build system does not respect it. This is a problem, for example, on Mac OS X when building with Clang with its integrated assembler turned on. Clang's integrated assembler supports .cfi directives, but the system assembler doesn't. During configure, a test file containing .cfi directives is passed to the compiler, on the assumption that it would be then passed to the system assembler. With Clang's integrated assembler, this assumption is broken. Thus, when winebuild tries to assemble files containing .cfi directives (because it believes that the system assembler supported them), it fails as a result. A workaround is to tell winebuild to use Clang to assemble, but the Makefile system doesn't support that. -- 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 6

[Bug 48078] New: Astro Avenger 2 fails to run with seh:setup_exception_record stack overflow
by WineHQ Bugzilla Sept. 18, 2026

Sept. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=48078 Bug ID: 48078 Summary: Astro Avenger 2 fails to run with seh:setup_exception_record stack overflow Product: Wine Version: 4.19 Hardware: x86-64 URL: https://astro-avenger.en.softonic.com/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iodreamify(a)gmail.com Distribution: Ubuntu Created attachment 65628 --> https://bugs.winehq.org/attachment.cgi?id=65628 winedebug warn+all log Astro Avenger 2 manages to launch but clicking "Run" in the launcher makes the game freeze forever with a "002a:err:seh:setup_exception_record stack overflow 816 bytes in thread 002a eip 00ac1926 esp 00231000 stack 0x230000-0x231000-0x330000" error. Tried it both in 64bit and 32bit prefixes in windows 7, XP, 2000 and 98 modes and also disabling csmt.I've added a winedebug=warn+all log below. A demo 60 min trial can be found at the link above. I've also done a +relay log but i'm not sure if it's relevant. 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.

2 6

[Bug 33126] New: divided SysEx and coalesced midiOutLongMsg
by wine-bugs＠winehq.org Sept. 16, 2026

Sept. 16, 2026

http://bugs.winehq.org/show_bug.cgi?id=33126 Bug #: 33126 Summary: divided SysEx and coalesced midiOutLongMsg Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: winealsa.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net Classification: Unclassified Johannes Kroll reported in wine-patches that the KORG Kontrol Editor software hung after sending an ill-formed SysEx via winealsa's midiOutLongMsg. http://www.winehq.org/pipermail/wine-patches/2013-January/121335.html The MIDIHDR data is F0 ... F7 00 00 00 (125 bytes). http://www.winehq.org/pipermail/wine-devel/2013-February/098852.html He observed that no hang occurs when skipping the trailing 3 zero bytes. F7 is the "End Of SysEx" (EOX) marker. It is still unclear what happens. MIDI HW is expected to skip over bogus bytes, thus the zero bytes should cause no harm. OTOH, ALSA might be getting into trouble processing ill-formed messages, and we don't know if or how many bytes ALSA actually sent out through the serial port. In any case, midiOutLongMsg handling in Wine needs fixes. - winealsa should extract the F0...F7 part and send that as a SysEx. - More generally, midiOutLong is known to accept not only SysEx packets, but also coalesced status messages. Some MIDI authors prefer to send e.g. chords via one LongMsg rather than successive calls to midiOutShortMsg, arguing that it's faster. Hence all Wine MIDI drivers need to decompose midiOutLongMsg into packets consisting of status message, regular SysEx ... and possibly junk. - All APIs (MS, ALSA, OSS, CA) acknowledge the existence of divided SysEx. As a result, framing SysEx with F0 ... F7 is entirely under application control. The current winealsa framing code is simply wrong. - winecoreaudio always declared 3 bytes for short messages, even program change. I have written a sequence of patches to fix all of this. The only thing that is unclear is how to encapsulate garbage data like the above 3 zero bytes or real time messages with ALSA. What ALSA API function and what ALSA message type to use? Heck, I'm not even sure winealsa.drv/midi.c:modData is ok to send a 2-byte MTC quarter frame via snd_seq_ev_set_sysex instead of using a primitive that sets the type SND_SEQ_EVENT_CLOCK/TICK. -- 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.

3 5

[Bug 46871] New: err:rpc: rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87
by wine-bugs＠winehq.org Sept. 15, 2026

Sept. 15, 2026

https://bugs.winehq.org/show_bug.cgi?id=46871 Bug ID: 46871 Summary: err:rpc:rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87 Product: Wine Version: 4.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)earthlink.net Distribution: --- Created attachment 63932 --> https://bugs.winehq.org/attachment.cgi?id=63932 NaturallySpeaking 13 setup log When installing Dragon NaturallySpeaking 13, the installation hangs up right at the last instruction. A prior bug 46160 was filed about NatSpeak 13 hanging up at the end of installation, and I think that bug might have been fixed in the most recent wine version, and this other bug uncovered. bug 46160 Anyway, the installation stops as of this: err:rpc:rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87 I have posted the installation log. If I kill the installation and then try to start the program, the program works up to a point. It waves hello, and then asks if I want to register the program immediately or run it up to 5 times without registering. When I hit either of these options, the program crashes. I have included the crash log also. -- 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 13

[Bug 35128] New: Air Conflicts (Pacific Carriers/Secret Wars) hangs at the loading screen
by wine-bugs＠winehq.org Sept. 14, 2026

Sept. 14, 2026

http://bugs.winehq.org/show_bug.cgi?id=35128 Bug ID: 35128 Summary: Air Conflicts (Pacific Carriers/Secret Wars) hangs at the loading screen Product: Wine Version: 1.7.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Classification: Unclassified Created attachment 46858 --> http://bugs.winehq.org/attachment.cgi?id=46858 terminal output I have this bug with both games from the Air Conflicts series when running under Wine. The native Linux version of AC:Pacific Carriers (running under the Linux version of Steam) doesn't have the problem. Also, running the Windows version in Virtualbox doesn't have the problem. The problem: the game starts fine and mouse/keyboard work as expected in the menus, but when I start a mission the game is stuck in the loading screen. The game is not completely dead because game tips are cycling through on the screen and the text 'Press any key to continue' is flashing, but the game doesn't accept mouse or keyboard input any more so I can't get in the game. The ACPC.exe process is consuming 30-40% cpu, but nothing happens, I have to kill the process to exit. Fedora 19 Nvidia binary drivers 325.15 X.Org X Server 1.14.4 -- 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 17

[Bug 49747] New: ICO_ExtractIconExW causes crash on incomplete windows executable
by WineHQ Bugzilla Sept. 12, 2026

Sept. 12, 2026

https://bugs.winehq.org/show_bug.cgi?id=49747 Bug ID: 49747 Summary: ICO_ExtractIconExW causes crash on incomplete windows executable Product: Wine Version: 5.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: andi(a)notmuch.email Distribution: --- Created attachment 68049 --> https://bugs.winehq.org/attachment.cgi?id=68049 backtrace of explorer.exe crashing I have 31% of a binary in a local directory because some installer/patcher crashed during installation. Whenever I use `winefile` or `wine explorer.exe` and scroll to that file in the directory wine crashes with the attached backtrace. It appears to be related to the ICO handling code within wine that expects more input but that doesn't exist yet. Attached is the backtrace of running the patcher for the "Dark Age of Camelot" freeshard "Phoenix" (https://playphoenix.online) which did cause this issue for me. -- 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 7