wine-bugs September 2022

wine-bugs@winehq.org

1 participants
3294 discussions

[Bug 52994] New: mstask:task_trigger - test_GetNextRunTime() fails in Wine on date change
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52994 Bug ID: 52994 Summary: mstask:task_trigger - test_GetNextRunTime() fails in Wine on date change Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mstask Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 72360 --> https://bugs.winehq.org/attachment.cgi?id=72360 Make the failure 100% reproducible mstask:task_trigger - test_GetNextRunTime() fails in Wine on date change: task_trigger.c:434: old: 5/5/2022 wday 0 23:58:00.000 task_trigger.c:443: new: 6/5/2022 wday 5 0:03:00.000 task_trigger.c:533: Test failed: got 0x41307 task_trigger.c:534: Test failed: got 0/0/0 wday 0 0:00:00 https://test.winehq.org/data/patterns.html#mstask:task_trigger What seems to be happening is that ITask_GetNextRunTime() returns SCHED_S_TASK_NO_VALID_TRIGGERS for TASK_TIME_TRIGGER_ONCE tasks where the trigger is on the next day. So I suspect the bug is in the ITask_GetNextRunTime() implementation rather than in the test itself. Note: Initially I was a bit alarmed by the week day change in the traces. But in fact trigger_add_ms() just sets it to 0 so that's what we get on the "old:" line. Then FileTimeToSystemTime() fully initializes it so we get the correct value on the "new:" line. That's why it changes in surprising ways. Luckily the test and Itask_GetNextRunTime() implementation were both added in the commit below and I was also able to confirm that the failure was already present: commit ac322334fa4d6740e89c6f19361a66f063103a46 Author: Dmitry Timoshkov <dmitry(a)baikal.ru> AuthorDate: Mon May 21 18:17:47 2018 +0800 mstask: Implement ITask::GetNextRunTime() for ONCE trigger type. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> 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 4

[Bug 52932] New: user32:edit - test_char_from_pos() fails on Windows with the UTF-8 codepage
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52932 Bug ID: 52932 Summary: user32:edit - test_char_from_pos() fails on Windows with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:edit's test_char_from_pos() fails on Windows with the UTF-8 codepage. Adding some traces it's clear that the problem is with the lower bounds: edit.c:1161: Test failed: 4/4/8: expected 1 got 0 edit.c:1179: Test failed: 282/282/286: expected 1 got 0 edit.c:1197: Test failed: 143/143/147: expected 1 got 0 https://test.winehq.org/data/patterns.html#user32:edit -- 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 52429] New: Guild Wars: login not possible (regression)
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52429 Bug ID: 52429 Summary: Guild Wars: login not possible (regression) Product: Wine Version: 7.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gero45(a)mr-gero.de Distribution: ArchLinux Created attachment 71689 --> https://bugs.winehq.org/attachment.cgi?id=71689 log When trying to login into Guild Wars, it fails with an error code 011, that indicates that a wrong password was typed in or a connection to the corresponding server was not possible. I double-checked the password and even copy-pasted it, it did not work. Then I used an older version of Wine (6.5) (since this was reported as the last working version on AppDB) and it works. Thus I think this must be a regression. I will try out wine 7.0, when it is released on Arch Linux (sadly it is not yet). -- 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 21

[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 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 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 September 2022