February 2020 - Wine-Bugs - list.winehq.org

[Bug 46916] New: Can' t restore focus to certain minimized fullscreen applications
by wine-bugs＠winehq.org Feb. 25, 2020

Feb. 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=46916 Bug ID: 46916 Summary: Can't restore focus to certain minimized fullscreen applications Product: Wine Version: 4.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chrylis(a)gmail.com Distribution: --- Created attachment 64004 --> https://bugs.winehq.org/attachment.cgi?id=64004 stderr logs This is a counterpart to the many (mostly resolved?) bugs regarding switching *out* of fullscreen applications. On some applications, I can switch out of the window without any problem. If the application has changed the desktop resolution, it is restored to the previous setting (e.g., 1920x1080->3840x2160). However, I cannot restore focus to the application once it loses focus. The application will unminimize (from the taskbar or the window switcher), and the mouse cursor changes to the appropriate graphics, but the application seems never to be unblurred; it's not redrawn (I believe this is its own choice when it thinks it doesn't have focus), and the "bookmarked" resolution isn't applied. The application does not respond to input, and I have to kill Wine from the CLI. The applications I have available where I'm able to reproduce the behavior are based on the Civ4 engine (Civ4 itself, Railroads!). The behavior is identical regardless of whether the application changes the screen resolution (if it hasn't, then it'll switch back to full screen and show the last render but is still frozen). Fallout 2, with or without Restoration, does *not* reproduce the behavior. It may be linked to D3D. I'm running KWin 5.14.5 on Intel graphics. -- 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

[Bug 40187] New: Dream Acquarium can't run
by wine-bugs＠winehq.org Feb. 25, 2020

Feb. 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=40187 Bug ID: 40187 Summary: Dream Acquarium can't run Product: Wine Version: 1.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sdunnagan(a)yahoo.com Distribution: --- Something changed in the Dream Acquarium application, and now it doesn't run after it automatically installs updates. -- 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 45216] New: Alien: Isolation crashes on startup
by wine-bugs＠winehq.org Feb. 25, 2020

Feb. 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=45216 Bug ID: 45216 Summary: Alien: Isolation crashes on startup Product: Wine Version: 3.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: moihack.inside(a)gmail.com Distribution: ArchLinux Created attachment 61439 --> https://bugs.winehq.org/attachment.cgi?id=61439 Alien:Isolation terminal output Alien: Isolation (Steam version) crashes on startup. There is an attempt for the game to load as a process named AI.exe is created and a window pops up on a black screen but with the mouse cursor changing to the in-game one. So the game at least attempts to boot up. Specifically for Arch Linux which I use, there is a "trick" to get this game running. If you install the package "wine-staging-nine" from the official repositories here : https://www.archlinux.org/packages/multilib/x86_64/wine-staging-nine/ the game boots correctly. It does not boot up with plain wine-staging or vanilla wine + gallium nine patches. So it probably needs a mix of patches from both projects. I'm attaching a terminal output below. GPU used: Radeon HD 6870 -- 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 48629] New: valgrind shows dependency on uninitialized memory in gdi32/dib.c
by WineHQ Bugzilla Feb. 25, 2020

Feb. 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48629 Bug ID: 48629 Summary: valgrind shows dependency on uninitialized memory in gdi32/dib.c Product: Wine Version: 5.0-rc6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 66480 --> https://bugs.winehq.org/attachment.cgi?id=66480 valgrind log See attachment. -- 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 3

[Bug 48241] New: PACE license manager installer dies with Error: -1627 Function failed
by WineHQ Bugzilla Feb. 25, 2020

Feb. 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48241 Bug ID: 48241 Summary: PACE license manager installer dies with Error: -1627 Function failed Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: emiel(a)kollof.nl Distribution: --- Installation seems to die here: 01de:err:msi:ITERATE_StartService Failed to start service L"PaceLicenseDServices" (6) 01de:err:msi:execute_script Execution of script 0 halted; action L"StartServices" returned 1627 01de:err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned 1627 00c9:err:ole:ClientRpcChannelBuffer_SendReceive called from wrong apartment, should have been 0xca000001de -- 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 48659] New: Job details page: Add links to the first error in a report
by WineHQ Bugzilla Feb. 24, 2020

Feb. 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=48659 Bug ID: 48659 Summary: Job details page: Add links to the first error in a report 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: --- When looking at a full WineTest report on the TestBot website finding the errors can require a lot of scrolling and there is a risk of skipping over them. The cache .errors files contain the line of each error and error group. This makes it possible to add links to the errors: * The first report line would contain a link pointing to the first report error (for instance in the form of a down arrow at the start of the line). * Errors would contain links to the previous/next errors, or to the first/last report line. * The last report line would link to the last report error. Once the first draft is ready the link chain may be tweaked: * The first line of test units containing errors, could be added to it. * A second chain link to be set up with only the new failures. -- 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 48658] New: Fix error handling in the WineRun* scripts
by WineHQ Bugzilla Feb. 23, 2020

Feb. 23, 2020

