February 2018 - Wine-Bugs - list.winehq.org

[Bug 30594] New: Mak of eternity crashes with DirectDraw mode.
by wine-bugs＠winehq.org Sept. 28, 2026

Sept. 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=30594 Bug #: 30594 Summary: Mak of eternity crashes with DirectDraw mode. Product: Wine Version: 1.5.3 Platform: x86 URL: http://www.download.com/King-s-Quest-The-Mask-of-Etern ity/3000-7564_4-10025133.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: jeremielapuree(a)yahoo.fr Classification: Unclassified Created attachment 40030 --> http://bugs.winehq.org/attachment.cgi?id=40030 Backtrace with ddraw channel enabled. Mak of eternity crashes with DirectDraw mode. With Direct3D mode, the game starts. -- 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 13

[Bug 25329] New: Divinity II demo fails to start gameplay screen unless I winetricks wmp9
by wine-bugs＠winehq.org Sept. 28, 2026

Sept. 28, 2026

http://bugs.winehq.org/show_bug.cgi?id=25329 Summary: Divinity II demo fails to start gameplay screen unless I winetricks wmp9 Product: Wine Version: 1.3.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: shannon.vanwagner(a)gmail.com Divinity2 demo starts to character creation but won't launch gameplay. So after installing winetricks wmp9, the introductory videos play and the game runs. -- 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 46

[Bug 35848] New: Sound, Black Screen then crash
by wine-bugs＠winehq.org Sept. 27, 2026

Sept. 27, 2026

http://bugs.winehq.org/show_bug.cgi?id=35848 Bug ID: 35848 Summary: Sound, Black Screen then crash Product: Wine Version: 1.7.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adec2010(a)hotmail.co.uk Killing Time. After installation, set to windows 95 compatibility. It runs with a black screen. I can hear sound but then a crash back to the desktop -- 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 10

[Bug 27336] New: Starcraft 2: Broken Sound
by wine-bugs＠winehq.org Sept. 23, 2026

Sept. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=27336 Summary: Starcraft 2: Broken Sound Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mmdevapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: aeneas(a)q-mail.me Since wine 1.3.19 the sound in StarCraft 2 as well as in other games (see comments from http://appdb.winehq.org/objectManager.php?sClass=version&iId=20882 ) is very broken. It has a lot of glitches and crashes very often. If it crashes, I have to select another Sound Device in the StarCraft settings to enable the sound again. Pre 1.3.19 using a mmdevapi override (disabled) was enough to enable sound. I report this using ALSA as my sound driver. eSound actually works pretty well but has a latency of about 0.6 - 0.8 seconds which is very anoying If you need any further information, like logs or something please contact me. -- 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 15

[Bug 41355] New: Microsoft Access 2007 is not opening a legitimate access file
by wine-bugs＠winehq.org Sept. 22, 2026

Sept. 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=41355 Bug ID: 41355 Summary: Microsoft Access 2007 is not opening a legitimate access file Product: Wine Version: 1.6-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: santanu_chatterjee59(a)yahoo.co.in Distribution: --- Created attachment 55706 --> https://bugs.winehq.org/attachment.cgi?id=55706 Microsoft Access 2007 is not opening a legitimate access file Microsoft Access 2007 is not opening a legitimate access field -- 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 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 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 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 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 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