wine-bugs October 2020

wine-bugs@winehq.org

1 participants
7052 discussions

[Bug 49679] New: Regression: deadlock in installer for VB6 enterprise edition
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49679 Bug ID: 49679 Summary: Regression: deadlock in installer for VB6 enterprise edition Product: Wine Version: 5.14 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: comsvcs Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com Distribution: --- 0368:err:ntdll:RtlpWaitForCriticalSection section 7BCC116C "loader.c: loader_section" wait timed out in thread 0368, blocked by 00c4, retrying (60 sec) Bisected to this commit: ac1bb4536473eb705d5fa828406fa4eb473b9f41 is the first bad commit commit ac1bb4536473eb705d5fa828406fa4eb473b9f41 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Thu Feb 7 12:21:34 2019 -0600 comsvcs: Create an implicit MTA thread in RegisterDispenser(). Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=46581 Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 5e4bf1bf4c22a70a87f14cc837b82c61e9d15c8e b40e6808759cf31e7e44519110c6ed0222793ef6 M dlls Reverse-applying that commit's changes to master fixes the problem. -- 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 48336] New: Can't connect to server with HTTP 503
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=48336 Bug ID: 48336 Summary: Can't connect to server with HTTP 503 Product: Wine Version: 5.0-rc2 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rmkk(a)atlas.cz Created attachment 66071 --> https://bugs.winehq.org/attachment.cgi?id=66071 Debug log from macos I'm using "Sparx Enterprise Architect" on Wine@MacOS, comparing to stable Wine 4.0.3 version, new 5.0-rc2 failed to connect to cloud server with HTTP status 503. Both - stable and rc2 prefixes - are installed in parallel side by side and set in the same way. I tried to copy log records that hopefully can relate to the cause, but I'm not sure. Thanks for assessment. -- 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 31

[Bug 50008] New: Metro Exodus fails to launch since commit fde5967f725624c5ee4995dcbe22f262979c5c9c
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=50008 Bug ID: 50008 Summary: Metro Exodus fails to launch since commit fde5967f725624c5ee4995dcbe22f262979c5c9c Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: andrewathalye(a)outlook.com Distribution: --- Since commit fde5967f725624c5ee4995dcbe22f262979c5c9c to wine, which modified the inheritance behaviour of handles upon process creation, Metro Exodus is unable to start up and instead hangs after displaying a brief message about System Information (which also occurs in working releases, without the hang). This was tested using the Epic Games version of Metro Exodus, launched by "legendary launch Snapdragon --wine=$PWD/wine64" (this was tested using git bisect, and validated to work from Wine 5.12 until this commit, after which it no longer launches.) Reverting the commit using git revert enabled the game to launch again successfully. Instructions to reproduce: 1. Fetch latest Wine from Git 2. Start a bisect from wine-5.17 (or earlier) until HEAD 3. Test Metro Exodus using the above command 4. The final commit, determined as "first bad," should be fde5967f725624c5ee4995dcbe22f262979c5c9c. This bug also occurs when launching Metro Exodus directly (without Legendary), under the same conditions. -- 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 9

[Bug 34558] New: Alawar launcher fails to start after game has been registered
by wine-bugs＠winehq.org 23 Oct '20

23 Oct '20

http://bugs.winehq.org/show_bug.cgi?id=34558 Bug #: 34558 Summary: Alawar launcher fails to start after game has been registered Product: Wine Version: 1.7.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thesource(a)mail.ru Classification: Unclassified Created attachment 46008 --> http://bugs.winehq.org/attachment.cgi?id=46008 Alawar launcher wine log Alawar game launcher starts properly when the game is in trial mode, but after it has been registered, launcher exits showing message box "Error: 198". According to log wine complains it can not create some ole objects. Judging by uuids it's something related to msxml, but winetricking msxml (3, 4, 6) does not help. Attaching log with WINEDEBUG=ole -- 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 29

