August 2024 - Wine-bugs - list.winehq.org

[Bug 37263] New: World Of Warcraft: stuck keys
by wine-bugs＠winehq.org 14 Sep '24

14 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=37263 Bug ID: 37263 Summary: World Of Warcraft: stuck keys Product: Wine Version: 1.7.25 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: brian(a)infinityplusb.com I'm running WoW 5.4.8. At random intervals keys appear "stuck", even though they are not physically stuck. I can really only notice the ones where the "stuck key" is for moving (e,d,s,f) cause the character keeps strafing or running. Sometimes repressing these keys causes the key to unstick, but that's maybe a 20-25% success rate. Maybe less. I'm new to this bug-filing thing so I'll try replicate the issue. I'm not sure this issue is specific to Warcraft, but it's the only game I play. There are other google tracks related to this, but they seem quite old (pre-2008). -- 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 11

[Bug 57121] New: wine make keys sticky
by WineHQ Bugzilla 14 Sep '24

14 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57121 Bug ID: 57121 Summary: wine make keys sticky Product: Wine Version: 9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs(a)winehq.org Reporter: axet(a)me.com Distribution: --- Hello! Playing wine games I notices key become sticky sometimes. Pressing keys makes no effect in the game for some delay and then all keys get burst into game making character cast / jump like you pressed it at once. This is only affecting keyboard input, mouse input is not affected. When keys are sticky you still can use mouse do move, left / right clicks and character responds to it. I found out that it is easy to reproduce by using slow USB flash drive (4MB/s write 20MB/s read) when you put all data into it: wine binaries, cache folder (with mesa_shader_cache using XDG_CACHE_HOME variable), game it self. When you start a game using this setup allays keys get sticky, but mouse is never affected. It is happening also when game and wine and cache on the HDD but much more rarely. I guess when USB flash got accessed by linux kernel. I'm using: debian trixie wine 9.16 i3-12100F // RX 6600 (amdgpu) -- 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 56030] New: Left 4 Dead 2 Version 2.2.0.0 Keyboard / Mouse inputs not properly recognized.
by WineHQ Bugzilla 14 Sep '24

14 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=56030 Bug ID: 56030 Summary: Left 4 Dead 2 Version 2.2.0.0 Keyboard / Mouse inputs not properly recognized. Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- With Wine-9.0-rc1 Left 4 Dead 2 Version 2.2.0.0 does not properly recognize keyboard / mouse inputs. It seems that in some cases key state changes are ignored. I.e. The key "gets stuck" in the last read state. Causing behaviors like the player not moving despite any of the WSAD keys being held down, continuing to move in a single direction, or the player constantly firing / reloading / switching a weapon (similar to a turbo controller) despite the mouse having only been clicked / scrolled once (and the mouse not having a turbo mode). This seems to happen about once every ~15-20 seconds. Making the game unplayable. It also seems that the only way for the key to be "unstuck" is to change it's state while the game is getting input. For example, If the player is stuck firing a weapon, the player needs to manually fire the weapon again (Mouse1 by default) and release the key before the game ignores input again to make the weapon stop firing. Simply doing nothing will *not* fix the key state as far as the game is concerned. It should be noted that mouse movement does not seem to be affected by this. As the player can still use mouse look normally despite the above behaviors. -- 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 53994] New: Internet Explorer 11: Install fails due to lack of DISM.exe implementation
by WineHQ Bugzilla 13 Sep '24

13 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=53994 Bug ID: 53994 Summary: Internet Explorer 11: Install fails due to lack of DISM.exe implementation 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: masterbuilder102(a)gmail.com Distribution: --- Created attachment 73579 --> https://bugs.winehq.org/attachment.cgi?id=73579 Log of IE11. (Contains two duplicate install attempts). Info: Debian 11, 32 bit wine prefix. Workarounds: Need to use native version of inseng.dll Download Link for IE11 32 bit: https://web.archive.org/web/20210701100535/http://download.microsoft.com/do… When installing IE11, it checks for a few files d3d11.dll api-ms-win-downlevel-user32-l1-1-0.dll Ntoskrnl.exe api-ms-win-security-base-l1-1-0.dll conhost.exe segoeui.ttf taskhost.exe tcpip.sys tdh.dll Wine lacks taskhost.exe, tcpip.sys, tdh.dll and segoeui.ttf, manually copying these files over will cause the installer to not manually install it, except for segoeui.ttf which fails regardless if the file is present. In my log I have all these files copied over already which is why they all say (True). Based on Bug 43509 I believe the issue is that the wine implementation of dism.exe is incomplete, but I also think it is possible to get IE11 working if the segoeui.ttf check can be done. -- 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 24684] New: SMP problems with Source games
by wine-bugs＠winehq.org 11 Sep '24

