February 2026 - Wine-Bugs - list.winehq.org

[Bug 53574] New: MSYS2 "pacman -Sy" fails key lookup
by WineHQ Bugzilla Feb. 23, 2026

Feb. 23, 2026

https://bugs.winehq.org/show_bug.cgi?id=53574 Bug ID: 53574 Summary: MSYS2 "pacman -Sy" fails key lookup Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joel(a)airwebreathe.org.uk Distribution: --- Created attachment 72951 --> https://bugs.winehq.org/attachment.cgi?id=72951 Log of console interaction With a fresh Msys2 installation, pacman fails to run, because it keeps producing "key lookup failed" errors. The user is prompted to with the following message: error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown :: Import PGP key 5F944B027F7FE2091985AA2EFA11531AA0AA7F57? [Y/n] Y However, if the user selects "yes", pacman simply asks the same question again after a short delay, in an infinite loop. -- 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 6

[Bug 57484] New: VKB Joystick not detected in Wine 9.22 but works in 9.21
by WineHQ Bugzilla Feb. 23, 2026

Feb. 23, 2026

https://bugs.winehq.org/show_bug.cgi?id=57484 Bug ID: 57484 Summary: VKB Joystick not detected in Wine 9.22 but works in 9.21 Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joseph+winehq(a)xaosnet.net Distribution: --- I am using Wine-Staging from the WineHQ Repos on Ubuntu 24.04, and with Staging 9.22, my VKB Gunfighter Left is not detected if hidraw is enabled, but is detected with Staging 9.21, or if I check the box to disable hidraw. I reproduced this with a fresh wine prefix as well as an updated one. I've seen reports that this is also impacting some VKB Gladiator users as well on the Star Citizen Linux Users Group discord. -- 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 14

[Bug 31899] New: No keyboard input in La-Mulana remake
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=31899 Bug #: 31899 Summary: No keyboard input in La-Mulana remake Product: Wine Version: 1.5.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: twwinwood(a)gmail.com Classification: Unclassified Created attachment 41993 --> http://bugs.winehq.org/attachment.cgi?id=41993 Output of "env WINEDEBUG=-all,+keyboard,+key,+dinput,+message wine LaMulanaWin.exe" Per the AppDB entry for version 1.1.1.1, the game works as far as the menu screen but cannot be played due to the lack of response to keyboard input. -- 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.

3 26

[Bug 35907] New: Caps Lock state gets confused with multiple processes/threads
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=35907 Bug ID: 35907 Summary: Caps Lock state gets confused with multiple processes/threads Product: Wine Version: 1.7.15 Hardware: x86 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: ken(a)codeweavers.com Open two instances of Notepad in the same prefix: wine notepad & wine notepad & With one Notepad window active, turn Caps Lock on. Switch to the other Notepad window. Type some text. Notice it's not capitalized, although it should be. Turn Caps Lock off. Type some text. Notice that it is capitalized, although it shouldn't be. Switch back to the first Notepad window. Type some text. Notice that it is capitalized, although it shouldn't be. -- 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.

3 15

[Bug 45385] New: Wrong state of virtual keys after cycling windows. Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every key can be affected.
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

https://bugs.winehq.org/show_bug.cgi?id=45385 Bug ID: 45385 Summary: Wrong state of virtual keys after cycling windows. Usually VK_MENU, VK_SHIFT and VK_CONTROL, but every key can be affected. Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: johnfound(a)asm32.info Distribution: --- I noticed that the state of the keys sometimes sticks in pressed state. This happens when cycling windows with some shortcut key combination. For example if cycling with Alt+Tab, on pressing Alt, the program gets WM_KEYDOWN and the state of the VK_MENU becomes pressed. But after cycling windows, the program does not get WM_KEYUP because the window is not focused and VK_MENU (and the respective VK_LMENU or VK_RMENU) remain in pressed state. When cycling back to the program window, the window get focused only after releasing Alt key, so it does not get this event as well. If cycling windows with another shortcut key combination (for example Alt+Shift+Tab - for backward cycling) both VK_MENU and VK_SHIFT keys stick. In the same time, GetAsyncKeyState returns the proper state of the keys. Note1: The problem is obviously in the wineserver code, because it handles the key state tables for the different threads. Note2: The effect happens only sometimes. It seems the code for proper processing is already there, but some racing conditions have place. Note3: There is some probability that the effect is in result of my application code, but it never happens on real Windows, so I considered it a bug. Note4: I tried to workaround this problem by reading the whole table by GetAsyncKeyState and setting it then with SetKeyboardState on WM_ACTIVATE message of the main window. This workaround actually works, but is too ugly IMO. The same trick on WM_ACTIVATEAPP does not work. -- 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.

