April 2007 - Wine-bugs - list.winehq.org

[Bug 3689] Microsoft Office 97 fails to install: "accwiz.dll failed to register itself"
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=3689 ------- Additional Comments From gon(a)pcbsd.org 2007-12-04 12:01 ------- I know its soooo dirty but for those people that doesnt know how to fix this: I copied the DLL: cp OS/SYSTEM/ACCWIZ.DLL /home/pcbsd/.wine/drive_c/windows/system32/Accwiz.dll I installed the MSOffice97 program (I tried this with all wine 0.9.3x and win98/xp): wine SETUP.EXE --->Some errors given and ignored. As Accwiz.dll shows me a little window telling me that the dll cant register himself, I used a command to register it manually: wine regsrv32.exe Accwiz.dll (from Accwiz.dll folder in system32) Once all its done, I had to run more than twice the WINWORD.EXE (ie) in order to stop warnings (the first one was about missing files, the second one about serial problem and the third one about..dunno) Up to the third time I run it, goes perfectly. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 8030] Need for Speed Carbon crashed after game starts
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=8030 ------- Additional Comments From thunder.m(a)czela.net 2007-12-04 11:31 ------- Created an attachment (id=5753) --> (http://bugs.winehq.org/attachment.cgi?id=5753&action=view) Log file with wine 120407 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 8030] New: Need for Speed Carbon crashed after game starts
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=8030 Summary: Need for Speed Carbon crashed after game starts Product: Wine Version: CVS Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: thunder.m(a)czela.net Need for Speed Carbon crashed after and change resolution to 640x480. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7434] 3DMark 2005 crashes after first test
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=7434 ------- Additional Comments From thunder.m(a)czela.net 2007-12-04 11:23 ------- Hi, this is fixed in current CVS (120407), but 3DMark 2006 still crashing after first test. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 8029] Heart of Darkness doesn't run or output any error.
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=8029 ------- Additional Comments From zajec5(a)gmail.com 2007-12-04 11:12 ------- Created an attachment (id=5752) --> (http://bugs.winehq.org/attachment.cgi?id=5752&action=view) Result of WINEDEBUG=warn+all wine ./HODWin32.exe 2> ~/hod.wine.log -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 8029] New: Heart of Darkness doesn't run or output any error.
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=8029 Summary: Heart of Darkness doesn't run or output any error. Product: Wine Version: 0.9.34. Platform: PC OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: zajec5(a)gmail.com I installed Heart of Darness without any problem. When I try to run it nothing happens, and console doesn't give any errors. Is looks like that: wine HODWin32.exe preloader: Warning: failed to reserve range 00000000-60000000 Then it hangs and nothing happen. I am not sure if it is usefull bug I made WINEDEBUG=warn+all wine ./HODWin32.exe 2> ~/hod.wine.log bzip2 ~/hod.wine.log Component "wine-misc" is probably incorrect but I don't know which one is OK. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 2398] OpenGL is only used on top level windows so child windows get overdrawn
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=2398 ------- Additional Comments From florianskarten(a)web.de 2007-12-04 10:22 ------- OpenGL still overdraw the GUI in the Warcraft 3 World Editor with patch http://bugs.winehq.org/attachment.cgi?id=5708. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 7909] Photoshop 5.0 crashes
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=7909 ------- Additional Comments From focht(a)gmx.net 2007-12-04 10:05 ------- Hello again, some update and possible solution :) Seems i misinterpreted returned X11DRV_GetAsyncKeyState() flag field. First call to X11DRV_GetAsyncKeyState() returns "rbutton down seen" (key is pressed + key got pressed since last time). All consecutive calls to X11DRV_GetAsyncKeyState() return "rbutton down seen" (key is pressed). No up state is reached/seen. After putting additional debugging code and trace messages it became obvious. --- trace --- trace:event:process_events ButtonPress for hwnd/window 0x10024/3a00001 trace:cursor:X11DRV_send_mouse_input before: (2) -> 0 trace:cursor:X11DRV_send_mouse_input after: (2) -> ffff8001 trace:event:process_events MotionNotify for hwnd/window 0x10024/3a00001 trace:cursor:X11DRV_MotionNotify hwnd 0x10024, event->is_hint 0 trace:cursor:X11DRV_send_mouse_input before: (2) -> ffff8001 trace:cursor:X11DRV_send_mouse_input after: (2) -> ffff8001 trace:event:process_events processed 2 events ... trace:key:X11DRV_GetAsyncKeyState before: (2) -> ffff8001 trace:key:X11DRV_GetAsyncKeyState after: (2) -> ffff8001 .... trace:key:X11DRV_GetAsyncKeyState before: (2) -> ffff8000 trace:key:X11DRV_GetAsyncKeyState after: (2) -> ffff8000 ... --- trace --- The problematic code is X11DRV_GetAsyncKeyState(). --- snip dlls/winex11.drv/keyboard.c --- SHORT X11DRV_GetAsyncKeyState(INT key) { SHORT retval; X11DRV_MsgWaitForMultipleObjectsEx( 0, NULL, 0, QS_KEY, 0 ); retval = ((key_state_table[key] & 0x40) ? 0x0001 : 0) | ((key_state_table[key] & 0x80) ? 0x8000 : 0); key_state_table[key] &= ~0x40; TRACE_(key)("(%x) -> %x\n", key, retval); return retval; } --- snip dlls/winex11.drv/keyboard.c --- Looking at the pseudo code from my posting earlier and you will know. The application basically "busy loops" using GetAsyncKeyState(). That means GetAsyncKeyState() has to handle not only keyboard but mouse button events too! In short: X11DRV_MsgWaitForMultipleObjectsEx( 0, NULL, 0, QS_KEY ...) is not enough, it filters out mouse button state messages (button down/up). Modify the filter to "QS_KEY | QS_MOUSEBUTTON" (dont use QS_ALLINPUT!) --- snip dlls/winex11.drv/keyboard.c --- SHORT X11DRV_GetAsyncKeyState(INT key) { SHORT retval; X11DRV_MsgWaitForMultipleObjectsEx( 0, NULL, 0, QS_KEY | QS_MOUSEBUTTON, 0 ); retval = ((key_state_table[key] & 0x40) ? 0x0001 : 0) | ((key_state_table[key] & 0x80) ? 0x8000 : 0); key_state_table[key] &= ~0x40; TRACE_(key)("(%x) -> %x\n", key, retval); return retval; } --- snip dlls/winex11.drv/keyboard.c --- Now it handles mouse button input too - which updates the key_state_table used by X11DRV_GetAsyncKeyState(). I tested with photoshop 5.5 tril and it worked like a charm, lockup gone, context menu shows up on right mouse click :) If any other applications/versions suffer from this one, please retest it using this workaround. Regards. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7910] Dreamfall Yellow Menu
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=7910 ------- Additional Comments From Wouter_Cox(a)yahoo.co.uk 2007-12-04 08:26 ------- I can confirm this. Both Wine 0.9.33 and 0.9.34 have this problem. I believe this problem was introduced in either Wine 0.9.32 or 0.9.33 (sorry I did not keep notes when it changed). Currently I am using 0.9.34 currently and this happens in all menus as well as on the intro screen. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 7909] Photoshop 5.0 crashes
by Wine Bugs 12 Apr '07

