wine-bugs February 2021

wine-bugs@winehq.org

1 participants
6842 discussions

[Bug 44201] New: Unimplemented function mf.dll.MFGetService
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=44201 Bug ID: 44201 Summary: Unimplemented function mf.dll.MFGetService Product: Wine Version: 3.0-rc2 Hardware: x86 URL: http://download.slingmedia.com/player/pc/SP2/SlingPlay er-2.0.3508-Setup-EMEA.exe OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Regression SHA1: a679caedf6ebbce0e193afb200d1d888c2b9776d Distribution: Ubuntu Created attachment 59970 --> https://bugs.winehq.org/attachment.cgi?id=59970 Wine 3.0-rc2 console output SlingPlayer 2.0 crashes with unimplemented function mf.dll.MFGetService Although this is a new crash I don't feel that a regression test will achieve anything, as it is probably obvious where the issue lay. https://source.winehq.org/source/dlls/mf/mf.spec#0075 Workaround is "winetricks -q mf". -- 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 44142] New: steamwebhelper.exe crashes on wine-stagining 2.21 because NtQueryInformationFile fails
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=44142 Bug ID: 44142 Summary: steamwebhelper.exe crashes on wine-stagining 2.21 because NtQueryInformationFile fails Product: Wine-staging Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: twunknown(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59890 --> https://bugs.winehq.org/attachment.cgi?id=59890 backtrace steamwebhelper.exe crashes on wine staging 2.21 but not vanilla wine because querying FileNameInformation on a named pipe has been implemented. If NtQueryInformationFile is called after CreateFileW has been called on the named pipe (Which is what happens in the case of steamwebhelper.exe) Then it will return STATUS_BAD_DEVICE_TYPE which is unexpected and the process crashes. This is different to Windows 7 in which the call will succeed and the information will be returned. -- 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 50660] New: The "job result" emails sent to developers are too big
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50660 Bug ID: 50660 Summary: The "job result" emails sent to developers are too big Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When a job completes WineSendLog sends an email to the developer who submitted it. This email contains every log and test report. When the patch causes a full recompilation of Wine the resulting email can be pretty big: more than 10 MB (before base64 encoding). We could compress the logs which may make the attachments a bit less practical to read. We could also may skip the build logs if the build was sucessful, but the test reports could be big too. And all this information is available from the TestBot's Job Details page anyway. So is it really necessary to email it? Wouldn't it be sufficient to just have a link to the Job Details page and a summary of the result like in the email sent to wine-devel? -- 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 50447] New: DeSmuME-VS2019-x64-Release crash
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50447 Bug ID: 50447 Summary: DeSmuME-VS2019-x64-Release crash Product: Wine Version: 6.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Bertrand_mainville(a)protonmail.com Distribution: --- Created attachment 69061 --> https://bugs.winehq.org/attachment.cgi?id=69061 Terminal logs DeSmuME-VS2019-x64-Release crash. Download links: Official download link: https://ci.appveyor.com/project/zeromus/desmume/build/artifacts Archived link (direct link): https://web.archive.org/web/20210103213512/https://appveyorcidatav2.blob.co… SHA1: 4B48AD259A7C760D90F2322494BCEAED349A8BD9 -- 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 11

