November 2021 - Wine-Bugs - list.winehq.org

[Bug 52090] New: New failures in d3d11:d3d11 in Wine
by WineHQ Bugzilla Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=52090 Bug ID: 52090 Summary: New failures in d3d11:d3d11 in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Running d3d11:d3d11 on the TestBot debiant2 VM used to consistently produce 70 failures. But on 2021-11-04 the failure mix changed and the count increased to a steady 77 failures. The new failures happen in void test_fractional_viewports() and test_negative_viewports(). In typical unified diff style: -d3d11.c:5926: Test failed: Got unexpected CPrimitives count: 3. -d3d11.c:5943: Test failed: Got unexpected CPrimitives count: 3. +d3d11.c:28242: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28242: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. +d3d11.c:28251: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28251: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. +d3d11.c:28188: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. +d3d11.c:28242: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28188: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. +d3d11.c:28251: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28188: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. https://test.winehq.org/data/patterns.html#d3d11:d3d11 A bisect shows that the new failures started with the commit below: commit 26a53f674c234aaba4a85ec36bae48384899b705 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Wed Nov 3 20:15:30 2021 +0300 wined3d: Emulate fractional viewports if GL doesn't support them. This allows test_fractional_viewports to pass regardless of GL capabilies. I don't think we can get rid of WINED3D_PIXEL_CENTER_INTEGER (and add +0.5 in the client libs) due to vpos in d3d9 shaders. Signed-off-by: Stefan Dösinger <stefan(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(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 5

[Bug 51703] New: Opening Omnisphere Authorization window with a large amount of text on the clipboard causes an unhandled page fault
by WineHQ Bugzilla Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=51703 Bug ID: 51703 Summary: Opening Omnisphere Authorization window with a large amount of text on the clipboard causes an unhandled page fault Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrew(a)amorgan.xyz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70576 --> https://bugs.winehq.org/attachment.cgi?id=70576 backtrace I'm attempting to register my Spectatronics Omnisphere installation, which requires pasting an authorization code into the application. However, it appears that during authorization Omnisphere will attempt to read the contents of the clipboard in order to validate the authorization code, but upon doing so with any clipboard size that is significantly large, the application will crash with a page fault. Unfortunately, I cannot work around this issue as there is no option to type in the authorization code rather than pasting it in in full. Running the application with a small amount of text on the clipboard works fine. I also found that simply having 500 letter 'A's on my clipboard ('AAAAA...') will also cause the application to crash, so it appears that the characters involved does not matter - only the size of the clipboard's content does. Through trial and error I have found that a string of 110 A's is fine, but 111 A's on the clipboard will cause the application to crash. -- 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 45896] New: Dungeon Keeper 2 - Patch'ed v1.8 - doesn't start
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=45896 Bug ID: 45896 Summary: Dungeon Keeper 2 - Patch'ed v1.8 - doesn't start Product: Wine Version: 3.0.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thomas000bauer(a)gmail.com Distribution: --- Hi, i have tried to launch Dungeon Keeper 2 with the "unofficial" Patch to Version v1.8 so the necessity of a noCD Crack is obsolete. When i try to execute the "wine" command it takes about 4-5seconds with/and without attached debug-log export to get me a new command line. But nothing else happens, no Output in the Terminal no nothing. I do as followed to launch Dungeon Keeper 2: [code] export WINEPREFIX="/media/daten350/games-software/wine/dungeon.keeper.2" export WINEDEBUG=+timestamp,+tid,+loaddll,+winediag,+synchronous,+seh,+x11drv,+xrandr cd /media/daten350/games-software/wine/dungeon.keeper.2/drive_c/Program\ Files\ \(x86\)/Bullfrog/Dungeon\ Keeper\ 2/ wine Dkii.exe &>~/wine-vanilla-3.0.2_loaddl_wgl_log.txt [/code] here the Log is on Git [url]https://gist.github.com/Phenicien/16b7fb1230df0e1becc0845351e80cdb[/url] as well as i have attached it as a .zip file. I already created a Form Thread [url]https://forum.winehq.org/viewtopic.php?f=2&t=31165&sid=b68c344b875b8472…] I'm grateful for every help or solution. Thanks -- 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 50527] New: Dying Light shows a black screen after starting a new game
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=50527 Bug ID: 50527 Summary: Dying Light shows a black screen after starting a new game Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: 8b3cc57df0b791ca6c33f383f9358e1613206b84 Distribution: --- Reverting the commit helps. -- 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 50100] New: Unable to log in to the Bentley CONNECTION client
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=50100 Bug ID: 50100 Summary: Unable to log in to the Bentley CONNECTION client Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: mira.rielynd(a)yandex.ru Distribution: --- Created attachment 68582 --> https://bugs.winehq.org/attachment.cgi?id=68582 Console output of running the CONNECT Client As I'm trying to log into the Bentley CONNECTION Client it does absolutely nothing after entering username and password. However, after looking at the terminal output, there is one specific fixme/error which comes up every time I'm interacting with buttons (which comes up twice): 0024:fixme:mshtml:ActiveScriptSite_OnScriptError ([xxx])->([xxx]) (See the full log of it. Every single time I'm moving my mouse above the screen I get bombarded with 'fixme:msctf:InputProcessorProfileMgr_GetActiveProfile' and 'TSFStaticSink::EnsureInitActiveLanguageProfile(), FAILED to get active TIP keyboard' messages) I tried it with the native mshtml as well, and there's the exact same message (somehow). Is there something I can try out myself for an fixing attempt/ Do you need any other info? I'm running Gentoo with the default/linux/amd64/17.1/desktop/plasma/systemd profile, and wine-vanilla-5.20. -- 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 15

