wine-bugs March 2024

wine-bugs@winehq.org

1 participants
1750 discussions

[Bug 56450] New: Non-input USB HID devices stopped working in 9.1
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=56450 Bug ID: 56450 Summary: Non-input USB HID devices stopped working in 9.1 Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: bugzilla-wine(a)opinsys.fi Regression SHA1: 814d2c176d23c581353ba5679977415d2218d0c5 Distribution: Debian Non-input USB HID devices stopped working in 9.1. Wine 9.0 + LoggerPro 3.16.2 + USB HID thermometer (08f7:0002 Vernier EasyTemp/Go!Temp): LoggerPro detects the device and starts collecting temperature measurements automatically. Wine 9.1 + LoggerPro 3.16.2 + USB HID thermometer (08f7:0002 Vernier EasyTemp/Go!Temp): LoggerPro does not detect the device. Host system detects the device and assigns hid-generic driver to it and a hidraw device is created. The device is not an input device and hence input subsystem is not used for this device (event devices are not created). My understanding is that commit 814d2c176d23c581353ba5679977415d2218d0c5 causes the regression, because it changes the policy to not use hidraw by default and requires devices to be explicitly listed in EnableHidraw bus option to be used by hidraw backend. Further changes to winebus.sys have been made to allow hidraw to be used in certain scenarios (some gamepads and when evdev and SDL is disabled), but these do not cover the case when non-input HID device is used in default environment. This bug still exists in 9.4. I am working on a patch set which fixes the bug. I'll create a merge request. -- 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 56406] New: wineserver crashes in set_input_desktop()
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=56406 Bug ID: 56406 Summary: wineserver crashes in set_input_desktop() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The wineserver crashes when running the Wine test suite on my Debian 12 PC. The crash happens during the dxgi:dxgi test. Here is some information collected by attaching gdb to wineserver while running the tests: Program received signal SIGSEGV, Segmentation fault. 0x56683005 in set_input_desktop (winstation=0x576aea90, new_desktop=0x576af890) at /home/fgouget/wine/wt23/src/server/winstation.c:246 246 set_rawinput_process( thread->process, 0 ); (gdb) p thread $1 = (struct thread *) 0x52fff4 (gdb) p thread->process Cannot access memory at address 0x530034 (gdb) bt #0 0x56683005 in set_input_desktop (winstation=0x576aea90, new_desktop=0x576af890) at /home/fgouget/wine/wt23/src/server/winstation.c:246 #1 0x5664afac in req_send_hardware_message (req=0x577995c0, reply=0xff829300) at /home/fgouget/wine/wt23/src/server/queue.c:2808 #2 0x566561c9 in call_req_handler (thread=thread@entry=0x577994d0) at /home/fgouget/wine/wt23/src/server/request.c:305 #3 0x5665720c in read_request (thread=0x577994d0) at /home/fgouget/wine/wt23/src/server/request.c:339 #4 0x566627a1 in thread_poll_event (fd=0x5778c070, event=1) at /home/fgouget/wine/wt23/src/server/thread.c:388 #5 0x5662faf6 in fd_poll_event (event=<optimized out>, fd=<optimized out>) at /home/fgouget/wine/wt23/src/server/fd.c:505 #6 main_loop_epoll () at /home/fgouget/wine/wt23/src/server/fd.c:599 #7 0x5662fd9f in main_loop () at /home/fgouget/wine/wt23/src/server/fd.c:955 #8 0x5661fa80 in main (argc=1, argv=0xff829b04) at /home/fgouget/wine/wt23/src/server/main.c:238 (gdb) info registers eax 0x5fae9a2c 1605278252 ecx 0x576aea90 1466624656 edx 0x53002c 5439532 ebx 0x566c0ff4 1449922548 esp 0xff8291e4 0xff8291e4 ebp 0x52fff4 0x52fff4 esi 0x576eedb0 1466887600 edi 0x576af890 1466628240 eip 0x56683005 0x56683005 <set_input_desktop+101> eflags 0x10296 [ PF AF SF IF RF ] cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x63 99 (gdb) p *winstation->input_desktop $23 = {obj = {refcount = 1466843598, handle_count = 2691322373, ops = 0x73006f, wait_queue = {next = 0x66006f, prev = 0x200074}, name = 0x68004a, sd = 0x6e0065, is_permanent = 1, obj_list = {next = 0x690065, prev = 0x550020}}, flags = 5439561, winstation = 0x470045, input_time = 20548038376620111, entry = { next = 0x54002e, prev = 0x460054}, threads = {next = 0x53002c, prev = 0x670065}, top_window = 0x65006f, msg_window = 0x550020, global_hooks = 0x49, hotkeys = {next = 0x49004d, prev = 0x47004e}, close_timeout = 0x49004c, foreground_input = 0x2e0055, users = 5505108, cursor = {x = 2883651, y = 6881357, clip = {left = 6750318, top = 6881356, right = 85, bottom = 5439565}, last_change = 4718681, win = 5505070}, keystate = "T\000C\000,\000M\000i\000c\000r\000o\000s\000o\000f\000t\000 \000Y\000a\000H\000e\000i\000 \000U\000I\000\000\000M\000E\000I\000R\000Y\000O\000.\000T\000T\000C\000,\000M\000e\000i\000r\000y\000o\000 \000U\000I\000\000\000M\000A\000L\000G\000U\000N\000.\000T\000T\000F\000,\000M\000a\000l\000g\000u\000n\000 \000G\000o\000t\000h\000i\000c\000\000\000Y\000U\000G\000O\000T\000H\000M\000.\000T\000T\000C\000,\000Y\000u\000 \000G\000o\000t\000h\000i\000c\000 \000U\000I\000\000\000S\000E\000G\000U\000I\000S\000Y\000"...} So it looks like it is the first input_desktop->threads entry which is wrong. The crashes started on 2024-02-28 and they happen most clearly when running the tests in a pure 32-bit environment[1]. Furthermore a bisect shows that the crashes started with the commit below: commit c43b1ecbc3e8509b1f4778d799f9759eb64dda40 (HEAD) Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Sun Feb 25 09:53:09 2024 +0100 server: Keep a list of processes that can receive rawinput messages. [1] When run in a 64-bit environment the tests succeed, and the 64-bit tests get stuck but there is no 'wineserver crashed' message in the logs. -- 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 56435] New: capture mouse dont work in virtual desktop (work on wine 9.3)
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=56435 Bug ID: 56435 Summary: capture mouse dont work in virtual desktop (work on wine 9.3) Product: Wine Version: 9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- using wine 9.3 mouse capture in virtual desktop work but in wine 9.4 dont work and compiling git, mouse capture work until this commit https://gitlab.winehq.org/wine/wine/-/commit/ad921b3c561c428ce36a2a3e0f44de… in my case after this dont work at simple seek i think about lastest patchs of Rémi Bernon about input can be related with this issue maybe this bug could be stay affected for lastest input patchs: https://bugs.winehq.org/show_bug.cgi?id=56429 -- 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 56411] New: Failure to build wine 9.4 due to EGL 64-bit development files not found
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=56411 Bug ID: 56411 Summary: Failure to build wine 9.4 due to EGL 64-bit development files not found Product: Wine Version: 9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timo.gurr(a)gmail.com Distribution: --- Trying to update our distribution package to the latest release configure fails for me on Exherbo Linux with: [...] checking for -lGL... libGL.so.1 checking for wayland-client.h... yes checking for wl_display_connect in -lwayland-client... yes checking for wayland-scanner... /usr/bin/wayland-scanner checking for xkbcommon/xkbcommon.h... yes checking for xkb_context_new in -lxkbcommon... yes checking for xkbcommon/xkbregistry.h... yes checking for rxkb_context_new in -lxkbregistry... yes checking for EGL/egl.h... (cached) yes checking for -lEGL... libEGL.so.1 checking for wayland-egl.h... yes checking for wl_egl_window_create in -lwayland-egl... yes configure: error: EGL 64-bit development files not found, the Wayland driver won't support OpenGL This is an error since --with-opengl was requested. despite the checks reporting "yes" and having (lib)wayland-egl installed --- [ignor] /usr/x86_64-pc-linux-gnu/lib/libwayland-egl.so.1.22.0 --- [ignor] /usr/x86_64-pc-linux-gnu/lib/libwayland-egl.so.1 --- [ignor] /usr/x86_64-pc-linux-gnu/lib/libwayland-egl.so cat /usr/x86_64-pc-linux-gnu/lib/pkgconfig/wayland-egl.pc prefix=/usr includedir=${prefix}/x86_64-pc-linux-gnu/include libdir=${prefix}/x86_64-pc-linux-gnu/lib Name: wayland-egl Description: Frontend wayland-egl library Version: 18.1.0 Requires: wayland-client Libs: -L${libdir} -lwayland-egl Cflags: -I${includedir} Gentoo suffers the same issue and they just apply a patch removing the additional WINE_NOTICE_WITH(opengl, [test -z "$ac_cv_lib_soname_EGL" -o -z "$HAVE_LIBWAYLAND_EGL"], check: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ddfba238cc0b1ab4056f6d… -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 56380] New: Rocket League crashes with Wine 9.3 after BakkesMod (trainer app) injects into the game
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=56380 Bug ID: 56380 Summary: Rocket League crashes with Wine 9.3 after BakkesMod (trainer app) injects into the game Product: Wine Version: 9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: oguilherme(a)protonmail.com Distribution: --- Created attachment 76126 --> https://bugs.winehq.org/attachment.cgi?id=76126 Wine 9.3 output (where Rocket League crashes if BakkesMod is running) As of Wine 9.3, I can not use BakkesMod[1] (a Rocket League[2] trainer ), to inject into the game anymore. git bisect indicates commit bb872831deb48382e4733979e00243e5122385d0 is the culprit. Without BakkesMod running, the game runs just fine. --- Steps to reproduce: 1. Launch BakkesMod 2. Launch Rocket League 3. Wait 4. Rocket League crashes --- System information: Wine v9.3 NVIDIA driver 470.239.06 (GPU: NVIDIA GTX 660) DXVK 1.10.3 BakkesMod v190 (Injector version 31) Rocket League (from Epic, version BC2_Update48+441123) --- Ref: [1] https://github.com/bakkesmodorg/BakkesModInjectorCpp [2] https://store.epicgames.com/en-US/p/rocket-league -- 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 16

