wine-bugs January 2023

wine-bugs@winehq.org

1 participants
3479 discussions

[Bug 52089] New: d2d1:d2d1 fails in test_draw_geometry() on Wine
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52089 Bug ID: 52089 Summary: d2d1:d2d1 fails in test_draw_geometry() on Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d2d1:d2d1 fails in test_draw_geometry() on the TestBot's debiant2 VM: d2d1.c:6664: Test failed: Figure does not match. d2d1.c:6672: Test failed: Figure does not match. d2d1.c:6680: Test failed: Figure does not match. d2d1.c:6688: Test failed: Figure does not match. d2d1.c:6664: Test failed: Figure does not match. d2d1.c:6672: Test failed: Figure does not match. d2d1.c:6680: Test failed: Figure does not match. d2d1.c:6688: Test failed: Figure does not match. (todos omitted for brevity) https://test.winehq.org/data/patterns.html#d2d1:d2d1 A bisect shows that the failures started with this commit: commit 044f5e109fd7bdb5a3c172240d6195faa87a1dce (HEAD, refs/bisect/bad) Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Wed Nov 3 20:15:28 2021 +0300 wined3d: Test if an offset is needed to get the correct filling convention. This fixes stray lines in GameFace GUIs, e.g. in World of Tanks. 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 13

[Bug 51268] New: Assembler messages: Error: no such instruction: `xsavec (%esp)'
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=51268 Bug ID: 51268 Summary: Assembler messages: Error: no such instruction: `xsavec (%esp)' Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)protonmail.com Distribution: --- Created attachment 70146 --> https://bugs.winehq.org/attachment.cgi?id=70146 log.txt in distro: # uname --kernel-release 3.0.66 # gcc --version 4.3.4 # ldd --version 2.10.1 config line: configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686" Compiling wine-6.10 fails with: Assembler messages: Error: no such instruction: `xsavec (%esp)' -- 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 54172] New: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_window_position() gets the size of the wrong screen in Wine
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54172 Bug ID: 54172 Summary: ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_window_position() gets the size of the wrong screen in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ddraw:ddraw1, ddraw:ddraw2, ddraw:ddraw4, ddraw:ddraw7 - test_window_position() gets the size of the wrong screen in Wine: ddraw1.c:14471: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). ddraw2.c:15385: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). ddraw4.c:18435: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). ddraw7.c:18702: Test failed: Expect window rect (0,0)-(1024,768), got (0,0)-(1024,737). See 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 never happen on debian11b which is a single-monitor configuration. $ xrandr | grep Virtual Virtual-1 connected primary 1024x768+0+0 0mm x 0mm Virtual-2 disconnected Virtual-3 disconnected Virtual-4 disconnected It also never happens on debian11 where both monitors have the same resolution: $ xrandr | grep Virtual Virtual-1 connected primary 1024x737+0+0 0mm x 0mm Virtual-2 connected 1024x737+1024+0 0mm x 0mm Virtual-3 disconnected Virtual-4 disconnected But it is systematic on the debiant VM where the two screens have different resolutions: $ xrandr | grep Virtual Virtual-1 connected primary 1024x768+0+0 0mm x 0mm Virtual-2 connected 1024x737+1024+0 0mm x 0mm Virtual-3 disconnected Virtual-4 disconnected Note: * I did not intentionally configure the two screens to have different resolutions but I did not fight it either because it's also not that uncommon in multi-monitor configurations. * The 737 pixel height is a bit weird but there is no dock. Really! I'm not sure how the X server picked these sizes. -- 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 54151] New: xactengine3_7:xact3 crashes when no speaker is connected
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54151 Bug ID: 54151 Summary: xactengine3_7:xact3 crashes when no speaker is connected Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: xactengine Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com xactengine3_7:xact3 crashes when no speaker is connected: xact3.c:209: Test failed: Cannot initialize engine, hr 0x88960001 xact3.c:215: Test failed: got hr 0x8ac70002 xact3.c:218: Test failed: got hr 0x8ac70002 xact3.c:224: Test failed: got hr 0x8ac70002 xact3.c:227: Test failed: got hr 0x8ac70002 xact3.c:235: Test failed: Cannot register notification, hr 0x8ac70002 xact3.c:243: Test failed: Cannot register notification, hr 0x8ac70002 xact3.c:249: Test failed: Cannot register notification, hr 0x8ac70002 xact3.c:259: Test failed: Cannot create a streaming wave bank, hr 0x8ac70002 xact3.c:259: this is the last test seen before the exception 0df8:xact3: unhandled exception c0000005 at 0000000000401A4C See https://test.winehq.org/data/patterns.html#xactengine3_7:xact3 Where: 0x88960001 == XAUDIO2_E_INVALID_CALL or XAUDIO20_E_XMA_DECODER_ERROR 0x8ac70002 == MAKE_HRESULT(SEVERITY_ERROR, FACILITY_XACTENGINE, XACTENGINE_E_NOTINITIALIZED) These failures only happen on w11pro64_amd and w11pro64_nv. What these have in common is that the sound is supposed to go through the graphics card's HDMI / DisplayPort connection. However those go to a dummy plug which emulates a screen... but not speakers. This causes Windows to disable the sound volume widget since it cannot detect any form of speaker. I suspect, but that may require confirmation, that this causes xact to refuse to initialize. More notes: * My fgtb-w10pro64-rx550 VM has the same audio-through-HDMI configuration but is connected to my real screen which does have speakers. So sound is not 'disabled'. * QEmu emulates an ich9 sound card in the regular w11pro64 test configuration and Spice (the virtual KVM) provides the remote speakers. So again sound is not 'disabled' (and I always lower the default volume in the VMs so I don't get deafened by the Windows boot sound). * Before 2022-12-09 the w11pro64 VM was missing many DirectX dlls which caused this test to be entirely skipped. This is why it did not crash on these test configurations before then. -- 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 52152] New: comctl32:edit gets unexpected heights in test_text_position_style() on Windows 10 1809+
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52152 Bug ID: 52152 Summary: comctl32:edit gets unexpected heights in test_text_position_style() on Windows 10 1809+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:edit gets unexpected heights in test_text_position_style() on Windows 10 1809+: edit.c:2090: Test failed: wrong height expected 16 got 17 edit.c:2091: Test failed: wrong height expected 16 got 18 edit.c:2092: Test failed: wrong height expected 16 got 26 edit.c:2100: Test failed: wrong height expected 16 got 17 edit.c:2101: Test failed: wrong height expected 16 got 19 edit.c:2103: Test failed: wrong height expected 16 got 18 edit.c:2111: Test failed: wrong height expected 16 got 17 edit.c:2113: Test failed: wrong height expected 16 got 24 edit.c:2121: Test failed: wrong height expected 16 got 17 edit.c:2123: Test failed: wrong height expected 16 got 24 edit.c:2134: Test failed: wrong height expected 16 got 17 edit.c:2135: Test failed: wrong height expected 16 got 18 edit.c:2136: Test failed: wrong height expected 16 got 26 edit.c:2144: Test failed: wrong height expected 16 got 17 edit.c:2145: Test failed: wrong height expected 16 got 19 edit.c:2147: Test failed: wrong height expected 16 got 18 edit.c:2155: Test failed: wrong height expected 16 got 17 edit.c:2157: Test failed: wrong height expected 16 got 24 edit.c:2165: Test failed: wrong height expected 16 got 17 edit.c:2167: Test failed: wrong height expected 16 got 24 https://test.winehq.org/data/patterns.html#comctl32:edit The set of bad heights is exactly the same on all failing configurations, regardless of the Windows version, graphics card or locale. So the failure really is related to a change that happened between 1709 and 1809. -- 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 6