[Bug 52074] New: crash in open source flight simulator Rowan's Battle of Britain
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=52074 Bug ID: 52074 Summary: crash in open source flight simulator Rowan's Battle of Britain Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: freehand(a)tutanota.com Distribution: --- Created attachment 71086 --> https://bugs.winehq.org/attachment.cgi?id=71086 text from crash dialog box In the open source combat flight simulation, The open source combat flight simulation Rowan's Battle of Britain crashes when entering the 3D view from the 2D map view. The text from the crash dialog box is attached as the file "textFromErrorDialog.txt" Rowan's Battle of Britain is open source. The source code is here: https://github.com/gondur/BOB_Src To install and run Rowan's Battle of Britain, download this tar file: https://www.mediafire.com/file/kx3kmpmnesl959y/esports-for-engineers-43b.ta… unpack it, cd to THU/BattleOfBritain and then execute the bash script ./battleOfBritain.sh -- 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 23782] New: Spaceforce Rogue Universe crashes in game videos (iccvid.dll)
by wine-bugs＠winehq.org Jan. 7, 2022

Jan. 7, 2022

http://bugs.winehq.org/show_bug.cgi?id=23782 Summary: Spaceforce Rogue Universe crashes in game videos (iccvid.dll) Product: Wine Version: 1.2 Platform: x86 URL: http://www.gamershell.com/download_19328.shtml OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=29821) --> (http://bugs.winehq.org/attachment.cgi?id=29821) traces log using only built-in dlls Spaceforce: RU always crashes when trying to play the game videos. Both the demo and the patched retail version is affected. How to reproduce the issue in the demo: 1. Install the demo then launch it from the game's /System directory, either by Start.exe (the launcher), or directly the game by SpaceForce.exe. Wine will crash when trying to play the intro video/company logos. The crash is always reproducible, when using Wine's built-in dlls. output of the 'file' command on one of the game's video files: Intro001.mff: RIFF (little-endian) data, AVI, 640 x 480, 25.00 fps, video: uncompressed Cinepak, audio: uncompressed PCM (stereo, 44100 Hz) If I replace the built-in iccvid.dll with the free version of the cinepak codec (available: http://www.probo.com/cinepak.htm) the issue changes into: Wine doesn't crash anymore, but plays the videos in a strange way: almost the whole screen is black, only a small chunk of the video can be seen at the left side of the screen. No music during the videos and in the whole game, though. Fedora 13 Nvidia 7600 series card / driver 195.36.31 The attached log shows traces, using winedebug=+ole,+msvideo,+iccvid,+avifile,+amstream,+quartz (all dlls are the built-in ones) -- 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 52071] New: mshtml:script fails in externalDisp_InvokeEx() on Windows
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=52071 Bug ID: 52071 Summary: mshtml:script fails in externalDisp_InvokeEx() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mshtml:script fails in externalDisp_InvokeEx() on all Windows versions from 7 to 10/21H1. script.c:640: L"/index.html?11:doc_mode: Testing compatibility mode 11" script.c:624: Test failed: L"/index.html?11:elem_attr: removed ondblclick string = function ondblclick(event)\n{\nstring\n}" script.c:3417: Running documentmode.js script in edge;123 mode... script.c:640: L"/index.html?11:doc_mode: Testing compatibility mode 11" script.c:624: Test failed: L"/index.html?11:elem_attr: removed ondblclick string = function ondblclick(event)\n{\nstring\n}" https://test.winehq.org/data/patterns.html#mshtml:script A bisect shows that this failure appeared with the commit below: commit 6b2c20c6a1aa046c5f0317221b52609bcaa11295 Author: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Date: Tue Nov 16 19:58:16 2021 +0200 mshtml: Clear the string dprop associated with the builtin attribute when removing it. Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Note that this failure was reported by the TestBot: https://www.winehq.org/pipermail/wine-devel/2021-November/200830.html https://source.winehq.org/patches/data/219693.testbot -- 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 49174] New: Duplicate checking iter->parent in mshtml/htmlwindow.c
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=49174 Bug ID: 49174 Summary: Duplicate checking iter->parent in mshtml/htmlwindow.c Product: Wine Version: 5.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal54(a)gmail.com Distribution: --- Should be probably `iter && iter->parent` https://github.com/wine-mirror/wine/blob/59987bc9ecdd0dbafd768a95c21a14884b… -- 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 49099] New: MIDI events sent to all devices at once
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=49099 Bug ID: 49099 Summary: MIDI events sent to all devices at once Product: Wine Version: 5.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: jpm(a)it-he.org Distribution: --- I am using an old version of Cakewalk SONAR to control a large number of synthesizers. These are connected via an ESI M8Uex MIDI interface, which appears to ALSA as 16 MIDI outputs and outputs over a single USB connection ("ESI M8U eX - ESI M8U eX MIDI 1", "ESI M8U eX - ESI M8U eX MIDI 2"). In WINE 4.x this has been working fine, but a recent Ubuntu upgrade has bumped WINE to 5.5, and now SONAR is sending the same MIDI commands to all 16 ports on the ESI device instead of just e.g. port 2. For example, if you play the organ part in isolation, it should be sending these notes to the Hammond XM-1 module on port 4 of the ESI device. But it is also sending these to the drum machine on port 6, the Triton on port 1 and so on. It does not appear to be sending the MIDI data to the Roland UM-ONE interface also attached the system, however. As a workaround I have reverted to an old version of winealsa.drv.so from 2017 which I happened to have lying around from some earlier experiment. This has made the problem go away. I can try building WINE myself to find the point at which the bug was introduced, but looking at the recent changes in git I'd be inclined to suspect this commit: https://github.com/wine-mirror/wine/commit/3d57cc2863f2f9a5ace40d29317b3ff4… ...since it appears to be using a much less fine-grained approach to sending MIDI data to the devices. It is quite likely that it works fine for the case of a USB synthesizer where one instrument is on one port, but for something like a 4x4 MIDI interface there appears to be a regression. Thanks, Joseph P Morris -- 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