wine-bugs February 2021

wine-bugs@winehq.org

1 participants
6834 discussions

[Bug 26189] New: Wine32bi (kernel32)t: Crysis Wars Dedicated Server no longer shows console on start under X
by wine-bugs＠winehq.org 07 May '21

07 May '21

http://bugs.winehq.org/show_bug.cgi?id=26189 Summary: Wine32bi (kernel32)t: Crysis Wars Dedicated Server no longer shows console on start under X Product: Wine Version: 1.3.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: armin.kazmi(a)tu-dortmund.de If you want to launch a crysis wars dedicated server, e.g. via wine CrysisWars/Bin32/CrysisWarsDedicatedServer.exe -mod MWLL -root C:/Program Files/CrysisWars/server +exec server.cfg you expect it to spawn a console window (using windows console host it seems) to show further output and provide a control interface. Via git bisect I tracked down the offending patch, which was added quite a long time ago. e4d090277b3f4f76b39e55480e5d1387798dbabe is the first bad commit commit e4d090277b3f4f76b39e55480e5d1387798dbabe Author: Eric Pouech <eric.pouech(a)orange.fr> Date: Mon Aug 30 22:19:24 2010 +0200 kernel32: Properly handle bare console on input. :040000 040000 79337f5cf3c9c78a557b10f8b1147476815470ac 860f197e56f714bea54dacbafe881c0ede7b19e9 M dlls Automatic revert of the patch from HEAD fails. -- 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 49763] New: ALOTInstaller crashes
by WineHQ Bugzilla 07 May '21

07 May '21

https://bugs.winehq.org/show_bug.cgi?id=49763 Bug ID: 49763 Summary: ALOTInstaller crashes Product: Wine Version: 5.16 Hardware: x86 OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Created attachment 68064 --> https://bugs.winehq.org/attachment.cgi?id=68064 crash log A user reported this as rated "garbage" in appdb, so i gave it a try The crash log shows a call to RtlConvertToAutoInheritSecurityObject, which is strange as the FIXME from that stub is not printed in console; is that normal? One issue is at least that RtlConvertToAutoInheritSecurityObject is wrong declared, see https://bugs.winehq.org/show_bug.cgi?id=33279#c1 but then committed patch declares it as BOOL: https://bugs.winehq.org/show_bug.cgi?id=33279#c3 I`ll send a patch for that one. But that is not the cause of the crash, even if i remove RtlConvertToAutoInheritSecurityObject from ntdll.spec it shows up in the crash log (???) So anyone knows what`going on? Note: I don`t know exactly what .net it needs, I tried dotnet40 and dotnet48, same crash happens Unhandled exception: 0xe0434352 in 64-bit code (0x000000007b01129e). . . Backtrace: =>0 0x000000007b01129e format_exception_msg+0x32e(ptr=<is not available>, buffer=<is not available>, size=<is not available>) [Z:\home\louis\sda2\wine64-build\dlls\kernelbase\..\..\..\wine\dlls\kernelbase\debug.c:315] in kernelbase (0x0000000000512d60) 1 0x000006447fd60412 EntryPoint+0x6440003ef15() in msvcr100_clr0400 (0x0000000000512d60) 2 0x000000007bc521e1 RtlConvertToAutoInheritSecurityObject+0x200(pdesc=<is not available>, cdesc=<is not available>, ndesc=<is not available>, objtype=<is not available>) [Z:\home\louis\sda2\wine64-build\dlls\ntdll\..\..\..\wine\dlls\ntdll\sec.c:1721] in ntdll (0x0000000000512d60) 3 0x000006447fd5f5a7 EntryPoint+0x6440003e0aa() in msvcr100_clr0400 (0x0000000000516319) -- 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 4

[Bug 22327] New: download
by wine-bugs＠winehq.org 07 May '21

07 May '21