[Bug 51420] New: likely regression: heavy lag to the point of brokenness running anything in wine. 158:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0158, blocked by 0144, retrying (60 sec)
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=51420 Bug ID: 51420 Summary: likely regression: heavy lag to the point of brokenness running anything in wine. 158:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0158, blocked by 0144, retrying (60 sec) Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mouse(a)dayrep.com Distribution: --- Debian bullseye using the winehq packages proprietary nvidia driver from Debian non-free Tested versions that work fine as before: 6.0.1, 6.10 Broken versions: 6.11, 6.12, staging-6.12 Running any program in wine, included or otherwise, is causing extremely poor systems performance and is very slow. As in you can see the mouse cursor move in steps and lagging behind inputs, or the file selection window of the wine uninstaller takes seconds to display the icons for folder contents and loads the one by one. This stops as soon as the wine process is killed again. Full difference in wine log between 6.10 (works fine) and 6.12 (bugged) reproduced below: 0158:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0158, blocked by 0144, retrying (60 sec) 0168:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0168, blocked by 0144, retrying (60 sec) 0180:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0180, blocked by 0144, retrying (60 sec) 0188:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0188, blocked by 0144, retrying (60 sec) 0198:err:ntdll:RtlpWaitForCriticalSection section 7BC61360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0198, blocked by 0144, retrying (60 sec) 0208:fixme:console:default_ctrl_handler Terminating process 20 on event 0 [Also: What is an ergonomic way to downgrade to a previous winehq-devel and dependent wine package versions on Debian? Because synaptic in general and in this specific (force version) case handles amd64 packages with i386 dependencies very poorly. Basically what is the apt command line to fetch and install winehq-devel, wine-devel, wine-devel-amd64 and wine-devel-i386 all in the same older version number? like 6.9 for example.] -- 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 67

