wine-bugs August 2020

wine-bugs@winehq.org

1 participants
6880 discussions

[Bug 30899] New: SlingPlayer 1.5 UI broken
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=30899 Bug #: 30899 Summary: SlingPlayer 1.5 UI broken Product: Wine Version: 1.5.6 Platform: x86-64 URL: http://download.slingmedia.com/player/pc/SlingPlayer-S etup-EU-1.5.1.343.exe OS/Version: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P4 Component: gdiplus AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk CC: madewokherd(a)gmail.com Classification: Unclassified Regression SHA1: dc3a08d840186c7692cc3cae45bdd517ab099e07 Created attachment 40512 --> http://bugs.winehq.org/attachment.cgi?id=40512 Corrupt UI in Wine 1.5.6 In Wine 1.5.6 the SlingPlayer UI appears broken (see attached screenshot). Problem not present in Wine 1.4. This is a regression. dc3a08d840186c7692cc3cae45bdd517ab099e07 is the first bad commit commit dc3a08d840186c7692cc3cae45bdd517ab099e07 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Tue Feb 14 13:50:59 2012 -0600 gdiplus: Rewrite SOFTWARE_GdipFillRegion to call brush_fill_pixels less. Reverting this commit fixes the problem. Workaround is native gdiplus. The only relevant output with built-in gdiplus is: fixme:gdiplus:resample_bitmap_pixel Unimplemented interpolation 7 A +gdiplus trace is enormous. -- 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 42502] New: SlingPlayer 1.5.1 crashes on load (Assertion failure)
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=42502 Bug ID: 42502 Summary: SlingPlayer 1.5.1 crashes on load (Assertion failure) Product: Wine Version: 2.2 Hardware: x86 URL: http://download.slingmedia.com/player/pc/SlingPlayer-S etup-EU-1.5.1.343.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: stefan(a)codeweavers.com Blocks: 17972, 18010, 31651, 38938 Regression SHA1: 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b Distribution: Ubuntu Created attachment 57376 --> https://bugs.winehq.org/attachment.cgi?id=57376 Wine 2.1 console output SlingPlayer 1.5.1 crashes around 98% of the time with an assertion failure, 1% of the time with a page fault, and 1% of the time it loads, but crashes later in a similar manner. The attached log shows an assertion failure, though the debugger doesn't run. wine: Assertion failed at address 0xb77df428 (thread 0009), starting debugger... *** Error in `/home/test/.wine/drive_c/Program Files/Sling Media/SlingPlayer/SlingPlayer.exe': corrupted double-linked list: 0x7c3ba500 *** This is a regression. 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b is the first bad commit commit 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Thu Jul 30 18:50:15 2015 +0200 wined3d: Try to detect the polygon offset scale value. FEAR draws the same geometry twice, the second time using zfunc=equal. In both cases it sets a huge depth bias of -0.5, presumably to get better precision for the fragile Z comparison. The GL polygon offset we set ends up being so large that it pulls the geometry into the negative Z range. It isn't clipped (or no longer, older NV drivers probably had a separate bug there), but the Z value gets clamped to 0.0 in the first draw and doesn't match the incoming Z in the second draw. This commit cannot be automatically reverted in latest git. No known workaround. The crash is avoided by running it under Valgrind. Optional native gdiplus to work around Bug 30899. -- 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 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 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 38939] New: u-blox U-center 8,17 crashes when attempting to open view->Packet Console
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=38939 Bug ID: 38939 Summary: u-blox U-center 8,17 crashes when attempting to open view->Packet Console Product: Wine Version: 1.6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: david.t.kerns(a)gmail.com Distribution: --- Created attachment 51875 --> https://bugs.winehq.org/attachment.cgi?id=51875 stack trace Cent-OS 6.4 yum install wine (from epel) wine u-center.exe select com port most things work as expected View-> Packet Console crashes every time -- 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 11

[Bug 47800] New: Better detect Windows reboots
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=47800 Bug ID: 47800 Summary: Better detect Windows reboots 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 test crashes Windows in a VM we get typically get an error like this: channel 2: open failed: connect failed: Connection refused channel 2: open failed: connect failed: Connection refused channel 2: open failed: connect failed: Connection refused An error occurred while waiting for the test to complete: network read got a premature EOF (wait2/connect:AgentVersion.h:0/9) The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died) The previous 2 run(s) terminated abnormally Nowadays most VMs autologin and autostart the TestAgent server with the --show-restarts option. What this does is pop up a dialog saying: TestAgentd.exe was restarted (2). Did Windows reboot? This is a telltale sign that Windows indeed rebooted (or that the TestBot administrator incorrectly set up the VM but then you'd see that dialog in all screenshots of that VM). The way this works is that when given the --show-restarts option the TestAgent server increases a persistent counter every time it starts. Normally the TestBot administrator will have reset that counter so it will be set to one such that a reboot will push it to 2 prompting this dialog. What's interesting is that this counter is accessible from the client with getproperties("start.counter"). So the WineRun*.pl script can know if the VM was indeed rebooted. But from the log above we also notice that they don't leave enough time for the VM to reboot and thus fail to reestablish the connection to the TestAgent server. This could be solved by adding a call to SetConnectionTimeout(,,$WaitForBoot) in the strategic places. Then in most cases the WineRun*.pl scripts could conclusively say that Windows crashed and rebooted. -- 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

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 August 2020