November 2019 - Wine-bugs - list.winehq.org

[Bug 45291] New: Dauntless Open Beta : Cant play Intro Video resulting in not responding black screen
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=45291 Bug ID: 45291 Summary: Dauntless Open Beta : Cant play Intro Video resulting in not responding black screen Product: Wine Version: 3.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: asembus(a)gmail.com Distribution: --- Tried to test the open beta version for dauntless with addtional dotnet installation. the launcher works fine but when the game start it doesnt show intro video and ends up with black screen. i've read the log and it seems the error is caused when the video cannot be shown [2018-06-02T11:11:33,434][ 0][LogMediaUtils][Error]Cannot play file://../../../Archon/Content/MoviesPackaged/MediaExample.mp4, because none of the enabled media player plug-ins support it: -- 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 48132] New: Elite Dangerous launcher broken (regression since wine-staging-4.20)
by WineHQ Bugzilla 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=48132 Bug ID: 48132 Summary: Elite Dangerous launcher broken (regression since wine-staging-4.20) Product: Wine-staging Version: 4.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 65724 --> https://bugs.winehq.org/attachment.cgi?id=65724 screenshots The Elite Dangerous launcher is broken, when using wine-staging-4.20. It's using 100 % of one CPU core, freezes after the first click and is graphically broken (see attached screenshots). It's a regression. Everything is fine when using either wine-4.20 or wine-staging-4.19. Something suspicious on the shell: 0065:fixme:d3d9:shader_validator_stub2 ./wine-staging-4.20/patches/patchinstall.sh DESTDIR=wine-4.20 --all -W uxtheme-CloseThemeClass -W uxtheme-GTK_Theming Tested workarounds: Use d9vk or gallium-nine. https://github.com/Joshua-Ashton/d9vk/releases (needs a Vulkan capable GPU) https://github.com/iXit/wine-nine-standalone (needs a Radeon-GPU or a very, very recent Intel-GPU) winetricks galliumnine -- 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 44089] New: Strider crashes after loading screen
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=44089 Bug ID: 44089 Summary: Strider crashes after loading screen Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: strider(a)strycore.com Distribution: --- Created attachment 59805 --> https://bugs.winehq.org/attachment.cgi?id=59805 backtrace of the crash While the main menu works fine, when starting a game, the game crashes. This is a regression that started in Wine Staging 2.16, when the deferred context patch (https://dev.wine-staging.com/patches/181/) was introduced. I had a build of Wine Staging 2.15 with that patch enabled and I noticed crashes starting with that build and onward until the latest tested, Staging 2.21. -- 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 48089] New: Origin update hangs with Esync enabled
by WineHQ Bugzilla 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=48089 Bug ID: 48089 Summary: Origin update hangs with Esync enabled Product: Wine-staging Version: 4.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 65647 --> https://bugs.winehq.org/attachment.cgi?id=65647 +server When Origin has an update available to be installed and Esync is enabled by passing WINEESYNC=1 envar, the updater hangs and never finishes. Disabling Esync solves the issue and allows Origin to complete the update. Attaching +server log. How to reproduce: 1) Create a prefix (64-bit will do) 2) Install DXVK using winetricks (app doesn't work correctly without it) 3) Add an override for OriginThinSetupInternal.exe and set it to disabled so that the app doesn't update during installation and a backup could be made for testing purposes. 4) Install an older version of Origin (you can use this link https://lutris.nyc3.cdn.digitaloceanspaces.com/games/origin/OriginSetup.exe) 5) Kill all processes in the prefix and remove override for OriginThinSetupInternal.exe 6) Run Origin.exe with WINEESYNC=1 envar passed on. Behavior with Esync disabled: Update window appears, then closes after a while, reopens and finishes the update. Behavior with Esync enabled: Update window appears, then closes but never reopens. The update hangs and never finishes. During the test, regular wine-staging build was used, but I've also tried it with a custom build that ports Fsync from Proton to Wine and it has the same issue when Fsync is in use (which it indicated in the logs). -- 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 46790] New: Witcher 3 hangs shortly after launch; may show ' press space to skip'
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=46790 Bug ID: 46790 Summary: Witcher 3 hangs shortly after launch; may show 'press space to skip' Product: Wine-staging Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: riddervancocagne(a)hotmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63809 --> https://bugs.winehq.org/attachment.cgi?id=63809 Zip file containing api trace, partial console output and Witcher 3 crash report. If The Witcher 3 is launched using Wine 4.3 Staging, it will grind to a halt almost immediately. This is no ordinary black screen, as the game often does display the text 'Press space to skip'. Pressing space has no effect, however. I have also tried running the game on Wine 3.03 Stable, Wine 4.0 Stable and Wine 4.3 Devel. All three variants launch and run the game. Attached: partial console output, api trace and Witcher 3 crash report generated by the game itself. -- 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 12

[Bug 47365] New: jittering caused by mouse input in vkquake
by wine-bugs＠winehq.org 24 Apr '20

