wine-bugs July 2025

wine-bugs@winehq.org

1 participants
892 discussions

[Bug 44840] New: Icewind Dale unusably glitchy starting with Wine Version 3.2
by wine-bugs＠winehq.org 03 Dec '25

03 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=44840 Bug ID: 44840 Summary: Icewind Dale unusably glitchy starting with Wine Version 3.2 Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wodencafe(a)gmail.com Distribution: --- Starting with Wine 3.2 and on, Icewind Dale (2.0.0.11 (GOG)) is having very strange input / glitchy rendering issues. I have attached a video comparison with 3.1 where it works fine. Tested with 3.2, 3.3, and 3.4, and all have the strange input and glitchy problem. There are no additional wine modifications. Please see the video for example of problem, and comparison of when it was working with 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 21

[Bug 56790] New: wine binds my application to "lo" adapter
by WineHQ Bugzilla 02 Dec '25

02 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=56790 Bug ID: 56790 Summary: wine binds my application to "lo" adapter Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: contact(a)msteinbusch.nl Distribution: ArchLinux Created attachment 76596 --> https://bugs.winehq.org/attachment.cgi?id=76596 A full wine trace Issue: Farming Simulator 2022 dedicated webserver binds application to "lo" adapter Wine doesn't run my program the same way as Windows does, for some reason it binds to the "lo" adapter. I suspect the application is selecting the first interface. Sadly there is no way to override this. I included a full trace, keywords to look trough are winsock, 127.0.0.1, winsock:bind socket etc. Any help is welcome and if more info is needed let me know. Wine: 9.10-1 and < Archlinux, Kernel 6.9.3. X68_64 A VNC instance where the issue can be reproduced is available on request. A license key for Farming Simulator 2022 can be provided by me on request. The download of the game/server can be found at: https://eshop.giants-software.com/downloads.php This docker container is using nginx to get around the issue: https://github.com/wine-gameservers/arch-wine-fs22 Screenshot and logs included in zip. -- 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 30

[Bug 52284] New: Factory I/O SPS-Software hangs
by WineHQ Bugzilla 01 Dec '25

01 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=52284 Bug ID: 52284 Summary: Factory I/O SPS-Software hangs Product: Wine Version: 7.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Hello everyone, I got a request from the ubuntuusers.de forum that one user had problems running this program and submitted an AppDB entry at https://appdb.winehq.org/objectManager.php?sClass=version&iId=40486 providing tests for 7.0rc1 and 7.0rc2 (queued) where as the console is spammed with 018c:fixme:d3d:wined3d_device_context_resolve_sub_resource Multisample resolve is not fully supported for typeless formats (dst_format WINED3DFMT_R8G8B8A8_TYPELESS, src_format WINED3DFMT_R8G8B8A8_TYPELESS, format WINED3DFMT_R8G8B8A8_UNORM). Steps to reproduce after installation: New → File → Drivers → Control I/O (opens up a grey window but nothing happens) -- 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 57588] New: Guardant USB key drivers: grdkey.sys crashes
by WineHQ Bugzilla 01 Dec '25

01 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57588 Bug ID: 57588 Summary: Guardant USB key drivers: grdkey.sys crashes Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: amorozov(a)etersoft.ru Distribution: --- Created attachment 77697 --> https://bugs.winehq.org/attachment.cgi?id=77697 Log with WINEDEBUG=+ntoskrnl,+plugplay and winedbg output I installed Guardant USB key drivers 7.0.224 from here: https://www.guardant.com/support/users/download/2238/ with WoW64 Wine build. $ md5sum GrdDrivers.exe 731d388d2ee4c1a4f45d655e4b8c9163 GrdDrivers.exe After installation windows/system32/drivers/grdkey.sys appears. And it crashes at Wine start: wine: Unhandled page fault on read access to 0000000000000008 at address 00006FFFFC8A295B (thread 00f0), starting debugger... In AddDevice handler grdkey.sys calls IoOpenDeviceRegistryKey. This results in calling get_device_instance_id -> get_device_id and sending IRP_MJ_PNP/IRP_MN_QUERY_ID with BusQueryDeviceID to the driver which calls IofCallDriver(NULL, ....) and crashes. The crash can be avoided with commenting out this line: device = IoGetAttachedDevice( device ); in get_device_id function in dlls/ntoskrnl.exe/pnp.c But I assume that the correct fix should be in avoiding to send IRPs from IoOpenDeviceRegistryKey. MSDN says that IRP_MN_QUERY_ID is sent before loading driver and calling AddDevice: https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/adding-a-… -- 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 58145] New: Out of Ctrl 1.2: game doesn't launch, gives error
by WineHQ Bugzilla 01 Dec '25

