June 2014 - Wine-Bugs - list.winehq.org

[Bug 35349] New: NC Corrector spams terminal with "fixme:olepicture:OLEPictureImpl_SaveAsFile"
by wine-bugs＠winehq.org Feb. 26, 2025

Feb. 26, 2025

http://bugs.winehq.org/show_bug.cgi?id=35349 Bug ID: 35349 Summary: NC Corrector spams terminal with "fixme:olepicture:OLEPictureImpl_SaveAsFile" Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: plaes(a)plaes.org Classification: Unclassified `NC Corrector 4.0` from http://www.nc-corrector.inf.ua/index_EN.htm spams following continuously in the terminal: [snip] ... fixme:olepicture:OLEPictureImpl_SaveAsFile (0x1fe9b0)->(0x19ad098, 0, (nil)), hacked stub. fixme:olepicture:OLEPictureImpl_SaveAsFile (0x2064d8)->(0x19ad098, 0, (nil)), hacked stub. .... [/snip] This could be also duplicate for #20222 -- 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 18959] New: MetaTrader 4 installer hangs at the very end of file extraction
by wine-bugs＠winehq.org Feb. 24, 2025

Feb. 24, 2025

http://bugs.winehq.org/show_bug.cgi?id=18959 Summary: MetaTrader 4 installer hangs at the very end of file extraction Product: Wine Version: 1.1.23 Platform: PC URL: http://www.metatrader4.com/files/mt4setup.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt AssignedTo: wine-bugs(a)winehq.org ReportedBy: arethusa26(a)gmail.com CC: julliard(a)winehq.org With today's Git (wine-1.1.23-221-gafce86b), the MetaTrader installer hangs at the very end of file extraction at "C:\Program Files\MetaTrader 4\mailbox\1190736044.english" with sufficient responsiveness to handle the Cancel button being pressed, which merely hides the installer window until a Ctrl+C interrupt is sent to the installer. The installer worked properly in 1.0.1, and the regression test revealed: 1c91d54503f9b2afa513dc4dd79bf19bc9bad51a is first bad commit commit 1c91d54503f9b2afa513dc4dd79bf19bc9bad51a Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Feb 18 14:44:17 2009 +0100 msvcrt: Don't try to duplicate invalid handles. Don't reset std handles if we didn't set them. :040000 040000 2abf5f9a82de1d29b1fccadc658fc3a956388ac4 86464380dfe4aca4c5c11ea2a539a1fc5def03b8 M dlls Reverting the commit in HEAD allows the installer to start. -- 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 32

[Bug 36781] New: palringo: The Chat Box view not txt !!
by wine-bugs＠winehq.org Feb. 23, 2025

Feb. 23, 2025

http://bugs.winehq.org/show_bug.cgi?id=36781 Bug ID: 36781 Summary: palringo: The Chat Box view not txt !! Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmedsaber20005(a)gmail.com Created attachment 48850 --> http://bugs.winehq.org/attachment.cgi?id=48850 Log of palringo crash when i want to chat with someone the palringo not show any text :/ and some times it is crash -- 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 4

[Bug 33211] New: C&C: Red Alert 2 still runs very slowly and mouse cursor flickers
by wine-bugs＠winehq.org Feb. 22, 2025

Feb. 22, 2025

http://bugs.winehq.org/show_bug.cgi?id=33211 Bug #: 33211 Summary: C&C: Red Alert 2 still runs very slowly and mouse cursor flickers Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: brymaster(a)gmail.com Classification: Unclassified The game runs slowly, especially while moving the cursor in-game. I've tried various winetricks configs with: ddr=opengl/ddr=gdi, rtlm=readtex, orm=backbuffer as well as setting a flag in ra2.ini for [Video]VideoBackBuffer=no - nothing works. Even looked at a 'lag fix' here that does nothing: http://www.stuffhost.de/files/cnc/CnCPatcher.html >From looking at past related issues (http://bugs.winehq.org/show_bug.cgi?id=2784, http://bugs.winehq.org/show_bug.cgi?id=5526, http://bugs.winehq.org/show_bug.cgi?id=14438) I get the feeling that someone was trigger happy and 'CLOSED FIXED' these without actually testing - people are still reporting its a problem. -- 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 27

[Bug 24308] New: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object)
by wine-bugs＠winehq.org Feb. 21, 2025

Feb. 21, 2025

http://bugs.winehq.org/show_bug.cgi?id=24308 Summary: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object) Product: Wine Version: 1.3.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: georg298(a)gmx.de For all MechWarrior 4 games, fullscreen fails with message fixme:ddraw:d3d7_CreateDevice Only one Direct3D device per DirectDraw object supported. Obviously, the game falls back to window'ed mode, as static HRESULT WINAPI d3d7_CreateDevice(IDirect3D7 *iface, REFCLSID riid, IDirectDrawSurface7 *surface, IDirect3DDevice7 **device) returns DDERR_INVALIDPARAMS changing this behaviour (returning D3D_OK instead): if (ddraw->d3ddevice) { FIXME("Only one Direct3D device per DirectDraw object supported.\n"); LeaveCriticalSection(&ddraw_cs); return D3D_OK; // return DDERR_INVALIDPARAMS; } makes fullscreen work for these games. Probably it's not "legal" to return D3D_OK in this case, but maybe there is a real solution for this problem? -- 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 26

[Bug 10522] New: endless WM_PAINT loop bug (update regions, queue paint count)
by wine-bugs＠winehq.org Feb. 17, 2025

