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

[Bug 39415] New: Make configuration settings accessible through the website
by wine-bugs＠winehq.org 21 Apr '20

21 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=39415 Bug ID: 39415 Summary: Make configuration settings accessible through the website Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently the way to change a configuration setting is to send a patch to wine-patches and have Alexandre apply it. This is the case for instance for all the VM host configuration settings ($MaxRevertingVMs, $MaxRevertsWhileRunningVMs, etc.), but also $JobPurgeDays, $RegistrationQ, etc. This is not very practical and prevents experimentation or quickly adjusting the settings when a problem arises. Instead these should be stored in a Parameters table and be accessible through an administrator-only section of the website. -- 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 3

[Bug 39416] New: Many settings should be per VM host
by wine-bugs＠winehq.org 21 Apr '20

21 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=39416 Bug ID: 39416 Summary: Many settings should be per VM host Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The following global settings should in fact be customizable on a per VM host basis: * $MaxRevertingVMs - Hosts with SSDs may be able to handle multiple reverts in parallel. * $MaxRevertsWhileRunningVMs - Again this may depend on disk speed and QEmu version. * $MaxActiveVMs - Depends on disk and CPU speed, number of cores, etc. * $SuiteTimeout & $SingleTimeout - Might need to be adjusted based on the CPU speed. * $BuildTimeout & $ReconfigTimeout - Might need to be adjusted based on the CPU speed. Fortunately we can currently only have one build VM so that's not too much of an issue. One way to do so would be to introduce a VMHosts table storing the settings for each VM host (see the schema attachment of bug 39412). VMs (VMInstances really) would then be linked to the relevant VM host so to indicate which set of constraints apply. Note that this would be different from the handling of the truly global settings described in bug 39415. -- 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 1

[Bug 48772] New: Attack on Titan 2 continually clips the cursor, resulting in incorrect cursor events
by WineHQ Bugzilla 21 Apr '20

21 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=48772 Bug ID: 48772 Summary: Attack on Titan 2 continually clips the cursor, resulting in incorrect cursor events Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com Distribution: --- For example: ... 0009:trace:cursor:SetCursor 0x20046 0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093) 0009:trace:cursor:ungrab_clipping_window no longer clipping 0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093) 0009:trace:cursor:ungrab_clipping_window no longer clipping 0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093) 0009:trace:cursor:ungrab_clipping_window no longer clipping ... 0009:trace:cursor:SetCursor 0x20046 0009:trace:cursor:X11DRV_MotionNotify hwnd 0x10052/4400003 pos 963,543 is_hint 0 serial 6080 0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093) 0009:trace:cursor:ungrab_clipping_window no longer clipping 0009:trace:cursor:X11DRV_MotionNotify hwnd 0x10052/4400003 pos 924,521 is_hint 0 serial 6083 00ce:trace:cursor:X11DRV_SetCursorPos warped to 960,540 serial 6413 001f:trace:cursor:X11DRV_EnterNotify hwnd 0x10020/3a0000a pos 921,509 detail 2 0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093) 0009:trace:cursor:ungrab_clipping_window no longer clipping 0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093) 0009:trace:cursor:ungrab_clipping_window no longer clipping ... Since the cursor is continually warped to the center of the screen, when ungrab_clipping_window calls XUnmapWindow, it reports to the game that the cursor has moved back to the center, resulting in the common "camera refuses to move" bug. Although the documentation[1] states that XUnmapWindow does nothing if called on a window that's already unmapped, when adding a variable to keep track of whether it's mapped or not and only unmapping it when needed, the issue is fixed. [1] https://tronche.com/gui/x/xlib/window/XUnmapWindow.html -- 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.

1 1

[Bug 34666] New: In The Adventures Of Lomax some graphic elements flicker, disappear or are garbled
by wine-bugs＠winehq.org 20 Apr '20

20 Apr '20

http://bugs.winehq.org/show_bug.cgi?id=34666 Bug #: 34666 Summary: In The Adventures Of Lomax some graphic elements flicker, disappear or are garbled Product: Wine Version: 1.7.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugs140(a)gmail.com Classification: Unclassified Created attachment 46209 --> http://bugs.winehq.org/attachment.cgi?id=46209 Lomax Log For example there is no transition between the main game screen and the next one. I mean, the black screen is displayed instead of a transition. The screen where you see Lomax and Evil Ed standing next to each other is garbled. When you begin the game the text message 'Let's go' flickers. There is also flickering when you press the space key to change your hat. The issues can be reproduced in the demo (check out the link). Tested with: Windows Vista (without Wine), GeForce 9600M GS--the program works fine here Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313) -- 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 12

[Bug 30506] New: Text misrendered in Brain Workshop
by wine-bugs＠winehq.org 20 Apr '20

20 Apr '20

http://bugs.winehq.org/show_bug.cgi?id=30506 Bug #: 30506 Summary: Text misrendered in Brain Workshop Product: Wine Version: 1.5.2 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified The free matching game Brain Workshop http://sourceforge.net/projects/brainworkshop/ downloadable from http://downloads.sourceforge.net/project/brainworkshop/brainworkshop/Brain%… renders all its "menu" text illegibly. 'winetricks corefonts' doesn't help. (Yes, there's a Linux version, but that doesn't work on my machine, so I thought I'd try the Windows version under Wine.) -- 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 17

[Bug 47833] New: FindFirstFileExW seems to be missing FILE_OPEN_FOR_BACKUP_INTENT flag to NtOpenFile
by WineHQ Bugzilla 20 Apr '20