01 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58145 Bug ID: 58145 Summary: Out of Ctrl 1.2: game doesn't launch, gives error Product: Wine Version: 10.6 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78425 --> http://bugs.winehq.org/attachment.cgi?id=78425 Wine-devel 10.6 terminal log The game Out of Ctrl 1.2 doesn't launch and gives the following error in a pop-up window on launch: Error Failed to initialize player Details: Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed tested using Gcenx's wine-devel 10.6 build (https://github.com/Gcenx/macOS_Wine_builds/releases/tag/10.6) with GStreamer 1.26.0 download link (20 MB) (choose "OutOfCtrl_v1_2_EXE.zip"): https://miknugget.itch.io/out-of-ctrl shas256: 5d26c746c4e85b98af2f1f9fb4a4daeed837deb49427bf108935545f8958dba9 I'm using macOS 11 -- 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 56681] New: 3d games continue receiving mouse input while not focused
by WineHQ Bugzilla 01 Dec '25

01 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=56681 Bug ID: 56681 Summary: 3d games continue receiving mouse input while not focused Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: pmargeti34(a)gmail.com Distribution: --- Wine wayland windows seem to get the mouse input even if the application window is not focused. 3D game world continues to respond to mouse input as if the game still had focus. To reproduce: -launch a 3d game in wayland mode (warframe in my example) -open another application and make sure it has focus -observe that when the mouse cursor is over the game window, game still receives input -- 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 30853] New:=?UTF-8?Q?=20Wine=20doesn=E2=80=99t=20always=20handle=20?="right alt" properly
by wine-bugs＠winehq.org 01 Dec '25

01 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=30853 Bug #: 30853 Summary: Wine doesn’t always handle "right alt" properly Product: Wine Version: 1.5.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 40410 --> http://bugs.winehq.org/attachment.cgi?id=40410 workaround/quick and dirty fix I’m trying to get World of Warcraft working under Wine. However, I have huge trouble with key bindings (I use unusual key bindings : I use the right half of my keyboard, whereas most players use the left half). After investigation, I found 3 bugs (different behaviors between Wine and my Windows installation). The first one is the management of the right "Alt" key (labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with Spy++, I get the followings events : <03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:0 fRepeat:0 fUp:0 <03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:0 fUp:0 <03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:0 fRepeat:1 fUp:1 Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb lp 760001 [note: wp = VK_OEM_PA2] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp c0260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp c0760001 [note: wp = VK_OEM_PA2] With xev, I get : KeyPress event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425), state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425), state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I get this under Wine : trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp a5 lp 21380001 [wp = VK_RMENU] trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp 4c lp 20260001 [wp = 'L'] trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c lp 20260001 [wp = 'l'] trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c lp e0260001 [wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp c1380001 [wp = VK_RMENU] (yes, I have a KEYUP without KEYDOWN) Wich is still not the same as Windows. So I think there is two problems here : - ISO_Level3_Shift is not properly recognized by Wine - "AltGr" doesn't have the same behavior under Wine and Windows FYI, attached patch is a workaround to have the same behavior than Windows. With it, I get this under Wine : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2 lp 1d0001 [note: wp = VK_LCONTROL] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4 lp 20380001 [note: wp = VK_LMENU] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c lp 20260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp e0260001 trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2 lp e01d0001 trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp c0380001 Which is still not the same as Windows : - Windows uses (right) control + menu (with fExtended flag for menu) whereas Wine uses left control + left menu. Not investigated if this is related to TranslateMessage. - AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message, wheras Wine send nothing. Note that I had to disable the XFilterEvent test in event.c to have those messages, otherwise nothing is sent to the program (but that’s another story for another bug report) But it suffice for my use case (WoW key bindings with right alt) -- 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 9