Feb. 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=10522 Summary: endless WM_PAINT loop bug (update regions, queue paint count) Product: Wine Version: CVS/GIT Platform: PC URL: http://www.microsoft.com/whdc/devtools/debugging/install x86.mspx OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=9265) --> (http://bugs.winehq.org/attachment.cgi?id=9265) trace with WINEDEBUG=+tid,+message,+win,+server Hello, I've seen this bug a while ago in other apps but ignored it because it was not easily to reproduce. Well until recently when I tested some stuff with windbg from "Debugging Tools for Windows" (Microsoft). I used debugging tools version 6.8.4.0 and recent GIT (wine-0.9.49-302-g58b85bb). Immediately when a child window was opened using toolbar (register, locals, .. whatever), windbg would become unresponsive, eating most CPU. Happens in both GUI modes - "floating/docking toolwindow" and "MDI emulation. Though "MDI emulation" is more obvious, it actually shows the endless refreshing (window caption). Attached is WINEDEBUG=+tid,+message,+win,+server log. Additionally I added a trace message which prints the current queue paint count (when incremented or fetched) which makes some things easier to spot. Printed as "inc_queue_paint_count: %d" and "get_message_paint_count: %d". The window hierarchy is as follows: --- snip --- *root*=0x10020 Shell_TrayWnd=0x10022 WinDbgFrameClass=0x10024 DockClass=0x10026 ToolbarWindow32=0x10028 msctls_statusbar32=0x1002a tooltips_class32=0x1002e WinBaseClass=0x10030 ToolbarWindow32=0x10032 SysListView32=0x10034 SysHeader32=0x10036 RichEdit20W=0x10038 --- snip --- After the child windows are created the queue paint count never drops to zero, resulting in endless WM_PAINT processing. Maybe some update (region) code path missed or flags problem? I played a bit with ignoring null region updates and it seemed to help a bit (preventing endless WM_PAINT loop) though other stuff wasn't drawn properly then. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 41

[Bug 30111] New: Crysis 2 ingame crashes
by wine-bugs＠winehq.org Feb. 16, 2025

Feb. 16, 2025

http://bugs.winehq.org/show_bug.cgi?id=30111 Bug #: 30111 Summary: Crysis 2 ingame crashes Product: Wine Version: 1.4-rc6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: christian.frank(a)gmx.de Classification: Unclassified Hi Guys, after getting the crysis2 loading issue fixed, i noticed that the game itself runs well, but very very unstable. The game simply crashes. The last i see on the console is (the d3d_texure fixme is repeatedly displayed all the time you play) fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x159925c8 stub! fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x15992338 stub! fixme:faultrep:ReportFault 0x32df20 0x0 stub fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x159925c8 stub! The sound of the game is still running but the process is [defunct]. Any ideas on how to debug this issue ? Any recommend traces ? I also noticed a freeze after a ingame video sequence. Many thanks, Christian -- 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 23

[Bug 21811] New: 3impact tech demo collection crashes on first demo
by wine-bugs＠winehq.org Feb. 16, 2025

Feb. 16, 2025

http://bugs.winehq.org/show_bug.cgi?id=21811 Summary: 3impact tech demo collection crashes on first demo Product: Wine Version: 1.1.39 Platform: x86 URL: http://www.3impact.com/ OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://www.3impact.com/3Impact_Engine/dyruk89b/3impact51_demo.exe is a set of demos showing mannekins flailing about and boulders rolling. Runs great on Vista. It installs fine on Wine. To start the app, do cd ~/".wine/drive_c/Program Files/3impact5demos" wine demos.exe skinnedragdoll.dll The first problem is bug 21790; do 'winetricks vcrun2005' to get past that. The next problem is a crash related to d3dx9_36.D3DXAssembleShaderFromResourceW, roughly bug 12020. Work around this with 'winetricks d3dx9'. The next problem is that full-screen mode doesn't work (bug 21791). Work around this by telling the demo to run in a window. This prompts you to press N, and then crashes after you do, with wine: Unhandled page fault on read access to 0x0000001c at address 0x431c10 (thread 0009), starting debugger... I'll attach a +relay,+seh log. -- 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 33295] New: Vietcong: Connecting to a multiplayer server does not work
by wine-bugs＠winehq.org Feb. 16, 2025

Feb. 16, 2025

http://bugs.winehq.org/show_bug.cgi?id=33295 Bug #: 33295 Summary: Vietcong: Connecting to a multiplayer server does not work Product: Wine Version: 1.5.26 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified Connecting to any multiplayer server in the server list will result in the phone sound that the connection has failed. Even servers with default maps (and logically compatible versions) does not work. -- 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 11718] New: d3d 2/3 blackout, world editor
by wine-bugs＠winehq.org Feb. 16, 2025

Feb. 16, 2025

http://bugs.winehq.org/show_bug.cgi?id=11718 Summary: d3d 2/3 blackout, world editor Product: Wine Version: 0.9.56. Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugzilla(a)gmail.com Created an attachment (id=10944) --> (http://bugs.winehq.org/attachment.cgi?id=10944) d3d 2/3 blackout Warcraft 3x world editor, version 1.21b (6052) The mouse cursor does not line up with the on screen cursor, thanks to 2/3 of the screen does not get draw. Trigger editor panel in wrong overlaps. (A pictures is worth a thousand words) -- 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 51