https://bugs.winehq.org/show_bug.cgi?id=48658 Bug ID: 48658 Summary: Fix error handling in the WineRun* scripts 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: --- Over time error handling in the WineRun* scripts has become complex and inconsistent. It's in need of a serious cleanup, particular so that errors can be reliably identified in the testbot.log file and shown on the JobDetails page. There are three places where the WineRun* scripts can send errors: * To the global 'var/log' log file. Sending errors to the global file makes sense for errors which could be relevant to other operations on that VM such as the preceding or following revert. * To the per-task 'testbot.log' file. This is where most errors should go for long term storage. * To stderr which is redirected to 'testbot.log' nowadays. Then there are a number of functions that report errors: * LogMsg() This adds a message to the global log (errors and others alike). It is used to log the startup and exit of the WineRun* scripts in the global log, but also to save some errors there. * Error() Prints the error on stderr if --log-only is not specified, and sends them to the global log (via LogMsg()). In particular things like usage errors thus end up in the global log which probably does not make sense. * LogTaskError() Explicitly opens testbot.log and appends to it. It should really print to stderr instead. But some calls to LogTaskErrors * FatalError() The main point of FatalError() is that it invokes WrapUpAndExit() with appropriate parameters. But it also sends the error message to both the global log and testbot.log (via LogTaskError()). That's probably not appropriate. * FatalTAError() This is a specialized form of FatalError() which also notifies the administrator of network issues. That's ok except that depending on the codepath it may end up calling any of Error(), LogMsg(), LogTaskError() or FatalError(). -- 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 0

[Bug 8439] Multiple Microsoft product installers fail due missing shell app path expansion (Visual Studio .NET 2002, 2003, Visual Foxpro 9.0)
by WineHQ Bugzilla Feb. 23, 2020

Feb. 23, 2020

https://bugs.winehq.org/show_bug.cgi?id=8439 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fgouget(a)codeweavers.com |wine-bugs(a)winehq.org -- 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 0

[Bug 47042] New: Ignore replies to patchset parts
by wine-bugs＠winehq.org Feb. 23, 2020

Feb. 23, 2020

https://bugs.winehq.org/show_bug.cgi?id=47042 Bug ID: 47042 Summary: Ignore replies to patchset parts 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 TestBot treats every email as a potential patch. This makes sense as replies to a patch could be a new version for that patch which means it should be tested. But replies to parts of patches are different. Here is what happened due to the failure to recognize this. I'm not sure why but the TestBot must have received the following emails in this order (this is not the order of the send times but it matches the order in which I received the emails in my inbox): * [PATCH 1/5] ntoskrnl.exe: Implement PsLookupThreadByThreadId. https://www.winehq.org/pipermail/wine-devel/2019-April/144085.html Part 1/5 in a patch series. The TestBot created a PendingPatchSet object to track the different parts. * Re: [PATCH 1/5] ntoskrnl.exe: Implement PsLookupThreadByThreadId. https://www.winehq.org/pipermail/wine-devel/2019-April/144088.html The TestBot decided this looked like a patch because the HTML version contains lines that start with "+++ ". Thus it treated this email as a new version of the previous patch, like it usually does, and replaced patch 1 in the PendingPatchSet. * Re: [PATCH 2/5] ntoskrnl.exe: Implement KeAreApcsDisabled using critical region functions. https://www.winehq.org/pipermail/wine-devel/2019-April/144086.html The TestBot created a job to test this patch but used the updated part 1 of the patch set which in fact was an HTML email. This resulted in an invalid patch and thus a failure to apply. The TestBot probably did two things wrong: 1. It took a patch from an HTML attachment. The TestBot already rejects those but somehow the $Part->effective_type ne "text/html" test in Patch::NewPatch() did not work. 2. It replaced part 1 of a patchset with a new version. One cannot send a new version of a part in a patchset: the whole patchset must be resubmitted (*). So the TestBot should never replace a part in a patchset. It looks like this check should be done in PendingPatchSets::NewSubmission() near the $Set->Parts->GetItem($PartNo) call. The issue here is that we may receive emails out of order. So we could receive a reply to part 1, and thus add it as part 1, before we receive the actual email for part 1. (*) Otherwise we'd have to keep the patchsets around and create new jobs for all parts that follow the replaced part. And if multiple parts are replaced... madness! -- 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 48031] New: Limit the size of the task logs
by WineHQ Bugzilla Feb. 23, 2020

Feb. 23, 2020

https://bugs.winehq.org/show_bug.cgi?id=48031 Bug ID: 48031 Summary: Limit the size of the task logs 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 TestBot does not check the size of the reports and logs it downloads from the VMs. These could be quite big and are even more likely to get big if setting WINEDEBUG is allowed. So there should be a limit. The TestAgent GetFile() API has no provision for putting a limit on the size of the file being retrieved. But checking the size against a limit would come quite naturally if the files are retrieved one chunk at a time (see bug 48030). Note that the Wine rebuild logs are quite big (11MB). -- 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 2