11 Sep '24

http://bugs.winehq.org/show_bug.cgi?id=24684 Summary: SMP problems with Source games Product: Wine Version: 1.3.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pitlicek(a)gmail.com Some games with latest Source engine (Alien Swarm, Left for Dead 2) has sometimes grayed out "Enable multicore rendering" in options menu. But when It's not grayed out, and I enable it, it works like it's supposed to, giving me notable fps boost and using both my CPU cores. But I'm using virtual desktop, to still be able to communicate with my friend using IM. But sometimes, when I leave virtual desktop and want to return back, the VD is not redrawing. I can still hear music, game sounds, even blindly open in-game console nad write quit to exit the game properly. This is not happening if multicore is disabled in game. -- 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 29

[Bug 54249] New: Temple of Elemental Evil Demo Backtrace
by WineHQ Bugzilla 11 Sep '24

11 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=54249 Bug ID: 54249 Summary: Temple of Elemental Evil Demo Backtrace Product: Wine Version: 8.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: --- Created attachment 73802 --> https://bugs.winehq.org/attachment.cgi?id=73802 Backtrace 8.0-rc2 (Slackware 15.0) Hello everyone, I was revisiting bug 9304 and did a fresh install from: https://www.fileplanet.com/archive/p-12410/The-Temple-of-Elemental-Evil-Demo sha256sum ToEE_Demo.exe 827a280487c3615ae4be0185daefbb63098a93c71f6a21409446040969e8c6a9 ToEE_Demo.exe I ran into the problem that now a backtrace is thrown in 8.0-rc2 -- 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 43461] New: NoLimits2 crashes on startup
by wine-bugs＠winehq.org 11 Sep '24

11 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=43461 Bug ID: 43461 Summary: NoLimits2 crashes on startup Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: alt.stephan(a)web.de Distribution: --- Created attachment 58835 --> https://bugs.winehq.org/attachment.cgi?id=58835 Wine console messages While initializing, the program quits with a fatal error: The application failed with: D3DXAssembleShader return with an unexpected error. (see crash.png) Wine console log (crash.log) attached below, as well as the wine "crash detected" log (err_report.log). I tried with both UseGLSL enabled and disabled. -- 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 15

[Bug 29947] New: Option to set virtual desktops to the current resolution
by wine-bugs＠winehq.org 09 Sep '24

09 Sep '24

http://bugs.winehq.org/show_bug.cgi?id=29947 Bug #: 29947 Summary: Option to set virtual desktops to the current resolution Product: Wine Version: 1.4-rc4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified At default the option "Emulate a virtual desktop" is set to 800x600 in winecfg. What about an option that sets the desktop size for virtual desktops automatically to the resolution of the system? -- 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 19

[Bug 57061] New: SRWLock is slower than CriticalSection on wine. Why?
by WineHQ Bugzilla 09 Sep '24

09 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57061 Bug ID: 57061 Summary: SRWLock is slower than CriticalSection on wine. Why? Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: euloanty(a)live.com Distribution: --- https://github.com/cppfastio/fast_io/blob/next/benchmark/0002.file_io_tsc/t… [cqwrteur(a)DESKTOP-9B705LH time]$ wine ./iobuf_file_lockable_critical_section.exe output:0.3784567s input:0.1407622s [cqwrteur(a)DESKTOP-9B705LH time]$ rm *.txt [cqwrteur(a)DESKTOP-9B705LH time]$ wine ./iobuf_file_lockable_srwlock.exe output:0.5857926s input:0.3284965s [cqwrteur(a)DESKTOP-9B705LH time]$ rm *.txt This is very strange tbh. Because on windows SRWLock is faster than CriticalSection. I have checked wine's implementation and I don't see why SRWLock is slower than CriticalSection on wine either since the implementation is very simple. -- 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 57095] New: Latest Wine Install - Installed windows App - LovenseConnect.exe Launched / displayed error
by WineHQ Bugzilla 08 Sep '24

08 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57095 Bug ID: 57095 Summary: Latest Wine Install - Installed windows App - LovenseConnect.exe Launched / displayed error Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: chad(a)devrizon.com Distribution: --- Created attachment 76975 --> https://bugs.winehq.org/attachment.cgi?id=76975 Ubuntu 24.04 running wine 9.0 launched LovenseConnect.exe / cricital error displayed i installed the latest WINE package on Linux Ubuntu 24.04. Installed the application LovenseConnect.exe and recieved the error during the launch of the application. -- 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