[Bug 51301] New: Right click inside Roblox Client window causes the cursor to freeze
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=51301 Bug ID: 51301 Summary: Right click inside Roblox Client window causes the cursor to freeze Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gnuwho.gnuwho(a)gmail.com Distribution: --- Platform: Arch Linux (GNOME) x86-64 In the Roblox Client (working as of Wine 6.11), if you join a game and press and hold right click (done in order to move the camera around), the cursor freezes in place and cannot get unstuck. As far as I know, this affects all users that try to run the Roblox Player using Wine 6.11 or later. Note: Roblox was installed using the Grapejuice wrapper (https://gitlab.com/brinkervii/grapejuice). -- 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 24

[Bug 48553] New: Catia (CAD software) refuse to run installation on newest wine (<=4.18)
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=48553 Bug ID: 48553 Summary: Catia (CAD software) refuse to run installation on newest wine (<=4.18) Product: Wine Version: 4.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tomo.hornacek(a)gmail.com Distribution: --- Created attachment 66366 --> https://bugs.winehq.org/attachment.cgi?id=66366 This is output of wine to console on my system. After running setup.exe of catia V5r19 or V5r20. Wine display "setup: Problem with VC8 Runtime. Please try to restart your computer or contact customer service" On wine 4.17 and lower installation's runs just fine. -- 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 54287] New: wineconsole: alterate screen buffer does not work
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54287 Bug ID: 54287 Summary: wineconsole: alterate screen buffer does not work Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: magiblot(a)hotmail.com Distribution: --- Created attachment 73855 --> https://bugs.winehq.org/attachment.cgi?id=73855 Source code of program to reproduce the issue Consider the attached program. On Windows, this program displays the characters '<==>' at the top left corner of the console. In Wine, if using the curses backend, the program is displayed as expected (except that the screen attributes are not reset when the program exits). However, if using the windowed wineconsole, this program displays just a black screen. If the source code is modified so that `HANDLE hOut = hInit;`, then the draw operations do change the screen. Thank you very much. -- 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 53583] New: the Reimplemented FindNLSStringEx has bug
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53583 Bug ID: 53583 Summary: the Reimplemented FindNLSStringEx has bug Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: 398063392(a)qq.com Distribution: --- Created attachment 72966 --> https://bugs.winehq.org/attachment.cgi?id=72966 the code project #include "stdafx.h" #include <windows.h> #include <assert.h> int _tmain(int argc, _TCHAR* argv[]) { DWORD flags = NORM_LINGUISTIC_CASING|FIND_STARTSWITH; int nResult = FindNLSStringEx(L"en-US",flags,L"x-oss-security-token",0xe,L"x-oss-",0x6,0,0,0,0); printf("FindNLSStringEx Result = %d \r\n", nResult); assert(nResult == 0); return 0; } the code in Windows print: "FindNLSStringEx Result = 0" but in Wine print: "FindNLSStringEx Result = -1 Assertion failed: nResult == 0, file .\FindNLSStringEx.cpp, line 13 " FindNLSStringEx is very important for C#, because it is the basis of the String class, StartsWith, EndsWith, IndexOf all rely on it to achieve. So hopefully you guys can test it rigorously, thanks a lot. In addition, I found a lot of bugs and fixed them myself, how can I submit these PRs? -- 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

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 January 2023