[Bug 56379] New: d2d1 regression unable to build after: https://gitlab.winehq.org/wine/wine/-/commit/167103114389c7f487f7d6aa398f56abf9cc5572
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=56379 Bug ID: 56379 Summary: d2d1 regression unable to build after: https://gitlab.winehq.org/wine/wine/-/commit/167103114 389c7f487f7d6aa398f56abf9cc5572 Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dofficialgman(a)gmail.com Distribution: --- Regression after https://gitlab.winehq.org/wine/wine/-/commit/167103114389c7f487f7d6aa398f56… unable to build with the following errors: i686-w64-mingw32-gcc -c -o dlls/d2d1/i386-windows/effect.o ../wine-9.3/dlls/d2d1/effect.c -Idlls/d2d1 -I../wine-9.3/dlls/d2d1 -Iinclude \ -I../wine-9.3/include -I../wine-9.3/include/msvcrt -D_UCRT -D__WINESRC__ -D__WINE_PE_BUILD -Wall \ -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Winit-self \ -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla \ -Wwrite-strings -Wpointer-arith -Wlogical-op -fno-omit-frame-pointer -mpreferred-stack-boundary=2 \ -gdwarf-4 -g -O2 ../wine-9.3/dlls/d2d1/effect.c: In function 'd2d_effects_init_builtins': ../wine-9.3/dlls/d2d1/effect.c:296:41: error: initializer element is not constant { &CLSID_D2D12DAffineTransform, _2d_affine_transform_description }, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../wine-9.3/dlls/d2d1/effect.c:296:41: note: (near initialization for 'builtin_effects[0].description') ../wine-9.3/dlls/d2d1/effect.c:297:46: error: initializer element is not constant { &CLSID_D2D13DPerspectiveTransform, _3d_perspective_transform_description}, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../wine-9.3/dlls/d2d1/effect.c:297:46: note: (near initialization for 'builtin_effects[1].description') ../wine-9.3/dlls/d2d1/effect.c:298:33: error: initializer element is not constant { &CLSID_D2D1Composite, composite_description }, ^~~~~~~~~~~~~~~~~~~~~ ../wine-9.3/dlls/d2d1/effect.c:298:33: note: (near initialization for 'builtin_effects[2].description') ../wine-9.3/dlls/d2d1/effect.c:299:28: error: initializer element is not constant { &CLSID_D2D1Crop, crop_description }, ^~~~~~~~~~~~~~~~ ../wine-9.3/dlls/d2d1/effect.c:299:28: note: (near initialization for 'builtin_effects[3].description') ../wine-9.3/dlls/d2d1/effect.c:300:30: error: initializer element is not constant { &CLSID_D2D1Shadow, shadow_description }, ^~~~~~~~~~~~~~~~~~ ../wine-9.3/dlls/d2d1/effect.c:300:30: note: (near initialization for 'builtin_effects[4].description') ../wine-9.3/dlls/d2d1/effect.c:301:33: error: initializer element is not constant { &CLSID_D2D1Grayscale, grayscale_description }, ^~~~~~~~~~~~~~~~~~~~~ ../wine-9.3/dlls/d2d1/effect.c:301:33: note: (near initialization for 'builtin_effects[5].description') Makefile:27950: recipe for target 'dlls/d2d1/i386-windows/effect.o' failed make: *** [dlls/d2d1/i386-windows/effect.o] Error 1 -- 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 29523] New: CDBurnerXP hangs on right-clicking empty space in the file browser
by wine-bugs＠winehq.org 22 Mar '24