24 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=47365 Bug ID: 47365 Summary: jittering caused by mouse input in vkquake Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tempel.julian(a)gmail.com Distribution: --- Created attachment 64704 --> https://bugs.winehq.org/attachment.cgi?id=64704 wine log In vkquake, enable vsync (and set an fps limit well above refresh rate via "host_maxfps" command if your using a refreshrate of greater than 60Hz, as the game caps to 72fps by default), start a new game and pan the camera via the keyboard's arrow keys. It should be absolutely smooth. Now, pan the camera by moving the mouse instead -> there is jitter. After alt + Tab to the desktop and back into the game, this jitter usually is gone. Still, it shouldn't occur in the first place, as it doesn't happen on Windows. I made sure this isn't a driver issue by checking with both modesetting and xf86-video-amdgpu DDX and also on xwayland. In xwayland, the issue is less distinct, but still noticeable. Happens with both wine 4.9, wine-staging 4.9 and my custom 4.10 build (4.10 not yet in Arch repository). Get vkquake here: https://github.com/Novum/vkQuake/releases/download/1.01.0/vkquake-1.01.0_wi… You also need the game's free demo content, copy the "id1" folder into the main folder. Since the official servers usually are a mess, you can get it from here as well: https://bugs.freedesktop.org/attachment.cgi?id=143128 -- 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 46633] New: unimplemented function: kernel32.dll.startthreadpoolio
by wine-bugs＠winehq.org 24 Apr '20

24 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=46633 Bug ID: 46633 Summary: unimplemented function: kernel32.dll.startthreadpoolio Product: Wine Version: 4.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mushipao(a)gmail.com Distribution: --- Created attachment 63542 --> https://bugs.winehq.org/attachment.cgi?id=63542 backtrace of exception 3rd party, proprietary software errors out in Wine. 0157:fixme:thread:CreateThreadpoolIo (0x64, 0x42fca0, 0x5fc2a0, (nil)): stub wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Unimplemented function KERNEL32.dll.StartThreadpoolIo called at address 0x7bc51e39 (thread 0157), starting debugger... -- 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 18

[Bug 18104] New: Final Draft: text to speech fails
by wine-bugs＠winehq.org 24 Apr '20

24 Apr '20

http://bugs.winehq.org/show_bug.cgi?id=18104 Summary: Final Draft: text to speech fails Product: Wine Version: 1.1.19 Platform: All URL: http://www.finaldraft.com/downloads/demo-final-draft.php OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jens(a)porup.com Final Draft is the screenwriter's standard word processor. It offers a text to speech feature that does not work in wine. It doesn't break anything if you try; the buttons just don't do anything at all. Terminal output coming soon. -- 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 23

[Bug 42136] New: switching tab in sapi.cpl crashes control
by wine-bugs＠winehq.org 24 Apr '20

24 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=42136 Bug ID: 42136 Summary: switching tab in sapi.cpl crashes control Product: Wine Version: 2.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fiendishx(a)gmail.com Distribution: --- Created attachment 56693 --> https://bugs.winehq.org/attachment.cgi?id=56693 console log sapi.cpl is installed by the Microsoft Speech SDK installer from https://download.microsoft.com/download/B/4/3/B4314928-7B71-4336-9DE7-6FA4C… (or via winetricks) $ wine control '.wine/drive_c/Program Files (x86)/Common Files/Microsoft Shared/Speech/sapi.cpl' brings up the Speech Properties control panel. Choosing the tab labeled "Text To Speech" crashes the control. Console log attached. -- 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 48052] New: kernel32:debugger - Wine randomly fails to get the thread context
by WineHQ Bugzilla 24 Apr '20

24 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=48052 Bug ID: 48052 Summary: kernel32:debugger - Wine randomly fails to get the thread context Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The kernel32:debugger test randomly fails with a variable number of these failures: debugger.c:320: Test failed: GetThreadContext failed: 5 debugger.c:320: Test failed: GetThreadContext failed: 5 debugger.c:320: Test failed: GetThreadContext failed: 5 debugger.c:320: Test failed: GetThreadContext failed: 5 See https://test.winehq.org/data/tests/kernel32:debugger.html These happen in test_debugger(), when fetch_process_context() tries to get the context of each thread. In Wine GetThreadContext() randomly fails causing a variable number of the above messages depending on how many threads are impacted. All three Wine builds are impacted. The ERROR_ACCESS_DENIED probably comes from get_handle_obj() in server/handle.c. Given that this test was added to test a Wine exception handling race (*), maybe the race is still present? (*) Based on the commit message for: commit 42a9b58b066ff374148cee088ac57cfba46e3b76 Author: Jacek Caban <jacek(a)codeweavers.com> AuthorDate: Mon Aug 26 19:37:20 2019 +0200 kernel32/tests: Add exception handling race test. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The tests were later enabled on Wine by: commit 27da4fa4498c3b6e0e46c72a9cdd13b620726e92 Author: Jacek Caban <jacek(a)codeweavers.com> AuthorDate: Fri Sep 20 16:33:53 2019 +0200 kernel32/tests: Enable debug break exception race tests on i386 Wine. Signed-off-by: Jacek Caban <jacek(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 7