http://bugs.winehq.org/show_bug.cgi?id=22327 Summary: download Product: Wine Version: 1.1.42 Platform: x86 URL: http://sourceforge.net/projects/phpgedview/files/1%20P hpGedView/PhpGedView%20v4.2.3/PGV-Demo-4.2.3.zip/downl oad OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: leighmanthegreat(a)hotmail.com Cannot install PGV demo for Windows using a clean wineprefix. After installing dotnet20sp2 Mono2.4 with winetricks I get the following output: err:module:import_dll Library php5ts.dll (which is needed by L"Z:\\home\\jack\\PGV test\\democd\\httpd\\php\\php5apache2_2.dll") not found (OS 10048)Address already in use: make_sock: could not bind to address 127.0.0.1:6880 no listening sockets available, shutting down Unable to open logs System.OverflowException: Number overflow. at System.Drawing.SizeF.ToSize () [0x00000] at System.Windows.Forms.MessageBox+MessageBoxForm.InitFormsSize () [0x00000] at System.Windows.Forms.MessageBox+MessageBoxForm.RunDialog () [0x00000] at (wrapper remoting-invoke-with-check) System.Windows.Forms.MessageBox/MessageBoxForm:RunDialog () at System.Windows.Forms.MessageBox.Show (System.String text) [0x00000] at PGVDemo.Form1.button1_Click (System.Object sender, System.EventArgs e) [0x00000] at System.Windows.Forms.Control.OnClick (System.EventArgs e) [0x00000] at System.Windows.Forms.Button.OnClick (System.EventArgs e) [0x00000] at System.Windows.Forms.ButtonBase.OnMouseUp (System.Windows.Forms.MouseEventArgs mevent) [0x00000] at System.Windows.Forms.Button.OnMouseUp (System.Windows.Forms.MouseEventArgs mevent) [0x00000] at System.Windows.Forms.Control.WmLButtonUp (System.Windows.Forms.Message& m) [0x00000] at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x00000] at System.Windows.Forms.ButtonBase.WndProc (System.Windows.Forms.Message& m) [0x00000] at System.Windows.Forms.Button.WndProc (System.Windows.Forms.Message& m) [0x00000] at System.Windows.Forms.Control+ControlWindowTarget.OnMessage (System.Windows.Forms.Message& m) [0x00000] at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x00000] at System.Windows.Forms.NativeWindow.WndProc (IntPtr hWnd, Msg msg, IntPtr wParam, IntPtr lParam) [0x00000] -- 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 35545] New: Proteus 8 demo installer needs IWshShell3::RegWrite method implementation
by wine-bugs＠winehq.org 06 May '21

06 May '21

https://bugs.winehq.org/show_bug.cgi?id=35545 Bug ID: 35545 Summary: Proteus 8 demo installer needs IWshShell3::RegWrite method implementation Product: Wine Version: 1.7.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Classification: Unclassified Hello folks, as the summary says ... found during investigation of bug 35539 (and blocked by). Probably also needed by Proteus 8 Professional installer. To work around bug 35539 pass 'KEY_SERVER' property via command line: --- snip --- $ wine msiexec -i setup_demo8.1.17358.0.msi KEY_SERVER=test ... $ fixme:wshom:WshShell3_RegWrite (L"HKLM\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment\\LXKSERVER" {VT_BSTR: L"test"} {vt 10}): stub ... --- snip --- Source: http://source.winehq.org/git/wine.git/blob/2b1f2001b153190bbd3bb138684149f6… --- snip --- 811 static HRESULT WINAPI WshShell3_RegWrite(IWshShell3 *iface, BSTR Name, VARIANT *Value, VARIANT *Type) 812 { 813 FIXME("(%s %s %s): stub\n", debugstr_w(Name), debugstr_variant(Value), debugstr_variant(Type)); 814 return E_NOTIMPL; 815 } --- snip --- 'winetricks -q wsh57' obviously works around. $ sha1sum prodemo.exe e3409adbc80bd73a36f82890da2b7d16be2fbf51 prodemo.exe $ du -sh prodemo.exe 166M prodemo.exe $ wine --version wine-1.7.12 Regards -- 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 50093] New: Lara Croft and the guardian of light have very low performance without neckloop even at lowest resolution
by WineHQ Bugzilla 06 May '21

06 May '21

