wine-bugs

wine-bugs@winehq.org

1 participants
158783 discussions

[Bug 53248] New: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_coop_level_mode_set() sometimes fails on Windows due to DDERR_SURFACELOST
by WineHQ Bugzilla 23 Mar '23

23 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53248 Bug ID: 53248 Summary: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_coop_level_mode_set() sometimes fails on Windows due to DDERR_SURFACELOST Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_coop_level_mode_set() sometimes fails on Windows due to DDERR_SURFACELOST. There are two variants: ddraw1.c:3504: Test failed: Got unexpected hr 0x887601c2. or ddraw1.c:3542: Test failed: Failed to create surface, hr 0x887601c2. https://test.winehq.org/data/patterns.html#ddraw:ddraw1 https://test.winehq.org/data/patterns.html#ddraw:ddraw2 https://test.winehq.org/data/patterns.html#ddraw:ddraw4 https://test.winehq.org/data/patterns.html#ddraw:ddraw7 These failures: * Happen on the Windows 8 TestBot VMs * Don't happen on the Windows 10 TestBot VMs * Happened on the cw-rx460 Windows 10 2009+ configurations. * Did not happen on cw-gtx560. So they appear to be very dependent on the Windows driver which is to be expected I guess. -- 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 54723] New: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_p8_blit() fails on Windows 11 + AMD
by WineHQ Bugzilla 23 Mar '23

23 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54723 Bug ID: 54723 Summary: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_p8_blit() fails on Windows 11 + AMD Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_p8_blit() fails on Windows 11 + AMD: ddraw7.c:9518: Test failed: Got unexpected P8 color key blit result. The same failure happens in ddraw1, ddraw2 and ddraw4. See https://test.winehq.org/data/patterns.html#ddraw:ddraw1 & co This failure is systematic on Windows 11 + AMD and has never happened in any of the other test configurations. -- 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 54693] New: Freedom Planet 2 performance is atrocious with near-zero hardware load
by WineHQ Bugzilla 23 Mar '23

23 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54693 Bug ID: 54693 Summary: Freedom Planet 2 performance is atrocious with near-zero hardware load Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: virtuousfox(a)gmail.com Distribution: --- Created attachment 74203 --> https://bugs.winehq.org/attachment.cgi?id=74203 wine64 FP2.exe log When running Freedom Planet 2 v1.2.0 on LGA-2011/Xeon E5-2697/AMD RX580 under rolling-release openSUSE Tumbleweed it gets atrocious ~10 fps in levels and ~45 fps in menus with ~1% GPU load, despite being simple low-res 2D game. The executable is 32-bit d3d11 Unity-based app. I actually use wine-staging but I can't test vanilla now to see if its different. However, one interesting part is that enabling WINEESYNC tanks fps more than twice of even that: <5 from 10. With WINEESYNC=0 CPU load is mostly on single core to about 60-80% but with WINEESYNC=1 load is shared among all 24 CPU threads to be almost unnoticeable, yet performance is literal slide-show. Tested with wine's GL rendering and dxvk with same result, wine's vulkan renderer hangs at startup. In comparison, Dishonored 2, pretty visually taxing game, maxed out with same wine/dxvk settings gives buttery-smooth native 72 fps (OC 60 fps panel) with <80% GPU load. There is nothing obvious in what little logs it spews out and there seem to be no audio or visual glitches. I'm quite at a loss to figure out what might be the bottleneck. -- 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 2

[Bug 54716] New: Hard Time (2007): incorrect text rendering caused by font anti-aliasing
by WineHQ Bugzilla 23 Mar '23

23 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54716 Bug ID: 54716 Summary: Hard Time (2007): incorrect text rendering caused by font anti-aliasing Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: liamstevens2287(a)gmail.com Distribution: --- Created attachment 74224 --> https://bugs.winehq.org/attachment.cgi?id=74224 A screenshot of 2007's 'Hard Time' showing incorrect font rendering on the left, with the intended appearance on the right. Distros tested: Arch Linux, EndeavourOS, SteamOS Versions tested: Wine 4.21, 7.2, 8.3, 8.4, and all versions of Valve Proton 2007 indie game 'Hard Time' incorrectly displays white outlines around all text, caused by font anti-aliasing being forced. On Windows, the game correctly runs with no AA without tweaking required by the user. Disabling font anti-aliasing at the Xorg level or by using your DE's options works around this, as there is no way to disable font AA in Wine itself (that I can tell). The game is free, and the official download is located at http://www.mdickie.com/downloads.htm (direct link at http://www.mdickie.com/downloads/new/hardtime_setup.exe) Attached is an image of two screenshots with font anti-aliasing enabled on the left, and disabled on the right to show the intended appearance. As this is my first Wine bug, please do tell me if there is any other information which is needed. Many 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.

1 2

[Bug 54719] New: MarioKartToolbox: Open file button enabled but does nothing
by WineHQ Bugzilla 22 Mar '23

22 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54719 Bug ID: 54719 Summary: MarioKartToolbox: Open file button enabled but does nothing Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: narkro555(a)gmail.com Distribution: --- Created attachment 74225 --> https://bugs.winehq.org/attachment.cgi?id=74225 Log from "wine MarioKartToolbox.exe &> output.txt" Upon starting the program, a file open dialog appears. Upon double clicking a valid program or clicking the open button after selecting one, nothing happens. The open button is at no point disabled. I was able to work around it by launching the program with a command line argument to the executable, but it was still very inconvenient as I now have to restart to switch projects or files. Downloaded from https://wiki.dshack.org/ File URL: https://cdn.discordapp.com/attachments/885622551362015272/88564165528847163… sha1sum: 1274b3a33de4133c116f99c3ef56246e17bb4847 MKTB_1680_RC1.7z -- 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 53456] New: kernel32:debugger - load_blackbox() sometimes fails for crash_and_debug() on Windows
by WineHQ Bugzilla 22 Mar '23