[Bug 50020] New: mf:mf tests crash on Windows 7
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=50020 Bug ID: 50020 Summary: mf:mf tests crash on Windows 7 Product: Wine Version: 5.19 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: sven.wine(a)gmail.com I feel like these tests don't actually test the right thing. If I change https://source.winehq.org/git/wine.git/blob/0c249e6125fc9dc6ee86b4ef6ae0d9f… to hr = IMFMediaTypeHandler_GetMediaTypeByIndex(handler, count-1, &mediatype2); ok(hr == S_OK, "Failed to get media type, hr %#x.\n", hr); hr = IMFMediaTypeHandler_GetMediaTypeByIndex(handler, count-1, &mediatype3); ok(hr == S_OK, "Failed to get media type, hr %#x.\n", hr); I get Windows 7: mf.c:3017: Test failed: Unexpected hr 0. mf.c:3049: Test failed: Failed to set current type, hr 0xc00d36b4. mf.c:3053: Test failed: Unexpected instance. mf.c:3125: Test failed: Failed to get interface, hr 0. Windows 8: mf.c:3017: Test failed: Unexpected hr 0. mf.c:3049: Test failed: Failed to set current type, hr 0xc00d4650. mf.c:3053: Test failed: Unexpected instance. mf.c:3125: Test failed: Failed to get interface, hr 0. Windows 10 1507: mf.c:3017: Test failed: Unexpected hr 0. mf.c:3049: Test failed: Failed to set current type, hr 0xc00d4650. mf.c:3053: Test failed: Unexpected instance. mf.c:3125: Test failed: Failed to get interface, hr 0. Windows 10 1809: mf.c:3017: Test failed: Unexpected hr 0. This is sort of consistent across all versions. So I feel like Wine is currently mimicking behaviour that holds only for some random media type which happens to not work on Windows 7 (Wine currently only has one media type available from GetMediaTypeByIndex). -- 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 49950] New: d3d10:reflection tests crash
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49950 Bug ID: 49950 Summary: d3d10:reflection tests crash Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: sven.wine(a)gmail.com Regression SHA1: ae415a7df78cbcf73f39c12d347e5bdf468d1895 Distribution: --- Seems like a regression since ae415a7df78cbcf73f39c12d347e5bdf468d1895 On the first occurrence of the crash: reflection.c:940: Test failed: (0): got unexpected hr 80070057. reflection.c:940: this is the last test seen before the exception 0a9c:reflection: unhandled exception c0000005 at 004230F3 d3d10:reflection:0a9c done (-1073741819) in 0s Test failed: crash (c0000005) https://source.winehq.org/git/wine.git/?a=blob;f=dlls/d3dcompiler_43/tests/… -- 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 7

[Bug 49960] New: The Sims Complete Collection is stuck on playing intro
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49960 Bug ID: 49960 Summary: The Sims Complete Collection is stuck on playing intro Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- Created attachment 68351 --> https://bugs.winehq.org/attachment.cgi?id=68351 +amstream,+quartz,+gstreamer When launching The Sims Complete Collection on current master (5d5102f8498413f4b7e11f7da0509e7717fb3735) with staging patches applied, the game plays the intro jingle very choppily (with no image whatsoever) and gets stuck on a black a screen (the game doesn't allow to skip the intro). In the output, I see spam of this: 0024:fixme:amstream:ddraw_sample_Update Unsupported flags 0x3. If I comment out this section in ddrawstream.c: if (flags & ~SSUPDATE_ASYNC) { FIXME("Unsupported flags %#x.\n", flags); return E_NOTIMPL; } the jingle plays (with image and audio) for a single frame and then immediately ends, and the game starts the loading process. Attached is a log with +amstream,+quartz,+gstreamer debug channels enabled. -- 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 49673] New: Backpacker 3:Americana:unhandled exception
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49673 Bug ID: 49673 Summary: Backpacker 3:Americana:unhandled exception Product: Wine Version: 5.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chebanenkoigor93(a)gmail.com Distribution: --- Created attachment 67913 --> https://bugs.winehq.org/attachment.cgi?id=67913 backtrace I can't run that game in Wine,and that game can't be debugged. -- 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 13

[Bug 49661] New: Red Evil:black screen in game.
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49661 Bug ID: 49661 Summary: Red Evil:black screen in game. Product: Wine Version: 5.14 Hardware: x86 URL: https://store.steampowered.com/app/1169070/RED_EVIL/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chebanenkoigor93(a)gmail.com Distribution: --- Created attachment 67898 --> https://bugs.winehq.org/attachment.cgi?id=67898 screenshot There is black screen in Red Evil game,that makes it unplayable with Intel Ivy Bridge HD 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.

1 4

[Bug 49012] New: Application build with .NET CoreRT crashes due to FLS callbacks not being called
by WineHQ Bugzilla 23 Oct '20

23 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49012 Bug ID: 49012 Summary: Application build with .NET CoreRT crashes due to FLS callbacks not being called Product: Wine Version: 5.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernelbase Assignee: wine-bugs(a)winehq.org Reporter: pgofman(a)codeweavers.com Distribution: --- Created attachment 66990 --> https://bugs.winehq.org/attachment.cgi?id=66990 Patchset .NET CoreRT performs thread tear down in a FLS callback which is currently not called in Wine. If the tear down callback is not performed on thread termination, the application later crashes on accessing the data from already freed static TLS data storage area. The attached patchset is fixing the issue. -- 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

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