https://bugs.winehq.org/show_bug.cgi?id=50093 Bug ID: 50093 Summary: Lara Croft and the guardian of light have very low performance without neckloop even at lowest resolution Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andy86(a)fastwebnet.it Distribution: --- Created attachment 68566 --> https://bugs.winehq.org/attachment.cgi?id=68566 plain wine console output at 640x480 with lowest settings and +fps,+tid,+timestamp Lara Croft and the guardian of light runs well at 60 fps (and at 100 and more fps if vsync is disabled) on the menu, but during the game it has a performance drop of about 14 fps even at the lowest resolution and with the settings as low as possible. CPU usage is around 20-35% for the game for a maximium total of approx 60% consider steam and wineserver, and 5-10% max GPU load measured at 640x480 resolution and lowest possible graphics settings and approx 300mb of RAM so it's do not appear as an hardware bottleneck. I tried some old versions (about 3.x) of wine to exclude other regressions (like bug 46942) and the performance on all tested versions are identical. I also tried wine-staging with pba patches and all mentioned wine version with unsupported dxvk and dgvoodo2 and performance are identical also on it. So it seems that the problem is not in d3d* and something others goes wrong in Wine, but I am not able to define exactly what. -- 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 22

[Bug 43343] New: Palette corruption or wrong/corrupted colours
by wine-bugs＠winehq.org 05 May '21

05 May '21

https://bugs.winehq.org/show_bug.cgi?id=43343 Bug ID: 43343 Summary: Palette corruption or wrong/corrupted colours Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: alehiphopdj2(a)hotmail.com Distribution: --- Created attachment 58684 --> https://bugs.winehq.org/attachment.cgi?id=58684 ZIP file with 3 screenshots of Frank Herbert's Dune showing colours wrong Playing Frank Herbert's Dune (2001) on Wine 2.12 on Linux (Ubuntu) from a fresh and successful installation, colours are corrupted on: - cutscenes (realtime rendering, not videos) - gameplay - title screen I attach a zip file with these 3 screenshots. These are the errors i get on the console: fixme:win:EnumDisplayDevicesW ((null),0,0x33f0d4,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33ea04,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f404,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f3b4,0x00000000), stub! fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:wined3d_colour_from_ddraw_colour Unhandled pixel format. fixme:ddraw:ddraw_surface7_Flip Ignoring flags 0x1. err:d3d:wined3d_format_get_float_color_key Unhandled color key to float conversion for format WINED3DFMT_R8G8_SNORM_L8X8_UNORM. err:d3d:wined3d_format_get_float_color_key Unhandled color key to float conversion for format WINED3DFMT_R8G8_SNORM_L8X8_UNORM. err:d3d:wined3d_format_get_float_color_key Unhandled color key to float conversion for format WINED3DFMT_R8G8_SNORM_L8X8_UNORM. err:d3d:wined3d_format_get_float_color_key Unhandled color key to float conversion for format WINED3DFMT_R8G8_SNORM_L8X8_UNORM. ... (this last error repeating all time until the end) Looks like colours are corrupted because this error... -- 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 41316] New: aplikasi ada masalah saat dibuka
by wine-bugs＠winehq.org 05 May '21

05 May '21

https://bugs.winehq.org/show_bug.cgi?id=41316 Bug ID: 41316 Summary: aplikasi ada masalah saat dibuka Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: santosoa141(a)yahoo.com Distribution: Ubuntu aplikasi kolotibablo ada masalah saat di buka -- 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 4

[Bug 32725] New: VC runtime functions crash when called from reloaded library in a thread
by wine-bugs＠winehq.org 05 May '21

05 May '21

http://bugs.winehq.org/show_bug.cgi?id=32725 Bug #: 32725 Summary: VC runtime functions crash when called from reloaded library in a thread Product: Wine Version: 1.3.24 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt AssignedTo: wine-bugs(a)winehq.org ReportedBy: most(a)museresearch.com Classification: Unclassified Created attachment 43181 --> http://bugs.winehq.org/attachment.cgi?id=43181 msvcrt-dll-problem.zip Assume WHAT.DLL is a windows DLL with static MSVCRT linkage. If WHAT.DLL is unloaded and reloaded, it's C runtime functions like std::cout can crash when called from a thread. According to Piotr Caban (piotr dot caban at gmail dot com) "The crash is caused by incomplete FlsFree implementation. There's a comment in it's code that says what needs to be added: /* FIXME: add equivalent of ThreadZeroTlsCell here */" The crash is repeatable with the attached example winelib program (captain.exe) and windows DLL (what.dll). Code for the compiled what.dll is included. An included README file describes the contents. 'make test' demonstrates the 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 8

[Bug 50439] New: Wine can no longer be installed
by WineHQ Bugzilla 05 May '21