[Bug 57925] New: winewayland.drv: Games are not filled to my monitor's resolution
by WineHQ Bugzilla 30 Nov '25

30 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57925 Bug ID: 57925 Summary: winewayland.drv: Games are not filled to my monitor's resolution Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78178 --> https://bugs.winehq.org/attachment.cgi?id=78178 SWAT 4 output log (in this log I opened the settings and tried to set the maximum resolution that the game supports) Old games (specifically Ghost Recon, Splinter Cell 1, Splinter Cell 2 and SWAT 4) won't fill to my monitor's resolution, even if I switch to a higher resolution in the game settings. This MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/6804) was supposed to work with winewayland.drv and fix this issue, but it doesn't work or fix it. However, this MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/5057) does work and fixes that issue. There is a workaround (at least for SWAT 4): which is to take the game window out of fullscreen, then toggle the maximization state of the game window and put the game window back into fullscreen (In labwc/openbox terms: ToggleFullscreen > ToggleMaximize > ToggleFullscreen). I think it also works for Ghost Recon. Splinter Cell 1 even supports 16:9 resolutions, but only in game (in the menus, loadings and cut-scenes are still not filled in for my monitor's resolution) and Splinter Cell 2 is worse, there's no support for 16:9 resolutions or even a workaround. - I use labwc/wlroots as WM. - I'm using the new WoW64 mode. I did some tests with normal wine, but it's been a few weeks or months, so I'm not sure if the new WoW64 mode has any impact here, but I don't think so. (Sorry if the paraphrases seem disconnected from each other, if I'm not very clear or if I'm giving too little information. I've been doing a lot of testing over the last few hours and my mind isn't in a good place to come up with a good text here :/) -- 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 8

[Bug 57584] New: 8-bit color mode is broken in Wine 9.11 and later
by WineHQ Bugzilla 29 Nov '25

29 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57584 Bug ID: 57584 Summary: 8-bit color mode is broken in Wine 9.11 and later Product: Wine Version: 9.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 77694 --> https://bugs.winehq.org/attachment.cgi?id=77694 Regedit on Wine 9.22 in Xephyr Similar to Bug 48088, palette colors are being mapped incorrectly again. Steps to reproduce: 1. In one terminal, run `Xephyr :2 -ac -screen 800x600x8` 2. In a second terminal, run `DISPLAY=:2 openbox` 3. In a third terminal, run `DISPLAY=:2 wine regedit` `git bisect` says: commit 6ace92e0cafcc381f324fc831f3006fb15db4b4e (HEAD) Author: Rémi Bernon <rbernon(a)codeweavers.com> AuthorDate: Mon Jun 3 17:48:30 2024 +0200 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Mon Jun 3 23:24:59 2024 +0200 winex11: Create a HBITMAP for the allocated surface pixels. dlls/winex11.drv/bitblt.c | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------- 1 file changed, 58 insertions(+), 19 deletions(-) -- 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 51546] New: ran a application and it gave an error
by WineHQ Bugzilla 28 Nov '25

28 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=51546 Bug ID: 51546 Summary: ran a application and it gave an error Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrtbryanonlinux(a)gmail.com Distribution: --- Created attachment 70389 --> https://bugs.winehq.org/attachment.cgi?id=70389 Im trying to run Xenos64.exe for gta v and then that happened plz help tried to run a application called xenos64.exe i use it for gta v so i wined it then that happened. plz try and fix ASAP -- 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 8

← Newer
1
...
4
5
6
7
8
9
10
...
90
Older →

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 July 2025