22 Mar '24

http://bugs.winehq.org/show_bug.cgi?id=29523 Bug #: 29523 Summary: CDBurnerXP hangs on right-clicking empty space in the file browser Product: Wine Version: 1.3.36 Platform: x86-64 URL: http://cdburnerxp.se/download?more-options OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Classification: Unclassified Created attachment 38233 --> http://bugs.winehq.org/attachment.cgi?id=38233 Terminal output Right-clicking in an empty section of the file browser causes CDBurnerXP to become unresponsive. On Windows, this brings up a context menu. Steps to reproduce: 1. winetricks dotnet20 2. Install and run CDBurnerXP 3. Choose "data disc" from the main menu 4. Right-click in some empty space within the file browser (top-right section) The problem is also present in 1.2. -- 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 13

[Bug 44514] New: Elder Scrolls Online (Dragon Bones update) requires more than 32 samplers in pixel shaders with D3D11 renderer
by wine-bugs＠winehq.org 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=44514 Bug ID: 44514 Summary: Elder Scrolls Online (Dragon Bones update) requires more than 32 samplers in pixel shaders with D3D11 renderer Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: ssorgatem(a)gmail.com Distribution: --- Practically the same as https://bugs.winehq.org/show_bug.cgi?id=41213 Missing ground textures that make the game rather hard to play, same as in the screenshots for that patch. The difference is that back then the game required more than 16 samplers... which was fixed, but it now requries more than 32 samplers: fixme:d3d:context_bind_shader_resources Shader 0x7fff03eb85a0 needs 37 samplers, but only 32 are supported. Happens in latest staging, 3.0 and 3.1 -- 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 66