05 May '21

https://bugs.winehq.org/show_bug.cgi?id=50439 Bug ID: 50439 Summary: Wine can no longer be installed Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maklip007(a)gmail.com When trying to install Wine for Mac, an error message saying: “winehq-stable-5.0.pkg” can’t be opened because Apple cannot check it for malicious software." shows up. -- 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 50293] New: native dxdiag complains about missing dxapi.sys (et al)
by WineHQ Bugzilla 04 May '21

04 May '21

https://bugs.winehq.org/show_bug.cgi?id=50293 Bug ID: 50293 Summary: native dxdiag complains about missing dxapi.sys (et al) Product: Wine Version: 6.0-rc1 Hardware: x86-64 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- To reproduce: winetricks -q dxdiag wine dxdiag Click no to driver check Choose 'DirectX Files' tab (2nd) The notes field complains: Several files (dxapi.sys, d3dpmesh.dll, dpmodemx.dll, etc.) are missing! You'll see several missing files: dxapi.sys d3dpmesh.dll dpmodemx.dll dpvvox.dll dpvacm.dll dpnhupnp.dll dimap.dll diactfrm.dll gcdef.dll dsound3d.dll dsdmoprp.dll dx7vb.dll encapi.dll qdv.dll qedwipes.dll I have stubs for these, after which dxdiag reports success (for that test, there are still other failures..). The last round of sent patches, for reference: https://source.winehq.org/patches/data/196982 However I suspect they should probably wait until after code freeze. In any event, the bug needed to be reported. -- 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 10

[Bug 33660] New: CS:GO - Call votes respond
by wine-bugs＠winehq.org 04 May '21

04 May '21

http://bugs.winehq.org/show_bug.cgi?id=33660 Bug #: 33660 Summary: CS:GO - Call votes respond Product: Wine Version: 1.5.30 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pepe(a)bloodkings.eu Classification: Unclassified Once a player can call vote, and only works the first choice (F1, 1). -- 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 19

[Bug 31787] New: Run the tests in Wine
by wine-bugs＠winehq.org 03 May '21

03 May '21

http://bugs.winehq.org/show_bug.cgi?id=31787 Bug #: 31787 Summary: Run the tests in Wine Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified The Wine TestBot runs the conformance tests on Windows VMs before they are committed to Wine. This greatly helped improve the quality of our conformance tests. The next step is making sure that the conformance tests work reliably in Wine too, and that Wine patches don't break them. The hope is that this will help us improve the state of the WineTest results: http://test.winehq.org/data/ Doing so will be much more processor intensive than the current process: * Currently only the conformance test patches are tested whereas we would need to test almost every single patch (we could ignore some documentation patches for instance). * Currently we only have to generate a binary for the one conformance test that's impacted. That's quick. Testing all Wine patches will require recompiling Wine every time which takes more time, even with ccache. * A Wine patch can have wide-ranging effects. For instance a patch to ntdll could impact pretty much any conformance test. That means rerunning all of them for every patch... unless we find reliable ways of pruning them (patches to conformance tests would be an obvious optimization). * Like for Windows we will need to test various configurations: different locales; 32, 64 and 32+64 bit Wine builds; different sound backends; possibly different Linux distributions; if possible FreeBSD and Solaris too (I'm leaving Mac OS X for another bug). In some cases the same binaries can be used for multiple tests (e.g. if only the locale changes) but in other cases not. * Also for the current Wine TestBot an unreliable test only impacts people modifying that test. But the above point means an unreliable test would impact most Wine patches, leading to lots of patches being rejected. So this means unreliable tests become a big issue and need to be handled in some way: fixed or blacklisted or still run but not considered cause for rejection (so one can notice when they get fixed). Then there is the question of whether this should be done by modifying the Wine TestBot or by using the BuildBot framework: http://trac.buildbot.net/wiki/AboutBuildbot Dan Kegel produced a proof of concept system based on BuildBot: http://wiki.winehq.org/BuildBot An issue is that without significant integration work, having both a WineTestBot and BuildBot system would be annoying: * The Wine TestBot currently has its own user database and BuildBot would add another one. So it would be one more login to manage for developers unless we manage to integrate either with another user database (e.g. through LDAP). * Developers would have to submit patches to both sites and check the results on both. * Integration with the Wine Patches site (http://source.winehq.org/patches/) would need to work with both systems. -- 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 33234] New: Improve user management
by wine-bugs＠winehq.org 03 May '21

