wine-bugs

wine-bugs@winehq.org

1 participants
158777 discussions

[Bug 54180] New: Petz 4: Recent wine releases (after 6.0) corrupt .pet files upon startup of game
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54180 Bug ID: 54180 Summary: Petz 4: Recent wine releases (after 6.0) corrupt .pet files upon startup of game 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: coreyjosesilva(a)gmail.com Distribution: --- Dogz 4, Catz 4, Dogz 5, Catz 5 all share this issue. The .pet files are the way to save "pets" in the game. The files are corrupted in recent wine releases. This essentially makes the game unplayable. I confirmed petz 4 works on wine 6.0 -- 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 54045] New: ntdll:rtl - test_RtlIpv6StringToAddress() fails on Windows 11
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54045 Bug ID: 54045 Summary: ntdll:rtl - test_RtlIpv6StringToAddress() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:rtl - test_RtlIpv6StringToAddress() fails on Windows 11: rtl.c:2061: Test failed: [::0:0:0:0:0:0:0] terminator = 0052F925, expected 0052F923 rtl.c:2061: Test failed: [::0:a:b:c:d:e:f] terminator = 0052F935, expected 0052F933 rtl.c:2067: Test failed: [::0:a:b:c:d:e:f] ip = 0:0:a00:b00:c00:d00:e00:f00, expected 0:0:0:a00:b00:c00:d00:e00 rtl.c:2293: Test failed: [::0:0:0:0:0:0:0] res = 0x00000000, expected 0xc000000d rtl.c:2293: Test failed: [::0:a:b:c:d:e:f] res = 0x00000000, expected 0xc000000d See https://test.winehq.org/data/patterns.html#ntdll:rtl Note that the 32-bit version crashes too due to bug 53536. -- 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 3

[Bug 53671] New: No objects are being rendered in any DX10/11 apps with older GPU drivers
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53671 Bug ID: 53671 Summary: No objects are being rendered in any DX10/11 apps with older GPU drivers Product: Wine Version: 7.17 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com There is a regression after a patch 5ce7adaace3637ff6f8a33264b62c69bf2e53967 I have AMD graphics with outdated driver for Windows XP. Stating from the patch above it broke WineD3D10/11 compatibility. This BUG appeared with WineD3D 6.13 and above. -- 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 28

