wine-bugs March 2011

wine-bugs@winehq.org

1 participants
8631 discussions

[Bug 25872] New: dxdiag doesn't support /t option, needed by Guild Wars 'test system' button
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=25872 Summary: dxdiag doesn't support /t option, needed by Guild Wars 'test system' button Product: Wine Version: 1.3.12 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com This is the next problem after bug 25871. Guild wars installs nicely, but if you press 'test system', you see ... fixme:dxdiag:ProcessCommandLine /t unimplemented -- 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 14

[Bug 19153] New: DX3 game does not recognize graphics capabilities
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=19153 Summary: DX3 game does not recognize graphics capabilities Product: Wine Version: 1.1.24 Platform: PC URL: http://appdb.winehq.org/objectManager.php?sClass=versi on&iId=9396 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: bobbyg(a)gmx.net Resident Evil 1 does not start giving the error "Failed to initialize the Graphics Hardware Device.(3)". It's a DirectX 3 game using immediate mode. After some debugging I found that it relies on 3 (three) entries returned by EnumDevices whereas wine returns only the Direct3D HAL entry in this case (d3dversion == 1). Removing the if-clause in ddraw/direct3d.c and duplicating the HAL entry solves the problem and the game actually runs almost perfectly (Garbage -> Platinum). I checked a Windows installation which returns "HAL", "RGB Emulation" and "Ramp Emulation" but the comments in the file suggest that not all games are happy about that. So how to fix this properly? -- 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 50

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

21 Feb '25

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 17 Feb '25

17 Feb '25

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 21811] New: 3impact tech demo collection crashes on first demo
by wine-bugs＠winehq.org 16 Feb '25

16 Feb '25

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 11718] New: d3d 2/3 blackout, world editor
by wine-bugs＠winehq.org 16 Feb '25

16 Feb '25

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

[Bug 16876] New: .NET 3.0: WIC installer hangs due to bug in property sheet control
by wine-bugs＠winehq.org 15 Feb '25