03 May '21

http://bugs.winehq.org/show_bug.cgi?id=33234 Bug #: 33234 Summary: Improve user management Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified When an account request is sent to a WineTestBot administrator the URL he gfets sent to is the UserDetails.pl one but it only has an 'Approve' button, not a 'Reject' one. This makes it unclear how to reject spam requests for instance (bug 31798), but this has now been documented. Still, rejecting an application actually requires going to another page and deleting the provisional account. This should be simpler: there should be a 'Reject' button right on the UserDetails page that does that. Furthermore, the status of the account, 'Pending approval' and 'Pending activation', should be clearly indicated both on the UserDetails page and on the UsersList page. -- 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 5

[Bug 48093] New: On cw-rx460 the WoW WinePrefixes are (likely) broken
by WineHQ Bugzilla 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=48093 Bug ID: 48093 Summary: On cw-rx460 the WoW WinePrefixes are (likely) broken 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: --- On cw-rx460 the wineprefixes created for the wow32 and wow64 test runs are flawed: * It looks like they do not define the %windir% and %SystemRoot% environment variables: https://www.winehq.org/pipermail/wine-devel/2019-October/152271.html * They may be responsible for a failure in crypt32:sip https://www.winehq.org/pipermail/wine-devel/2019-November/154240.html What's puzzling is that cw-rx460 runs the same wt-daily script (*) as cw-gtx560 and other machines which don't have the same set of failures (see also bug 48092). cw-rx460 is not a TestBot VM so this does not impact the TestBot results. But if the wineprefixes are indeed causing extra test failures this could lead developers on a wild goose chase. So to avoid confusion I disabled the wow32 and wow64 WineTest runs on that machine until I have had time to investigate. (*) https://github.com/fgouget/wt-daily -- 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 4

[Bug 39442] New: Using Spice required to avoid failure in mmdevapi:capture
by wine-bugs＠winehq.org 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=39442 Bug ID: 39442 Summary: Using Spice required to avoid failure in mmdevapi:capture 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 Windows 7+ VMs all use an ich6 virtual soundcard (they don't support any of ac97, es1370 or sb16 ones). But they have failures in mmdevapi:capture such as: capture.c:586: Returned latency: 5.8050 ms capture.c:178: Test failed: Position 375 expected 0 capture.c:186: Wait'ed position 375 pad 0 flags 1, amount of frames locked: 448 capture.c:228: Test failed: Position 1719 expected 823 [...] It turns out that the way the VM is configured for remote access impacts the result of the tests: * If configured for VNC then the tests fail as described, even if no client is connected. * If configured for Spice access then the tests succeed, even if no client is connected. And if a client is connected the sound is carried over with pretty good reliability. So the way one accesses the VM changes the behavior in the guest. That seems wrong and I reported it to QEmu: https://bugs.launchpad.net/qemu/+bug/1499908 I have updated the w7pro64 configuration on 2015/09/25 and it now only has one intermittent Master volume failure left in mmdevapi:capture. The change does not seem to have negatively impacted the other tests. So it seems the change can safely be propagated to the other Windows 7+ VMs. There may be one issue though, which is that combining QXL with Spice causes the Windows 10 VM to freeze very quickly. Hopefully that's specific to Windows 10. -- 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 39419] New: Fix the 'Failure running script in VM' errors
by wine-bugs＠winehq.org 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=39419 Bug ID: 39419 Summary: Fix the 'Failure running script in VM' errors 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: --- There are two very common 'boterror' types: Failure running script in VM: the "nc -q0 '10.42.42.133' '4242'" command returned 1 and Failure running script in VM: network read timed out (Connect:AgentVersion.h:0/9) Both seem to correspond to a network issue and both seem to almost exclusively and systematically happen with the w864 and w1064 VMs when running either a 32 or 64 bit WineTest job (i.e. running the full suite). -- 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 2

[Bug 47852] New: Let developers pick any of the Wine VM's missions for their job
by WineHQ Bugzilla 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=47852 Bug ID: 47852 Summary: Let developers pick any of the Wine VM's missions for their job 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: --- Wine VMs can typically perform multiple missions. For instance the Debian 10 VM missions are: win32,test=module:win32,lang=fr_FR:win32,lang=ja_JP:win32,test=module,lang=zh_CN|wow32,test=module:wow64,test=module This means it can run the tests against the win32, wow32 and wow64 Wine builds, in English, French, Japanese and Chinese locales. But when submitting a job though the website the tests are only run against the win32 Wine build in the English locale and the developer cannot pick any other test configuration. This means debugging failures that only happen on the wow64 build of the TestBot require sending the patch to wine-devel which pollutes the mailing list, triggers many other tests, and is cumbersome for the developer. So the 'Submit job' page should analyze a Wine VM's missions and provide a way to pick any combination of build and language (since they are independent). -- 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 40239] New: Submitting more than one job for a given file fails
by wine-bugs＠winehq.org 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=40239 Bug ID: 40239 Summary: Submitting more than one job for a given file fails 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: --- Steps to reproduce: * Open the 'Submit job' page in two windows. * In both select the same file, for instance a patch.diff file or mytest.exe one. * Fill the Remarks field and click on the next button in both windows. * Continue the submission process on both sides. * At the end one job will work and the other will have 'unknown' written in the 'File name' column and fail with a TestBot error. During the submission process the server faces the following conditions: * The server needs the uploaded file early in the submission process so it can analyze it and adjust the questions it asks later (e.g. prefill the command line for patches, only present 64 bit VMs for 64 bit executables, etc.). * There is no job yet to store the user-provided file. So it is stored in a temporary 'staging' area and then moved into place when the job is created. * The user can abandon the submission process at any time which causes the temporary files he uploaded to be orphaned. To deal with this issue the server has a garbage collecting mechanism. * To avoid interference between users if they upload files that have the same name the temporary filename is prefixed with a per-user string. * However nothing prevents a collision in the staging area starts two job submissions at the same time for the same file. This is what happens in the steps above. That last point is somewhat intentional as it limits the accumulation of orphaned files if a user abandons a submission only to pick it up a bit later. But getting a broken job is wrong in any case. -- 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 2