[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

[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

[Bug 52749] New: winetricks dotnet35sp1: printfilterpipelinesvc.exe crashes in background
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52749 Bug ID: 52749 Summary: winetricks dotnet35sp1: printfilterpipelinesvc.exe crashes in background Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: NEW Keywords: dotnet, download, regression Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 68feb134af0538d7fc589c2ddb6403de9cea1055 Distribution: --- Created attachment 72119 --> https://bugs.winehq.org/attachment.cgi?id=72119 backtrace Regression introduced by: 68feb134af0538d7fc589c2ddb6403de9cea1055 is the first bad commit commit 68feb134af0538d7fc589c2ddb6403de9cea1055 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Sep 13 13:50:08 2021 +0200 winspool: Use configuration file for DocumentPropertiesW. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> (note: may require a printer to be configured, didn't try disabling it/cups). After this commit, dotnet35sp1 (possibly more, this is the first place I noticed) have a crash in the background, in printfilterpipelinesvc.exe. It doesn't print to the console, even if the crash dialog is disabled. Viewing via dialog shows it, though: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00000000). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00000000 ESP:0021fb5c EBP:0021fbb8 EFLAGS:00010206( R- -- I - -P- ) EAX:00000000 EBX:01001ebc ECX:0021f8f0 EDX:00260f30 ESI:00000000 EDI:00000000 Stack dump: 0x0021fb5c: 663cc95f 00000000 01001ebc 00000000 0x0021fb6c: 00000000 00000000 00000004 0021fbb8 0x0021fb7c: 7bc27c0a 80000001 0021fba0 00000074 0x0021fb8c: 663df3fa 00250000 00000000 00000000 0x0021fb9c: 00260f30 00000000 014b61e0 0021fbd0 0x0021fbac: 0021fca8 00000074 0021fc0c 0021fc28 Backtrace: =>0 0x00000000 (0x0021fbb8) 1 0x663d5274 AddPrinterW+0x714(pName=<internal error>, Level=<internal error>, pPrinter=<internal error>) [Z:\home\austin\wine-git\dlls\winspool.drv\info.c:517] in winspool (0x0021fc28) 2 0x0101c6f9 in printfilterpipelinesvc (+0x1c6f9) (0x0021fd6c) 3 0x0101dd9f in printfilterpipelinesvc (+0x1dd9f) (0x0021fda0) 4 0x0101c4ad in printfilterpipelinesvc (+0x1c4ad) (0x0021fdc8) 5 0x0101c51d in printfilterpipelinesvc (+0x1c51d) (0x0021fde4) 6 0x0101c5df in printfilterpipelinesvc (+0x1c5df) (0x0021fe08) 7 0x0101e998 in printfilterpipelinesvc (+0x1e998) (0x0021ff30) 8 0x7b62d2a0 WriteTapemark+0x100(device=7FFD1000, type=<is not available>, count=<is not available>, immediate=<is not available>) [Z:\home\austin\wine-git\dlls\kernel32\tape.c:317] in ker nel32 (0x0021ff48) 9 0x7bc58147 RtlWakeConditionVariable+0x57(variable=7B62D290) [Z:\home\austin\wine-git\dlls\ntdll\sync.c:757] in ntdll (0x0021ff5c) 10 0x7bc58800 RtlCreateUserThread(entry=0101E813, arg=7FFD1000) [Z:\home\austin\wine-git\dlls\ntdll\thread.c:261] in ntdll (0x0021ffec) 0x00000000: -- no code accessible -- The issue persists in wine-7.5. -- 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 3

[Bug 52557] New: GetNetworkParams loops forever on musl
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52557 Bug ID: 52557 Summary: GetNetworkParams loops forever on musl Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: me(a)atiltedtree.dev Distribution: --- On musl, res_getservers does not exist and dnsapi/resolv_get_serverlist will fall back to res_state.nsaddr_list. But musl also does not set res_state.nsaddr_list causing dnsapi/resolv_get_serverlist to always return DNS_ERROR_NO_DNS_SERVERS. iphlpapi/get_dns_server_list will call DnsQueryConfig( DnsConfigDnsServerList, ...), which calls dnsapi/resolv_get_serverlist, until it does not return an error, but on musl it will always return an error causing iphlpapi/get_dns_server_list to loop infinitely. This means that any application that calls iphlpapi.GetNetworkParams or iphlpapi.GetPerAdapterInfo will loop infinitely, if wine was built on musl. -- 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 27244] New: Wiggles: Indeo
by wine-bugs＠winehq.org 13 Jan '23

13 Jan '23

http://bugs.winehq.org/show_bug.cgi?id=27244 Summary: Wiggles: Indeo Product: Wine Version: 1.3.19 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=34827) --> (http://bugs.winehq.org/attachment.cgi?id=34827) Terminal output on Wine 1.3.19 Steps to reproduce: 1) remove ~/.wine 2) winetricks gecko icodecs 3) install Wiggles 4) patch Wiggles with Wiggles_Patch_1_0_844.exe 4) wine Wiggles.exe Behaviour: I get only audio from intro video. Expected behaviour: I should get audio and video from intro video. Additional info: I can play video in Smplayer. Here I give info about video: Resolution: 640 x 360 Format: IV32 Bitrate: 4373 kbps FPS: 24.000 Decoder: ffindeo3 Size: 96,2 MB -- 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 54301] New: Global hotkey support
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54301 Bug ID: 54301 Summary: Global hotkey support 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: linux(a)bernd-steinhauser.de Distribution: --- My original use case is the head tracker linuxtrack that can be used to control camera movements in e.g. racing simulators or flight simulators. linuxtrack provides a wine bridge to be able to use it with games run via wine. https://github.com/uglyDwarf/linuxtrack The wine bridge provides a controller application that is makes use of two hotkeys to pause and to recenter the tracker. These are not essential to use it (i.e. it works without), but they make the usage much more convenient. The problem is that the hotkeys only work when the controller application has the focus, which obviously is usually not the case, since you're using it just as a background application while running a game. So if I e.g. want to recenter the tracker, I have to Alt+Tab out of the application to do that. Unfortunately, some applications don't really like that and it could result in all kinds of problems, including crashes. Since that use case is very specific and might not be easily accessible to everybody (you need hardware for it), I looked at another use case and that is foobar2000. foobar2000 is a popular media player for Windows and as a media player, it makes of course usage of hotkeys, both within the application and global ones. So I installed it into a wine prefix using the latest version, assigned a hotkey to a functionality (e.g. play/pause), made that global and tried if it works and it does not. Or, to be more specific, it works as long as the window has focus (and thus gets keyboard input). As soon as the window is in the background, it doesn't work anymore. (I'm using KDE Plasma on X11 with kwin as the compositor, in case that matters.) Now, I spent quite some time trying to research the subject and was actually surprised by how little information I could find. Especially, I wasn't able to find anything in the wine documentation whether global hotkeys (or keyboard shortcuts) are supposed to work or not. Thus, I am actually still not sure whether this is a feature request or a bug. (I suspect it's the former, but I don't know.) I did find one tutorial that did suggest using xdotool, but this should possibly called xdodotool, since it's more or less dead. In any case, it surely wouldn't be future-proof, since everything is slowly heading towards wayland (and xdotool won't work there). Since there are many tools out there that are used alongside games, be it scripting tools, controller tools or various mods/addons, I think that some kind of support for global hotkeys would be really good. -- 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 54300] New: LdrLoadDll illegal memory access on DllPath
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54300 Bug ID: 54300 Summary: LdrLoadDll illegal memory access on DllPath Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: novae.harpist06(a)icloud.com Distribution: --- Created attachment 73867 --> https://bugs.winehq.org/attachment.cgi?id=73867 Reproducer See reproducer (attached) DllPath can be search flags, which is indicated by passing a pointer where the lowest bit is set. This is not handled in wine, which calls wcslen on it: https://github.com/wine-mirror/wine/blob/a8c1d5c108fc57e4d78e9db126f395c890… The path resolution is correctly implemented in LdrGetDllPath, but that function is not used (besides being an export). Windows output: Trying flag 00000200 Trying flag 00000400 Trying flag 00000800 Trying flag 00001000 Trying flag 00002000 Trying flag 00004000 Wine output: Trying flag 00000200 wine: Unhandled page fault on read access to 0000000000000201 at address 0000000170069B40 (thread 05ec), 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.

1 1

[Bug 54306] New: mf:mf - test_sar() sometimes gets an unexpected refcount in Wine
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54306 Bug ID: 54306 Summary: mf:mf - test_sar() sometimes gets an unexpected refcount in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mf:mf - test_sar() sometimes gets an unexpected refcount in Wine: mf.c:5441: Test succeeded inside todo block: Release returned 0 See https://test.winehq.org/data/patterns.html#mf:mf Note that although the WineTest results seem to implicate that this only happens on my desktop, this failure has happened on the GitLab CI too (see MR1965). Maybe it's a timing issue that's impacted by the CPU load. Should the test be removed entirely or just marked as flaky_wine? -- 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 54303] New: mfplat:mfplat - test_MFCreateDXSurfaceBuffer() gets stuck locking the media buffer on Windows 11 + Nvidia
by WineHQ Bugzilla 13 Jan '23

13 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54303 Bug ID: 54303 Summary: mfplat:mfplat - test_MFCreateDXSurfaceBuffer() gets stuck locking the media buffer on Windows 11 + Nvidia Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mfplat:mfplat - test_MFCreateDXSurfaceBuffer() gets stuck locking the media buffer on Windows 11 + Nvidia: ... mfplat.c:6537:96.969 Test succeeded mfplat:mfplat:1fbc done (258) in 120s See https://test.winehq.org/data/patterns.html#mfplat:mfplat mfplat:mfplat gets stuck even if all the other test functions are skipped. A WINETEST_TIME trace shows that in even that case it gets stuck on the line below after less than 1 second: hr = IMFMediaBuffer_Lock(buffer, &data, NULL, &length); -- 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

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