22 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53456 Bug ID: 53456 Summary: kernel32:debugger - load_blackbox() sometimes fails for crash_and_debug() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - load_blackbox() sometimes fails for crash_and_debug() on Windows: debugger.c:155: Test failed: unable to open 'C:\Users\winetest\AppData\Local\Temp\wt39FA.tmp' debugger.c:155: Test failed: failed to open: C:\Users\winetest\AppData\Local\Temp\wt39FA.tmp debugger.c:676: Test failed: the child and debugged pids don't match: 4840 != 1472 https://test.winehq.org/data/patterns.html#kernel32:debugger This happens on Window 8 to Windows 10 21H1 in both 32- and 64-bit tests but the failure rate appears to be below 2%. -- 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 54715] New: Several VST plugins dont know some knobs
by WineHQ Bugzilla 21 Mar '23

21 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54715 Bug ID: 54715 Summary: Several VST plugins dont know some knobs Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: assinkzkie(a)proton.me Distribution: --- Its the same as in this old Closed bug report, so it still exists. https://bugs.winehq.org/show_bug.cgi?id=41593 I tried the "MaxVersionGL" workaround already, but this didnt seem to work for me. relevant error is: err:d2d:d2d_bitmap_create Failed to create texture, hr 0x80070057. It happens in several plugins for me, For instance bx_opto (brainworks) and Black Rooster Audio VLA-2A -- 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 54304] New: user32:input - test_GetRawInputBuffer() sometimes gets unexpected GetRawInputData() success in Wine
by WineHQ Bugzilla 21 Mar '23

21 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54304 Bug ID: 54304 Summary: user32:input - test_GetRawInputBuffer() sometimes gets unexpected GetRawInputData() success in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:input - test_GetRawInputBuffer() sometimes gets unexpected GetRawInputData() success in Wine. This results in a group of 3 failures: input.c:2287: Test failed: GetRawInputData succeeded input.c:2288: Test failed: GetRawInputData returned deadbeef input.c:2421: Test failed: Spurious WM_INPUT messages See https://test.winehq.org/data/patterns.html#user32:input The first known instance goes back to 2022-08-29 and there has been roughly 2 failures per month since then with a two months gap (October & November). That makes it hard to know when this failure really appeared. Note that the 'spurious WM_INPUT messages' failure also appears on Windows. See bug 54053. -- 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 2

[Bug 52982] New: PotPlayer: Crashes and hangs
by WineHQ Bugzilla 21 Mar '23

21 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=52982 Bug ID: 52982 Summary: PotPlayer: Crashes and hangs Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bq74stlxvkpb(a)opayq.com Distribution: --- Created attachment 72350 --> https://bugs.winehq.org/attachment.cgi?id=72350 Terminal output when the application hangs PotPlayer crashes or hangs shortly after starting, or starting to play a video file. Default configuration (just with Windows 10 set). I'm trying to add a printscreen as a second attachment, but it seems I cannot have more than one attachment? Well, I can add it as a link, I guess: https://imgur.com/zedUjNf (other applications work correctly with these settings and all of those drive paths are accessible) I can't quite use a non-stable version, because this is my work laptop and my work needs for wine to work correctly at all times. It would be nice if I could watch videos through PotPlayer while on breaks, though! :) https://t1.daumcdn.net/potplayer/PotPlayer/Version/Latest/PotPlayerSetup64.… I've managed to get PotPlayer working for a bit, even playing videos without a hitch, but I have no idea why - upon closing it and relaunching, I was met with a hang (I'm going to place that in the attachment). Furthermore, the logging mini-application that is supposed to gather the logs for the crash also... crashed/hanged. Dammit! :D It's been like this for over 10 minutes: https://imgur.com/HEMRh2l I've decided to use the newest hang as the attachment. I don't know how to connect this bug to the App database other than to just post a link here: https://appdb.winehq.org/objectManager.php?sClass=application&iId=14890 PotPlayer version: 220420 (1.7.21632) O.S: Linux Mint 20.3 Una with Cinnamon -- 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 8

[Bug 51877] New: improve POSIX compatibility for wine-staging's patches/gitapply.sh
by WineHQ Bugzilla 21 Mar '23

21 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=51877 Bug ID: 51877 Summary: improve POSIX compatibility for wine-staging's patches/gitapply.sh Product: Wine-staging Version: 6.19 Hardware: x86-64 OS: other Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 70802 --> https://bugs.winehq.org/attachment.cgi?id=70802 Makes patches/gitapply.sh more POSIX compatible wine-staging's patches/patchinstall.sh can apply patches using Git commands, or CLI tools. It prefers Git commands, but when it detects that some parent directory is a Git repository, it passes --nogit to patches/gitapply.sh, which then starts using CLI tools which use various Linuxisms. On FreeBSD, the Git commands work, but since the Ports tree can itself be a Git repository, and Wine extracts under it (by default), they cannot always be used, falling back to CLI tools with Linuxisms that break. This patch makes patches/gitapply.sh more POSIX compatible, and gets it working on FreeBSD. -- 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 18

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