20 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=47833 Bug ID: 47833 Summary: FindFirstFileExW seems to be missing FILE_OPEN_FOR_BACKUP_INTENT flag to NtOpenFile Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com Distribution: --- When running USVFS (through ModOrganizer 2), its hooked version of NtOpenFile checks for the FILE_OPEN_FOR_BACKUP_INTENT flag to see if the function calling it is FindFirstFileExW. Under Windows, this apparently works as expected, but wine doesn't pass the flag, causing USVFS to fail injecting directory listings. Adding the flag allows USVFS to work properly. I haven't tested this under windows, so I have no way to verify if the flag only gets set for some arguments sent to FindFirstFileExW and not others, but since USVFS has been known to work for many different programs, I would personally assume that the flag is always set. -- 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.

1 7

[Bug 41936] New: Regression in The Witcher 2: Assassins of Kings
by wine-bugs＠winehq.org 20 Apr '20

20 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=41936 Bug ID: 41936 Summary: Regression in The Witcher 2: Assassins of Kings Product: Wine Version: 1.9.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: jeff(a)macloue.com Distribution: --- Created attachment 56320 --> https://bugs.winehq.org/attachment.cgi?id=56320 Witcher2: Welcome screen - garbled text in menu Found a possible regression in The Witcher 2: Assassins of Kings game under Wine: the text is rendered incorrectly in the menus, subtitles, etc. A screenshot (1920x1080 downscaled 50%) is attached. Tracked the breakage between 1.9.13 and 1.9.14 (tested a few of 1.9.x series, the bug is reproduced up to version 1.9.23) and used git bisect to track the commit which introduced the regression: beccd5a2e53927137de031c1976e66d35b08afeb is the first bad commit commit beccd5a2e53927137de031c1976e66d35b08afeb Author: Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> Date: Wed Jun 22 06:00:55 2016 +0000 d3dx9_39: Share the source with d3dx9_36. Signed-off-by: Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 bfecf0f484447414e0b927c99d73c24cf4f695c9 4fbc2c7f69c3217284b8be7ebddad88ed1fdf094 M dlls :040000 040000 d2bc5924fd8102f1a1aff298f4426050db271fd5 60184108c62c5437f2724096b1cd43f14083eaba M tools No idea what the exact problem is, I see a batch of commits with the same description around this one. The system is Slackware64-14.2+multilib, hardware is Intel Core i7-6700/ASUS Q170M-C/NVIDIA GeForce GT 730 (with NVIDIA proprietary driver 370.23). -- 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 10

[Bug 25264] New: ExamXML crashes when opening an XML file
by wine-bugs＠winehq.org 20 Apr '20

20 Apr '20

http://bugs.winehq.org/show_bug.cgi?id=25264 Summary: ExamXML crashes when opening an XML file Product: Wine Version: 1.3.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: m.duelli(a)web.de There is a 30-day evaluation edition of ExamXML at http://www.a7soft.com/examxml.html While the installation and the program start-up went fine, the program immediately crashes after selecting an XML file for comparison. The output from the start-up to the crash is: err:rebar:REBAR_WindowProc unknown msg 2002 wp=00000000 lp=0033f9d8 err:rebar:REBAR_WindowProc unknown msg 2002 wp=00000000 lp=0033fd20 err:rebar:REBAR_MoveChildWindows EndDeferWindowPos returned NULL fixme:font:WineEngCreateFontInstance Untranslated charset 255 wine: Unhandled page fault on write access to 0x20202024 at address 0x7ef927d9 (thread 0009), starting debugger... err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7ef927d9 -- 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 48082] New: shell:PathResolveW needed by Visual C++ Express 2005
by WineHQ Bugzilla 20 Apr '20

20 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=48082 Bug ID: 48082 Summary: shell:PathResolveW needed by Visual C++ Express 2005 Product: Wine Version: 4.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: codespunk+bugzilla.winehq(a)gmail.com Distribution: --- Created attachment 65633 --> https://bugs.winehq.org/attachment.cgi?id=65633 Error window I can't dismiss this dialog because no matter what I enter, I always get this error telling me that the path is invalid. This is most likely due to the following stub as reported in the log: 0009:fixme:shell:PathResolveW (L"C:\\users\\mattd\\My Documents\\Visual Studio 2005\\Settings\\C++ Express\\CurrentSettings.vssettings",(nil),0x00000000),stub! -- 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.

1 8

[Bug 47615] New: _putws outputs NULs, other wchar.h functions don't
by wine-bugs＠winehq.org 20 Apr '20

20 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=47615 Bug ID: 47615 Summary: _putws outputs NULs, other wchar.h functions don't Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: dmo2118(a)gmail.com Distribution: --- Created attachment 65041 --> https://bugs.winehq.org/attachment.cgi?id=65041 Test program This seems inconsistent: $ i686-w64-mingw32-gcc -Wall -municode -mconsole putws-test.c $ wine a.exe | hexdump -C 00000000 70 00 75 00 74 00 77 00 73 00 0d 0a 00 66 70 75 |p.u.t.w.s....fpu| 00000010 74 77 73 0d 0a 77 70 72 69 6e 74 66 0d 0a 77 66 |tws..wprintf..wf| 00000020 70 72 69 6e 74 66 0d 0a 63 0d 0a |printf..c..| 0000002b Expected behavior: "putws" outputs as 70 75 74 77 73, without the 00s in between. I concede I am not running up-to-date development Wine. I'm having trouble installing it, and I don't know how long that would take to fix. Given the source code I've looked at, I have reason to believe that this still affects current Wine. $ wine --version wine-3.0 (Ubuntu 3.0-1ubuntu1) $ lsb_release -d Description: Ubuntu 18.04.3 LTS -- 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