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

[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

[Bug 47899] New: Review the VM name validation
by WineHQ Bugzilla Feb. 22, 2020

Feb. 22, 2020

https://bugs.winehq.org/show_bug.cgi?id=47899 Bug ID: 47899 Summary: Review the VM name validation 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 web interface allows the creation of VMs that have dashes in their name. But when untainting its parameters LibvirtTool considers such names to be invalid, so that trying to revert these VMm fails. There is a VM::Validate() method that should validate the VM name among others, but obviously it cannot be used to check and untaint script parameters. So the VM name validation criterions need to be checked and a standard function provided. -- 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 47492] New: Typo in function name (__wine_spec_fini)
by wine-bugs＠winehq.org Feb. 22, 2020

Feb. 22, 2020

https://bugs.winehq.org/show_bug.cgi?id=47492 Bug ID: 47492 Summary: Typo in function name (__wine_spec_fini) Product: Wine Version: 4.12.1 Hardware: x86 OS: Solaris Status: UNCONFIRMED Severity: trivial Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: evgeny.v.litvinenko(a)gmail.com Created attachment 64875 --> https://bugs.winehq.org/attachment.cgi?id=64875 A patch example. Hi all. It looks like there is a typo in the file tools/winegcc/winegcc.c The command ggrep "[^_]_wine_spec_fini" -r * in the source tree finds two places where __wine_spec_fini is with one underscore in the begining. I've attached a patch just to show the places with typo (I think it's a typo), feel free to use it as you want. Regards evgeny. -- 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 48625] New: Game DayZ Dedicated Server 1.07.152951 - Can not connect
by WineHQ Bugzilla Feb. 22, 2020

Feb. 22, 2020

https://bugs.winehq.org/show_bug.cgi?id=48625 Bug ID: 48625 Summary: Game DayZ Dedicated Server 1.07.152951 - Can not connect Product: Wine-staging Version: 5.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chris.76(a)hotmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 66475 --> https://bugs.winehq.org/attachment.cgi?id=66475 wine 5.2 logs Hello Support, I'm an advanced user on linux and I'm trying to set up a dedicated server for my game DayZ. My game is available only on Steam, windows version and in 64-bit. I used steamcmd for linux version to download the dedicated server windows version. Details about depots of this game : https://steamdb.info/app/223350/depots/ You can see 2 libraries are needed : - VC 2013 Redist - VC 2015 Redist So I installed wine, setted up in windows 10 (and used WINEARACH, WINEPREFIX) and installed VC 2013 & 2015 in 64-bit edition. My server is using a vanilla config, it means untouched. My server comes online but when i try to connect, my client fails. When I look logs from game server, I can't see any traces when I tried to connect. (it's not normal, it's should) I attached logs. Thanks in advance for helping me. Have a nice day. -- 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

[Bug 4418] black screen when starting Warlords Battlecry
by WineHQ Bugzilla Feb. 22, 2020

Feb. 22, 2020

https://bugs.winehq.org/show_bug.cgi?id=4418 --- Comment #24 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still occurs with wine-5.2 -- 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 48638] New: Clrmamepro 4036a_64_20200220: crashes when quit
by WineHQ Bugzilla Feb. 21, 2020

Feb. 21, 2020

https://bugs.winehq.org/show_bug.cgi?id=48638 Bug ID: 48638 Summary: Clrmamepro 4036a_64_20200220: crashes when quit Product: Wine Version: 5.2 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vicmarto(a)me.com Created attachment 66494 --> https://bugs.winehq.org/attachment.cgi?id=66494 log + backtrace Clrmamepro crashes when quit. Just open the program, and then trying to quit is enough to trigger the crash. Download link: https://mega.nz/#!ydpxCCyB!IEznOWu5b8hJN51YwYXXCwEKrGt7677kJsVMS2x1ATw cdf93153a324c1402a26ce84f25058ee39df3e95 cmp4036a_64_20200220.zip -- 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