[Bug 39417] New: Display duration instead of 'Ended' time
by wine-bugs＠winehq.org 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=39417 Bug ID: 39417 Summary: Display duration instead of 'Ended' time 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: --- For Jobs and Tasks the website shows the 'Ended' time but this is not very practical. Developers would likely be much more interested in the time it took to run the job/task. So all this does is force them to do that calculation themselves. The (slight) difficulty is mostly that the relevant pages use a base class that builds the HTML from all the selected fields. So the framework would need to be modified to let subclasses either provide their own 'virtual columns' with the corresponding header and content. Alternatively, in this case we could make do with letting them replace the column's header and content. -- 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 2

[Bug 47844] New: Add a dual-screen Wine VM
by WineHQ Bugzilla 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=47844 Bug ID: 47844 Summary: Add a dual-screen Wine VM 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: --- Wine has tests that deal with multi-head displays. These would need some matching multi-head test Wine VMs. -- 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 5

[Bug 47869] New: dwrite:font fails on cw-rx460-1809
by WineHQ Bugzilla 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=47869 Bug ID: 47869 Summary: dwrite:font fails on cw-rx460-1809 Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dwrite:font started failing when the AMD HD6800 graphics card was replaced with the ADM RX 460 one. The failures are always the same: font.c:1731: Test failed: got 0x8007007a font.c:1744: Test failed: got 54 font.c:1749: Test failed: got 54 The exact tag is cw-rx460-1809, which is the Windows 10 1809 disk image. This means either the new graphics driver changed something (maybe it installed a new strange font?), or a Windows 10 update slipped in while the new graphics driver was being updated (which is quite likely). -- 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 5