[Bug 56085] New: Guitar Pro 8.1.1 Build 17 crashes once hitting Design Button
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=56085 Bug ID: 56085 Summary: Guitar Pro 8.1.1 Build 17 crashes once hitting Design Button Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vmustin(a)gmail.com Distribution: --- Created attachment 75748 --> https://bugs.winehq.org/attachment.cgi?id=75748 System Information Error is reproducible since several Versions (7.0, 7.5, 8.0, 8.1.1) Using Linux Mint 21.2 (see system information) -- 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 52401] New: Improper synchronization in sock_recv/sock_send leads to arbitrary reordering of completion of I/O requests
by WineHQ Bugzilla 21 Mar '24

21 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=52401 Bug ID: 52401 Summary: Improper synchronization in sock_recv/sock_send leads to arbitrary reordering of completion of I/O requests Product: Wine Version: 7.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Distribution: --- The sock_recv function (dlls/ntdll/unix/socket.c) issues a 'recv_socket' call to the server to complete the I/O request. Prior to calling the server, the function attempts to serve the I/O request locally first by calling try_recv(). The consequence is that there are two types of asynchronous I/O request (hereinafter "Async") sent to the server: 1. Eager: try_recv() call has succeeded before 'recv_socket'. There is no more I/O to be done. 2. Deferred: the request is still pending. When the server senses an incoming packet, async_recv_proc() (in client side) will be called to complete the I/O. The problem is that eager Asyncs are _not_ prioritized before deferred Asyncs. Therefore, deferred Asyncs may be completed before eagar Asyncs. The following scenario illustrates the problem: 1. The socket's incoming buffer is initially empty. 2. Client: The application calls WSARecv(). In sock_recv(), try_recv() fails with STATUS_DEVICE_NOT_READY; therefore, a deferred Async is queued to the server. WSARecv() returns with error ERROR_IO_PENDING. 3. The socket receives packet [A] in the meantime. The socket's incoming buffer is no longer empty. 4. Client: The application calls WSARecv() again. In sock_recv(), try_recv() succeeds with packet [A]; therefore, an eager Async is queued to the server. 5. The socket receives packet [B] in the meantime. 6. Server: the poll() loop detects this, and calls async_wake_up( &sock->read_q, status ). This causes APC_ASYNC_IO for deferred Async to be called to the client process. 6. Client: While still in the second sock_recv(), the client does wait_async() on the returned wait handle. This causes the APC_ASYNC_IO (a system APC) to be dequeued. 7. Client (select loop): The client does a server select call. This returns STATUS_KERNEL_APC with APC_ASYNC_IO. The client calls try_recv() (from async_recv_proc), which succeeds with packet [B]. The client process completes the deferred Async with this packet. 8. Client (select loop): The client re-issues the select call after the APC. 8. Server: the wait on the async wait handle is satisfied, causing async_satisified() to be called. This in turn calls async_set_result(), which completes the eager Async (with packet [A]). 9. Client: The client exits sock_recv() and in turn WSARecv(), which reports immediate success. (Ditto for sock_send and other similar asynchronous I/O requests.) If the application uses a completion port, it will observe the deferred Async first, and the eager Async second. The deferred Async carries packet [B], while the eager Async carriers packet [A]. This results in the application receiving the packets in the wrong order. -- Three possible solutions comes to mind: 1. Replace the call to try_recv()/try_send() in sock_recv()/sock_send() with STATUS_DEVICE_NOT_READY. This may slightly reduce performance, since it always defers all I/O requests and forces them to go through the poll() loop. 2. Make async_handoff() immediately call async_set_result() if the status and data are already set (i.e. the I/O has completed synchronously). Since this affects other asynchronous operations as well, I'm not sure this approach is semantically correct. 3. Prioritize immediately satiable async wait handles _before_ system APCs when waiting for objects. This approach too changes semantics, and appears much uglier than other solutions. -- 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 14

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 March 2024