15 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=16876 Summary: .NET 3.0: WIC installer hangs due to bug in property sheet control Product: Wine Version: 1.1.12 Platform: Other URL: http://www.microsoft.com/downloads/details.aspx?FamilyID =10cc340b-f857-4a14-83f5-25634c3bf043 OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, after bug 16875 is fixed, there is another bug unearthed by WIC installer. Normally you won't notice it because the main installer claims success on this sub-installer. If you run WIC installer manually and press "finish" in last property page it simply hangs. Prerequisite: 1. clean WINEPREFIX 2. download .NET 3.0 Framework installer from: http://download.microsoft.com /download/4/d/a/4da3a5fa-ee6a-42b8-8bfa-ea5c4a458a7d/dotnetfx3setup.exe (sha1sum: a566bcd2ffffc3842a95adc57f7df3f8cd11577f) 3. export _SFX_CAB_SHUTDOWN_REQUEST=1 (workaround, see bug 9158) 4. wine ./dotnetfx3setup.exe It might take a while until all required packages are downloaded using BITS. Note: If you need to redo steps, backup the directory "dotnetfx304506.30" from "c:\\windows\\temp" to a different location, remove ~/.wine, copy "dotnetfx304506.30" again to "c:\\windows\\temp" to prevent BITS from downloading over and over again. There is a (ui) thread spawned to display and handle property sheet: --- snip --- 0084:Starting thread proc 0x1043904 (arg=(nil)) ... 0084:Call comctl32.CreatePropertySheetPageW(7ec515b4) ret=01045ccb ... 0084:Ret comctl32.CreatePropertySheetPageW() retval=00149568 ret=01045ccb ... 0084:Call comctl32.PropertySheetW(7ec516e0) ret=01045ffc 0084:Call KERNEL32.GlobalAlloc(00000040,00000084) ret=7763bc0e 0084:Ret KERNEL32.GlobalAlloc() retval=006026a8 ret=7763bc0e 0084:trace:propsheet:PropertySheetW (0x7ec516e0) 0084:trace:propsheet:PROPSHEET_CollectSheetInfoW ** PROPSHEETHEADER ** dwSize 52 dwFlags 01198100 hwndParent (nil) hInstance (nil) pszCaption L"\1828\7ec5" nPages 5 pfnCallback 0x1043cb1 ... 0084:trace:propsheet:PROPSHEET_PropertySheet startpage: 0 of 5 pages 0084:trace:propsheet:PROPSHEET_CreateDialog ... 0084:trace:propsheet:PROPSHEET_Finish active_page 4 ... 0084:trace:propsheet:PROPSHEET_CleanUp ... 0084:trace:propsheet:PROPSHEET_Finish msg result 0 ... 0084:Ret comctl32.PropertySheetW() retval=00000001 ret=01045ffc .. 0084:Call user32.GetMessageA(7ec519ec,00000000,00000000,00000000) ret=01043942 <hangs here> --- snip --- Relevant code: --- snip dlls/comctl32/propsheet.c --- static BOOL PROPSHEET_Finish(HWND hwndDlg) { .. if (psInfo->result == 0) psInfo->result = IDOK; if (psInfo->isModeless) psInfo->activeValid = FALSE; else psInfo->ended = TRUE; return TRUE; } --- snip dlls/comctl32/propsheet.c --- --- snip dlls/comctl32/propsheet.c --- static INT_PTR PROPSHEET_PropertySheet(PropSheetInfo* psInfo, BOOL unicode) { ... if(!psInfo->isModeless) { parent = psInfo->ppshheader.hwndParent; if (parent) EnableWindow(parent, FALSE); } bRet = PROPSHEET_CreateDialog(psInfo); if(!psInfo->isModeless) { bRet = do_loop(psInfo); if (parent) EnableWindow(parent, TRUE); } return bRet; } --- snip dlls/comctl32/propsheet.c --- --- snip dlls/comctl32/propsheet.c --- static INT do_loop(const PropSheetInfo *psInfo) { MSG msg; INT ret = -1; HWND hwnd = psInfo->hwnd; while(IsWindow(hwnd) && !psInfo->ended && (ret = GetMessageW(&msg, NULL, 0, 0))) { if(ret == -1) break; if(!IsDialogMessageW(hwnd, &msg)) { TranslateMessage(&msg); DispatchMessageW(&msg); } } if(ret == 0) { PostQuitMessage(msg.wParam); ret = -1; } if(ret != -1) ret = psInfo->result; DestroyWindow(hwnd); return ret; } --- snip dlls/comctl32/propsheet.c --- This propery sheet is modal. When the message pumps exits, the return value is derived from "psInfo->result" which is set to IDOK (button "finish") in PROPSHEET_Finish(). Unfortunately this tells the app the property sheet is modeless and it tries to setup it's own message pump after PropertySheetW() return which obviously hangs because the control is no more present at this time. Regards -- 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 22849] New: Printing coupons from online sites results in a blank coupon
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=22849 Summary: Printing coupons from online sites results in a blank coupon Product: Wine Version: 1.1.38 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tribes2player2003(a)yahoo.com Many stores / sites use a product called "coupon activator" to support online coupon distribution (Target on-line is my test case), but a quick net search reveals that many sites use this service. When printing should take place, the following messages are printed to console: fixme:psdrv:PSDRV_GetDeviceCaps (0x1f5c): unsupported capability 1, will return 0 fixme:psdrv:PSDRV_GetDeviceCaps (0x1f5c): unsupported capability 3, will return 0 ... (capability numbers go from 1 to 31). The coupon boarders, expiration date, and scissors icon print, but the internals of the coupon are blank (bar codes, images, etc). Steps to reproduce (using Default Fedora 12 wine install): - Install firefox on wine - Visit target.com, goto "get coupons" - Allow install of coupon activator - Select a coupon to print - Print If there's any additional steps I can take to help with this, please let me know. -- 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 9

[Bug 19386] New: Please provide single login for all websites of winehq.org portal.
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=19386 Summary: Please provide single login for all websites of winehq.org portal. Product: WineHQ.org Version: unspecified Platform: PC OS/Version: All Status: UNCONFIRMED Severity: major Priority: P5 Component: www-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: yurikoles(a)gmail.com For every website users must create new account. I think it's really annoying. -- 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 21

[Bug 17258] New: M.A.X.2 : error "Screen init failed" when starting the game
by wine-bugs＠winehq.org 26 Jan '25

26 Jan '25

http://bugs.winehq.org/show_bug.cgi?id=17258 Summary: M.A.X.2 : error "Screen init failed" when starting the game Product: Wine Version: 1.1.14 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jazzedupj0sh(a)gmail.com Created an attachment (id=19245) --> (http://bugs.winehq.org/attachment.cgi?id=19245) Game does not start, instead shows this error Installation works fine. This is a game meant for Windows 98. Not sure which version of Directx it uses. The game does not start, instead I get an error. The screenshot of the error is 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 33

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs March 2011