[Bug 48191] New: Add a captcha to the feedback page
by WineHQ Bugzilla 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=48191 Bug ID: 48191 Summary: Add a captcha to the feedback page 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: --- We are now regularly getting spam on the captcha page. Spammers really have time to waste! So we should add a captcha. Despite its simplicity the one on the registration page still seems to work so it should be a simple matter of porting it over. -- 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 48035] New: Speed up the new failures detection
by WineHQ Bugzilla 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=48035 Bug ID: 48035 Summary: Speed up the new failures detection 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 a task completes the TestBot distinguishes new failures from preexisting ones by comparing the task's report to the latest WineTest report. Any failure present in the task's report which is not present in the WineTest report is new. This means parsing both reports to extract the errors and diffing them. This needs to be done whenever we need the list of new failures which is: * When sending a notification to the developer when a wine-patches job completes. * On the JobDetails page. But the WineTest reports are pretty big (~600KB on Windows, ~1.5MB on Wine) which translates into non negligible processing time. For instance on my development environment loading the JobDetails page for a job with 1 Windows report and 8 Wine reports takes about 0.2 s without the reference WineTest reports, but close to 2 s when they are present. So it would help to only store the WineTest failures instead of the full report (optimisation a in bug 47998). This would cut down not only on the amount of data to read, but also on the required parsing. Testing this in the same development environment indicates this could bring the JobDetails processing time down to about 0.3 s. -- 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 4

[Bug 47998] New: Better deal with random test failures
by WineHQ Bugzilla 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=47998 Bug ID: 47998 Summary: Better deal with random test failures 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: --- Some tests fail randomly. They should be fixed of course but the in the meantime the TestBot should try not to report them as new failures when they happen. To detect new errors the TestBot compares a task's test result with that of the latest WineTest run. So if a failure did not happen during the last WineTest run and then happens when testing a patch it will be reported as a new failure. To avoid that the TestBot should take into account not just the latest WineTest report, but all the available test reports. This way, if the random failure happened in any of those runs it will be reported as pre-existing as expected. How much of a history to take into account can then be adjusted by changing $JobPurgeDays, or adding a specific setting. Note that this means if a failure is fixed and is reintroduced soon after it will not be reported as a new failure. This scenario should be rare enough to not be an issue in practice. To implement this: 1. Store the WineTest reports in the var/latest directory with the following naming format: <vmname>-job<jobid>_<stepno>_<taskno>-<report> 2. At the start of WineRunTask and WineRunWineTest delete any reference report in the task's directory (in case the task is restarted), then make new hard links to the current set of reference reports. Handle this in LogUtils::GrabReferenceReports() so this code is shared. 3. Add LogUtils::AddReferenceReport() to deal with copying the WineTest reports to var/latest. Call this function when WineRunTask and WineRunWineTest complete. 4. In GetNewLogErrors() initially mark all errors as new. Then diff the current report with each of the reference reports located in the task's directory in turn and remove any error that's not new from the set of new errors. Note that currently the reference logs are simple copies of the original WineTest report. This means these are large files which must be parsed again to extract errors. With the current $JobPurgeDays setting there will be around 20 reference logs which will require 20 times as much log parsing. So there are two optimizations one can do, both happening when adding a new reference report (i.e. in AddReferenceReport()): a. Instead of copying the full report, save only the errors. That's all the diff needs and this should reduce the size of the files by a factor of 10 (and thus speed up parsing). b. After saving a new reference file, diff it against the old reference files. Delete any old reference file that has no error not already present in the new reference file. This will not help much if the set of failures is different with every run. But otherwise this will speed up both the parsing and diffing. -- 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 4

[Bug 42770] New: test.winehq.org: Provide a view showing only the TestBot VMs
by wine-bugs＠winehq.org 03 May '21

03 May '21

https://bugs.winehq.org/show_bug.cgi?id=42770 Bug ID: 42770 Summary: test.winehq.org: Provide a view showing only the TestBot VMs Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- In Huw's words: > Something else that would be very useful is the ability to > display just the test bot VMs. These are the ones we care > about the most, and the ones that are possible to fix without > having to get a third-party to manually run a test. I find it > difficult to just keep track of these VMs when their results get > swamped by all the other machines’ failures. > > I‘d imagine this should be possible to do using static > pages. The root page (equivalent to data/index.html) > could be something like data/wtb_index.html. Clicking > on a build id would take you to data/build-id/wtb_index.html, > then clicking on an OS flavour would take you to > data/build-id/wtb_index_flavour.html. You’d also need some > way to toggle in and out of the mode. This should be pretty similar to adding the 'flat index' files mentioned in bug 39379. https://bugs.winehq.org/show_bug.cgi?id=39379 An interesting alternative would be to go the JavaScript way and make the index files, which are essentially big tables, sortable, filterable on the client-side. -- 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

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 February 2021