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

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

Sept. 11, 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 20

[Bug 18260] New: Quicktime 2 installer exits silently
by wine-bugs＠winehq.org Sept. 11, 2026

Sept. 11, 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 35

[Bug 25723] New: PhysX causes major lag in Mirror's Edge.
by wine-bugs＠winehq.org Sept. 8, 2026

Sept. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=25723 Summary: PhysX causes major lag in Mirror's Edge. Product: Wine Version: 1.3.11 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: H3g3m0n(a)gmail.com When the PhysX option is enabled (setting in the Video Options) in Mirror's Edge. When 'physics' things start to occur the game starts to get some major lag becoming unplayable. Mirror's Edge doesn't make too much use of PhysX (I believe it was on of the first games with support for it), afaik it's mostly used for enabling shattering glass to create shards and maybe some bits of paper on the ground. As such this only seems to happen at specific points in the game. For example Chapter 1 Flight->Check Point D. As you are running across the bridge, the helicopter starts to shoot the glass causing it to shatter. If you continue on to the next area, at some point (when you go underground) it suddenly returns to normal speed (most likely it has unloaded the previous area). With PhysX set to off, there is no lag but no glass shards. -- 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 22

[Bug 23364] New: 16-bit games - many don't work in Wine.
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=23364 Summary: 16-bit games - many don't work in Wine. Product: Wine Version: 1.1.42 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: turbolad995(a)hotmail.co.uk As I have not found a bug report for this already I've decided to create one myself. Many 16-bit games, especially the old Windows 3.1 games like "whack-a-mole", "Bricklayer" and many others I've tried simply don't work at all in Wine. Since there's too many 16-bit games to list, it makes sense to write one bug report covering the same problem i.e. problems running 16-bit games. Try some yourself from here: http://members.chello.at/theodor.lauppert/games/win16.htm Here I've found that the 32-bit version of tetris works in Wine, but the 16-bit version does NOT work at all (try it yourself from this link, you get to download both the 32-bit and 16-bit versions respectively, at the bottom of that page): http://members.chello.at/theodor.lauppert/games/tetrisjr.htm I'm pleased to say that the Ballistic (Paddle) game appears to work: http://www.classicdosgames.com/genre/paddle.html This bug report may appear trivial and not important, but playing old Windows games appeals to some people. These games will NOT work in dosbox. Also consider that 64-bit versions of Microsoft Windows won't even run 16-bit programs and games, whereas Wine can sometimes get them working, as in the case of the Ballistic game. -- 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 19

[Bug 25373] New: epoc32 emulator don't start
by wine-bugs＠winehq.org Sept. 4, 2026

Sept. 4, 2026

http://bugs.winehq.org/show_bug.cgi?id=25373 Summary: epoc32 emulator don't start 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: daniele(a)smartango.com $ env WINEPREFIX="/home/daniele/.wine" wine "C:\\Symbian\\9.1\\S60_3rd_MR\\Epoc32\\Release\\Winscw\\Udeb\\Epoc.exe" fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x59cd818: stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex (0x59cd850) stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex ((nil)) stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x59cd818: stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex (0x59cd850) stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex ((nil)) stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x59cd818: stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex (0x59cd850) stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex ((nil)) stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x59cd818: stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex (0x59cd850) stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex ((nil)) stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x59cd818: stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex (0x59cd850) stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex ((nil)) stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x59cd818: stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex (0x59cd850) stub fixme:ntoskrnl:__regs_ExTryToAcquireFastMutex ((nil)) stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0xffffff01: stub err:mmtime:TIME_MMTimeStop Timer still active?! $ strace env WINEPREFIX="/home/daniele/.wine" wine "C:\\Symbian\\9.1\\S60_3rd_MR\\Epoc32\\Release\\Winscw\\Udeb\\Epoc.exe" 2>mylog.txt I attach strace (fist time I report a bug here, I think strace could be useful ...) -- 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 18790] New: Default search does not include resolved bugs
by wine-bugs＠winehq.org Aug. 31, 2026