12 Apr '07

http://bugs.winehq.org/show_bug.cgi?id=7909 ------- Additional Comments From focht(a)gmx.net 2007-12-04 07:54 ------- Hello, your observation is correct. I used ps 5.5 trial + latest wine snapshot. The following pseudo code snippet illustrates the lockup in photoshop (made up from disassembly): --- pseudo code --- bool some_app_class::waitMouseRButtonUp( int& x, int& y) { // right mouse button up ? if( ::GetAsyncKeyState( ::GetSystemMetrics(SM_SWAPBUTTON) ? VK_LBUTTON : VK_RBUTTON) & 0x8000) == 0x8000) { // right mouse button still down, wait until up while( ::GetAsyncKeyState( ::GetSystemMetrics(SM_SWAPBUTTON) ? VK_LBUTTON : VK_RBUTTON) & 0x8000) == 0x8000); } if ( m_hwnd != 0) { MSG msg; if( !::PeekMessage (&msg, m_hwnd, WM_RBUTTONUP, WM_RBUTTONUP, PM_REMOVE)) return false; POINT pt = { GET_X_LPARAM( msg.lParam), GET_Y_LPARAM( msg.lParam) }; ::ClientToScreen( m_hwnd, &pt); x = pt.x; y = pt.y; } return true; } --- pseudo code --- Running "WINEDEBUG=+key,+msg" shows following sequence: --- trace --- trace:msg:WINPROC_CallProcWtoA (hwnd=0x20196,msg=WM_SETCURSOR,wp=00020196,lp=02040001) trace:msg:WINPROC_CallProcWtoA (hwnd=0x4002e,msg=WM_SETCURSOR,wp=00020196,lp=02040001) trace:msg:WINPROC_CallProcWtoA (hwnd=0x10026,msg=WM_SETCURSOR,wp=00020196,lp=02040001) trace:msg:WINPROC_CallProcWtoA (hwnd=0x10024,msg=WM_SETCURSOR,wp=00020196,lp=02040001) trace:key:X11DRV_GetAsyncKeyState (2) -> ffff8001 trace:key:X11DRV_GetAsyncKeyState (10) -> 0 trace:key:X11DRV_GetAsyncKeyState (12) -> 0 trace:key:X11DRV_GetAsyncKeyState (11) -> 0 trace:msg:WINPROC_CallProcWtoA (hwnd=0x20196,msg=WM_NCHITTEST,wp=00000000,lp=00a3011a) trace:key:X11DRV_GetAsyncKeyState (20) -> 0 trace:key:X11DRV_GetAsyncKeyState (10) -> 0 trace:key:X11DRV_GetAsyncKeyState (20) -> 0 trace:key:X11DRV_GetAsyncKeyState (12) -> 0 trace:key:X11DRV_GetAsyncKeyState (11) -> 0 trace:key:X11DRV_GetAsyncKeyState (2e) -> 0 trace:key:X11DRV_GetAsyncKeyState (8) -> 0 trace:key:X11DRV_GetAsyncKeyState (1b) -> 0 trace:key:X11DRV_GetAsyncKeyState (10) -> 0 trace:key:X11DRV_GetAsyncKeyState (12) -> 0 trace:key:X11DRV_GetAsyncKeyState (11) -> 0 trace:msg:WINPROC_CallProcWtoA (hwnd=0x20196,msg=WM_NCHITTEST,wp=00000000,lp=00a3011a) trace:key:X11DRV_GetAsyncKeyState (20) -> 0 trace:key:X11DRV_GetAsyncKeyState (12) -> 0 trace:key:X11DRV_GetAsyncKeyState (2) -> ffff8000 trace:key:X11DRV_GetAsyncKeyState (2) -> ffff8000 .... <continues endlessly> --- trace --- The rbutton up event shows up first (trace:key:X11DRV_GetAsyncKeyState (2) -> ffff8001), No previous rbutton down event is seen. The offending code in photoshop is executed after seeing second WM_NCHITTEST message. Due to "trace:key:X11DRV_GetAsyncKeyState (2)" returning "rbutton down" state all the time, it loops forever (see "while" loop in code). Maybe some kind of race condition or missed mouse event/update (X11DRV_MsgWaitForMultipleObjectsEx)... Sidenote: While debugging/killing the hanging app, wine x11 subsystem killed my window borders (decorator/compiz) several times. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0