[Bug 44709] New: Take live/regular screenshots
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=44709 Bug ID: 44709 Summary: Take live/regular screenshots 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 used to have a 'live screenshot' feature. This feature had to be disabled due to Libvirt/QEmu issues and because it required the TestBot server to make a long blocking call. It would be nice to bring back this feature in some form. However it may be even better to bring it in a different form and simply take screenshots every 10 or 30 seconds and timestamp them. For a lot of tests the screenshots are likely to all be identical so this could be used for deduplication so that the storage footprint would not be too large. Then the JobDetails.pl page would allow the user to browse through the screenshots for each test run (making this nice would likely require some JavaScript). >From a technical standpoint an advantage of taking regular screenshots is that it would not involve the web server. Instead it would happen in a separate thread or a fork of WineRunTask.pl (see TakeScreenshot()). So this would side-step the blocking call issue. >From a developer point of view, all long-running tests would have multiple screenshots, even after they are completed (which is not the case for 'live screenshots'). -- 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 48353] New: Use In-Reply-To when identifying patch series
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=48353 Bug ID: 48353 Summary: Use In-Reply-To when identifying patch series 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 detects patchsets from the n/N pattern in the subject and then matches the different parts together based on the From email address and the total number of parts. This means if the TestBot receives the parts of two patchsets with the same number of parts and from the same developer at the same time it is likely to mix elements of the two patchsets, and thus fail to test them. However it is customary for patches in a series to all reference the first email in the patch series through the In-Reply-To and Message-ID fields. This could be used to resolve ambiguities in such a case. However we may not want to use this as the sole way to attach parts to the patchset in case setting In-Reply-To is not possible for some reason. -- 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 41582] New: We need a different case for pathnames to detect case dependant tests as failure
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=41582 Bug ID: 41582 Summary: We need a different case for pathnames to detect case dependant tests as failure Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: wine.dev(a)web.de Distribution: --- We need a different case for pathnames to detect case dependant tests as failure. My Win7 on the Laptop is using "tmp" and has failures because of such bugs. Example: http://test.winehq.org/data/e6e8ed47e6d6d245e4bbda13691eb714cf95a675/win7_d… Test fixed by: http://source.winehq.org/git/wine.git/commit/1ebbfb1a1d54c4573d79367261030d… I did not test with 'desktop' yet. -- 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 40832] New: MultiSpec 2.8.2016 32-Bit: Installs fine but crashes while opening tif images
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=40832 Bug ID: 40832 Summary: MultiSpec 2.8.2016 32-Bit: Installs fine but crashes while opening tif images Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kara067(a)gmail.com Distribution: --- Created attachment 54792 --> https://bugs.winehq.org/attachment.cgi?id=54792 Backtrace log of crash. MultiSpec is an free program for multi channel images (Satellite images etc..). Program runs first. But when I try to open a tif image it crashes. Crash log is in the attachment. I use Debian 64bit. -- 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 29

[Bug 50659] New: Allow creating multiple WineTest jobs in the Special Jobs page
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50659 Bug ID: 50659 Summary: Allow creating multiple WineTest jobs in the Special Jobs page Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The Special Jobs page allows creating one 32-bit and one 64-bit WineTest job at a time. That's usually ok but it becomes cumbersome when one wants to trigger a WineTest run on all the locale and multi-screen snapshots of a given VM after a configuration change. So it would be nice to modify the page to present the VM configurations a bit like the Submit Jobs page does. An improvement may be to present one column for each of the reconfig, win32, wow32 and wow64 configurations, as applicable to the VM on that line so one can select the precise mix of jobs to run. The could also be an extra column as a shortcut to select all the options on the line in one go. Then rather than creating one job per WineTest run it could also create just one for reconfigs, one for 32-bit WineTest, etc. -- 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 50658] New: The Special Jobs page does not take MissionCaps into account
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50658 Bug ID: 50658 Summary: The Special Jobs page does not take MissionCaps into account Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- A lot of Windows VM configurations have the following: Role=base|winetest Missions=exe64 MissionCaps=exe32 These VMs typically mirror a base VM for which we already run both 32- and 64-bit WineTest daily. Since these configurations typically only differ in the locale, running both bitnesses again would be redundant. So the above results in only the 64-bit WineTest being run, but still allows developers to submit 32-bit jobs if desired (e.g. if they want to run a 32-bit binary). But this configuration throws the "Special Jobs" page off and causes it to create an empty job when trying to run the 32-bit WineTest. It should really see that MissionCaps allows running 32-bit tests. However the issue comes from the shared AddWindowsTestJob() function: it should take MissionCaps into account without changing the behavior of CheckForWinetestUpdate.pl. -- 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

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