Aug. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=18790 Summary: Default search does not include resolved bugs Product: WineHQ Bugzilla Version: unspecified Platform: PC OS/Version: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P3 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk The default search (the search box at the top of this page) does not include closed bugs (rightly so), but it also does not include resolved bugs. This leads to duplicates that could be avoided. See Bug 18601 - a recent regression that is fixed by the next release, but anyone searching for an open bug for Google Sketchup will not see it unless they choose to run an advanced search, which some users clearly don't. I'm sure this is a simple change to the code. -- 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 10

[Bug 26758] New: Makefile system does not respect AS variable
by wine-bugs＠winehq.org Aug. 30, 2026

Aug. 30, 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 5

[Bug 16179] New: QIP: flashing chat window disappears if it is not on the current desktop.
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=16179 Summary: QIP: flashing chat window disappears if it is not on the current desktop. Product: Wine Version: unspecified Platform: PC-x86-64 URL: http://qip.ru/en/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: crossroads0000(a)gmail.com If QIP tries to flash one of its chat windows while the user is on another desktop, the chat window disappears completely until I restart the application. The problem also comes up when you change desktops while the window is flashing. No error logs are attached because there is no output in the console if the bug appears. To reproduce the crash: 1) Download QIP (e.g. at http://qip.ru/download/qip/?http://download.qip.ru/qip8070.exe ). 2) Start QIP. If it fails to start (this is a bug unrelated to this one), try this work-around: go to your QIP-Directory (should be ~/.wine/drive_c/Program\ Files/QIP), open current.cfg in your "Skins" directory, and replace "1" with "0". 3) Log on with your ICQ #. If you don't have one, you can easily register one with QIP in less than 30 seconds (you don't have to enter any email address). 4) Open the chat window, make someone send you a chat message, but before you receive it, change the desktop. 5) If you receive a message while you're on another desktop, the chat window will disappear. This only works if the chat window had focus before you changed the desktop. -- 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 11

[Bug 21539] New: Using "Bare Streams" console mode with SRCDS does not work.
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=21539 Summary: Using "Bare Streams" console mode with SRCDS does not work. Product: Wine Version: 1.1.37 Platform: x86 URL: http://srcds.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: laurikoivunen(a)hotmail.com SRCDS ( Source Dedicated Server ) is designed to run both in GUI and CLI modes. However, when trying to run the server in pure console without X and using "bare streams" as described here ( http://www.winehq.org/docs/wineusr-guide/cui-programs ) I still receive the error: DISPLAY='' WINEDEBUG=+console wine srcds.exe -console ... trace:console:AllocConsole () err:curses:WCCURSES_InitBackend (n)curses was not found. err:wineconsole:WINECON_Init failed to init. This is probably due to srcds running in "hybrid" mode where it is marked as a GUI application, but uses AllocConsole to create a console hence resulting in a new console creation, which currently fails. As a workaround I stubbed AllocConsole and only returned TRUE. This allows the application to start and reach a point where it tries to read the console and where it then fails due to wine not being able to read from the console. Could you add an option for true "bare streams" and so that input would also work? ps: I know that there is a linux version of SRCDS but there are no linux binaries for the server I am trying to run. This bug forces a lot of server hosters run X on their servers to be able to run SRCDS in wine. The server is free to download and use. -- 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 8

[Bug 28236] New: unable to activate windows input method for wine programs
by wine-bugs＠winehq.org Aug. 29, 2026

Aug. 29, 2026

http://bugs.winehq.org/show_bug.cgi?id=28236 Summary: unable to activate windows input method for wine programs Product: Wine Version: 1.3.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com 1. Install Services Framework Redist files Download instMSTSF.exe (Services Framework Redist files) from http://www.microsoft.com/download/en/details.aspx?DisplayLang=en&id=11759 extract instMSTSF.exe, install mstsf10.exe with Windows Version = Win2k override native msctf.dll, avoid Bug 28125 2. install a input method, for example, MSPY2010.exe (Chinese input method from Microsoft) : Download MSPY2010.exe from http://www.microsoft.com/china/pinyin/ and install. winetricks vcrun2008, avoid Bug 28205 override newer version of native msutb.dll, avoid Bug 28178 3. start notepad in a terminal, start ctfmon.exe in another terminal $ wine notepad $ wine ctfmon.exe 4.try to change the input method in the Language Bar, however, the windows input method will not be activated as expect. Try to type something in notepad, but result is still the same as raw keyboard input without any input method. log for notepad and ctfmon are both attached. -- 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 7