3 4

[Bug 26269] New: BioShock 2: Loss of keyboard input on loading screen
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=26269 Summary: BioShock 2: Loss of keyboard input on loading screen Product: Wine Version: 1.3.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: mgavl69(a)juno.com Created an attachment (id=33488) --> (http://bugs.winehq.org/attachment.cgi?id=33488) trace +keyboard On the inital 'New Game' loading screen you cannot use the space bar to continue. Keyboard and mouse input is recognised correctly when adjusting settings in the menus. Wine version 1.3.14-git Xserver v1.10.0 -- 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.

3 33

[Bug 37966] New: xrandr12 regression for nvidia users across a range of applications (too many to list)
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

https://bugs.winehq.org/show_bug.cgi?id=37966 Bug ID: 37966 Summary: xrandr12 regression for nvidia users across a range of applications (too many to list) Product: Wine Version: 1.7.35 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Dead Space 3: "Your Graphics Card does not meet Dead SpaceTM 3 minimum requirements." Call of Juaraz: "Failed to initialize rendering device. Check if your graphic card supports DirectX 9.0c" Overlord: Unhandled exception Overlord II Unhandled exception ...surely many more but you get the idea. Reverting commit 8e9e4a657f29ff018c6296ced1f115ca8731e5e6 (introduced in 1.7.35) makes all these problems go away. Furthermore, this commit introduces all the warnings reported in bug 34348. I have never seen these warnings produced on my Nvidia-based laptop prior to 1.7.35, and I now get them even when not running a 3D application (eg. cmd.exe). Nvidia GTX660M nvidia 346.35 driver $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.9*+ 39.9 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) Let me know if there's anything else you need. -- 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.

3 16

[Bug 26898] New: wine does not show save game screenshots
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=26898 Summary: wine does not show save game screenshots Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: vaniaz(a)msn.com Screenshots are saved in dds format. When saving game, I get the following in console fixme:d3d_surface:surface_convert_format Cannot find a conversion function from format WINED3DFMT_B8G8R8A8_UNORM to WINED3DFMT_DXT1. Saved screenshot is completely black. -- 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.

3 35

[Bug 23166] New: X-Blade's launcher does not display background, button images and cannot be closed.
by wine-bugs＠winehq.org Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=23166 Summary: X-Blade's launcher does not display background, button images and cannot be closed. Product: Wine Version: 1.2-rc3 Platform: x86 URL: http://games.on.net/file/25712/X-Blades_Demo OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrew.millington(a)gmail.com The launcher does not display *the background instead it displays gray background *the images for the buttons instead it displays generic Window's buttons plus you cannot close the launcher eg "Exit" or "Run Game". Both appear to be in a launcher.dat file body.bmp (background) /img/*.png (button images) Installing Internet Explorer 6 allows the images to displayed and you can close the launcher -- 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.

3 25

[Bug 59447] New: No visual difference between enabled and disabled tree view element
by WineHQ Bugzilla Feb. 23, 2026

Feb. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=59447 Bug ID: 59447 Summary: No visual difference between enabled and disabled tree view element Product: Wine Version: 11.3 Hardware: x86-64 URL: https://github.com/SimplexDesigns/Windows-Components-T ester/releases/download/v1-release/Release.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: gsw.eugeneulan(a)gmail.com Distribution: Ubuntu Created attachment 80431 --> http://bugs.winehq.org/attachment.cgi?id=80431 Running Windows Component Tester on different systems All disabled window elements have some sort of gray color applied to them, except for the Tree View. This is very confusing, as with no visual difference the user should interact with an element to see whether it's disabled or not. You can use Windows Components Tester utility for additional testing: 1. Download its archive by the direct link included in the bug's URL field; 2. Extract the archive; 3. Run "Windows Component Tester.exe" in the default Wine prefix; 4. Go to the "Item View" tab at the top; 5. See and compare observed and expected results on the attached screenshot! -- 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 0