wine-bugs

wine-bugs@winehq.org

1 participants
158776 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 54210] New: Some AVX2 calls in ntdll are make impossible to compile Wine with Glibc 2.17
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54210 Bug ID: 54210 Summary: Some AVX2 calls in ntdll are make impossible to compile Wine with Glibc 2.17 Product: Wine Version: 8.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: Zenitur(a)yandex.ru Distribution: --- When I trying to compile an actian Wine 8.0-rc2 version I'd got these error: dlls/ntdll/unix/signal_x86_64.c: In function ‘signal_init_process’: dlls/ntdll/unix/signal_x86_64.c:2432:28: error: ‘AT_HWCAP2’ undeclared (first use in this function) if (getauxval( AT_HWCAP2 ) & 2) syscall_flags |= SYSCALL_HAVE_WRFSGSBASE; ^ dlls/ntdll/unix/signal_x86_64.c:2432:28: note: each undeclared identifier is reported only once for each function it appears in Serching for the commit that are broke the build, I'd found that the Wine 6.12 were the last version withount these error. The commit that broke my build is there (this is after Wine 6.12 and before the 6.13): https://github.com/wine-mirror/wine/commit/216d2411781f4bf12edf2083a7ac84d2… (committed on Jul 6, 2021) The reason of the error is my Glibc 2.17. According of the changelog of the Glibc 2.18 version (that's available there: https://lists.gnu.org/archive/html/info-gnu/2013-08/msg00003.html) the call AT_HWCAP2 was introduced in Glibc 2.18, hovewer I have 2.17. After that I'd tried to compile Wine 6.12 and I'd got another error caused by another AVX2 call that was introduced in Glibc 2.24 There is an error: tools/winegcc/winegcc -o dlls/ntdll/ntdll.so --wine-objdir . -m64 -fPIC -fasynchronous-unwind-tables -munix -shared \ dlls/ntdll/ntdll.spec -nodefaultlibs dlls/ntdll/unix/cdrom.o dlls/ntdll/unix/debug.o \ dlls/ntdll/unix/env.o dlls/ntdll/unix/esync.o dlls/ntdll/unix/file.o dlls/ntdll/unix/loader.o \ dlls/ntdll/unix/loadorder.o dlls/ntdll/unix/process.o dlls/ntdll/unix/registry.o \ dlls/ntdll/unix/security.o dlls/ntdll/unix/serial.o dlls/ntdll/unix/server.o \ dlls/ntdll/unix/signal_arm.o dlls/ntdll/unix/signal_arm64.o dlls/ntdll/unix/signal_i386.o \ dlls/ntdll/unix/signal_x86_64.o dlls/ntdll/unix/socket.o dlls/ntdll/unix/sync.o \ dlls/ntdll/unix/system.o dlls/ntdll/unix/tape.o dlls/ntdll/unix/thread.o dlls/ntdll/unix/virtual.o \ dlls/ntdll/unix/version.o dlls/winecrt0/libwinecrt0.a libs/port/libwine_port.a -lrt -lpthread -ldl \ -Wl,-z,relro ntdll-sNLwi5.AoHWp5.s: Assembler messages: ntdll-sNLwi5.AoHWp5.s:115: Error: no such instruction: `xsavec64 0xc0(%rcx)' winebuild: /usr/bin/gcc-4.9 failed with status 1 winegcc: ./tools/winebuild/winebuild failed make[1]: *** [dlls/ntdll/ntdll.so] Error 2 When I tried to google this error I'd found that the call xsavec were introduced in Intel Skylace CPU's. According the webpage (https://sourceware.org/legacy-ml/libc-stable/2017-10/msg00049.html) these calls were introduced in Glibc 2.24 hovewer I have Glibc 2.17. The commit that broke my build is there (this is after Wine 6.2 and before the 6.3): https://github.com/wine-mirror/wine/commit/30e5250622f40037a58dd87517267dba… (committed on Sep 2, 2020) The both problems present in the 32-bit and 64-bit OS'es. My build system: CPU: AMD Phenom II (amdfam10) OS: Debian 7 (32-bit and 64-bit versions on a two partitions) Kernel: Linux 4.11 Compiler: GCC 4.9, binutils 2.22, bison 3.2 Other: Glibc 2.17, xserver 1.16 -- 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 53837] New: wine-devel cannot install THS_hevo_gc8.6.1.2.exe after devel 7.8 version
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53837 Bug ID: 53837 Summary: wine-devel cannot install THS_hevo_gc8.6.1.2.exe after devel 7.8 version Product: Wine Version: 7.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dean-chen(a)qq.com Distribution: --- How to reproduce: 1. download the THS_hevo_gc8.6.1.2.exe from this stock web site from China(同花顺财经): http://activity.ths123.com/html/xb/160809/index.html, note: download this exe from windows, if you try to download it from linux, you probally will get linux setup package. 2. install wine devel 7.8, and chinese fonts using winetricks winetricks prefix=ths1 --force corefonts cjkfonts, then run the following command for installation: wine THS_hevo_gc8.6.1.2.exe, this will work successfully 3. upgrade wine to any version above 7.8, install THS_hevo_gc8.6.1.2.exe again, you will see error message. -- 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

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

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