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

[Bug 57198] New: Chessbase 11: Incorrect vertical window size if moved to external monitor and restarted
by WineHQ Bugzilla 17 Sep '24

17 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57198 Bug ID: 57198 Summary: Chessbase 11: Incorrect vertical window size if moved to external monitor and restarted Product: Wine Version: 9.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dav75uk(a)yahoo.co.uk Distribution: --- Starting chessbase 11 on my laptop screen. I move the window to my external monitor. I close it there. I restart and it's moved back to the laptop monitor. The vertical size of the window has changed to less than 100 pixels. I have to resize it from the menu bar as resize by dragging the edge stops being available. I'd expect the size to be the same (both screens are 4K). I don't know if I should be expecting it to reopen on the same screen. Happy to jump on a zoom call to demonstrate / debug. -- 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 51202] New: Chessbase 11 Incorrect window brought to front on search termination
by WineHQ Bugzilla 17 Sep '24

17 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=51202 Bug ID: 51202 Summary: Chessbase 11 Incorrect window brought to front on search termination Product: Wine Version: 6.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dav75uk(a)yahoo.co.uk Distribution: --- In Chessbase 11, when search is terminated (manually or by completion) a different ChessBase window (main one?) is brought to the front rather than refreshing the current one. This has always been an issue in 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 2

[Bug 657] Many games and applications need 'mfc42.dll' ('winetricks -q mfc42' is a workaround)
by WineHQ Bugzilla 16 Sep '24

16 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=657 jacobbrett+winehqbugs(a)jacobbrett.id.au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacobbrett+winehqbugs(a)jacob | |brett.id.au -- 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

[Bug 12532] New: Autodesk TrueView fails to install
by wine-bugs＠winehq.org 16 Sep '24

16 Sep '24

http://bugs.winehq.org/show_bug.cgi?id=12532 Summary: Autodesk TrueView fails to install Product: Wine Version: CVS/GIT Platform: PC URL: http://usa.autodesk.com/adsk/servlet/index?id=6703438&si teID=123112 OS/Version: Linux Status: UNCONFIRMED Keywords: download, Installer Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: xerox_xerox2000(a)yahoo.co.uk Hi, a user submitted this new app into appdb with garbage test results, so i gave it a try as well. That user reported a problem that the disk was full, but i can't reproduce that, it fails differently here. To run into this bug you need Alex Villacis' patch here: http://article.gmane.org/gmane.comp.emulators.wine.patches/49916 hopefully that patch will make it into git monday. after applying that patch the intaller failed with a message 'Call not implemented' The problem seems to be: fixme:MsiDatabaseGenerateTransformW By just returning ERROR_SUCCESS, it ran into two other unimplemnted functions: MsiQueryFeatureStateFromDescriptorA and MsiCreateTransformSummaryInfoW By stubbing these out with ERROR_SUCCESS the installer claimed to be successfull (but i guess that's doubtful). Anyway , this all shows that these three functions need to be implemented to get this installer finish, and that's where I created this bug for. -- 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 53

[Bug 57157] New: winedbg: can't attach to windows process
by WineHQ Bugzilla 16 Sep '24

16 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57157 Bug ID: 57157 Summary: winedbg: can't attach to windows process Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)jmbreuer.net Distribution: --- I'm trying to debug a hang/freeze concerning Fallout 1 (it's still available on Epic for free for a couple of hours, if someone should want to replicate specifically). Got myself to a point to run winedbg against the game, provoke the hang (in my case, I just need to press Escape to open the in-game save/options/... menu). Now, I want to have a look where all threads of the game are. Wine-dbg>info process pid threads executable (all id:s are in hex) 00000168 6 'falloutwHR.exe' 0000008c 3 'explorer.exe' 00000038 8 'services.exe' 000000e0 6 \_ 'rpcss.exe' 000000c0 3 \_ 'svchost.exe' 000000a8 4 \_ 'plugplay.exe' 00000068 8 \_ 'winedevice.exe' 00000044 8 \_ 'winedevice.exe' 00000020 1 'start.exe' 0000010c 1 \_ 'winedbg.exe' =0000011c 1 \_ 'winedbg.exe' >00000124 9 \_ 'Launcher.exe' 00000114 1 \_ 'Launcher.exe' 00000104 2 \_ 'conhost.exe' OK, so, switch to falloutwHR.exe first, I guess: Wine-dbg>attach 00000168 syntax error Wine-dbg>attach 168 syntax error Um. What am I doing wrong? Or is there something really weird broken? - I see that there's a testing package of wine 9.16 for my distro (gentoo), I'll try that next. -- 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 57185] New: Virtual DJ 2024: Unable to show drives on explorer panel
by WineHQ Bugzilla 16 Sep '24

16 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=57185 Bug ID: 57185 Summary: Virtual DJ 2024: Unable to show drives on explorer panel Product: Wine Version: 9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rizalmart98(a)gmail.com Distribution: --- When expanding the DRIVES folder on explorer panel (panel at the lower left corner) when clicking the "+" button, it does not show the drives detected instead of showing C: and Z: drives after expanding the DRIVES folder -- 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 51732] New: TradeStation Installer: Unable to register servers. Setup will now abort.
by WineHQ Bugzilla 15 Sep '24

15 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=51732 Bug ID: 51732 Summary: TradeStation Installer: Unable to register servers. Setup will now abort. Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christopher.m.penalver(a)gmail.com Distribution: Ubuntu Created attachment 70617 --> https://bugs.winehq.org/attachment.cgi?id=70617 WINEDEBUG=+relay wine 'TradeStation Setup.exe' 2>&1 Hello, attempting to install TradeStation from https://update.tradestation.com/Installs/TradeStation/10.00.02.925/TradeSta… with wine 6.0.1 causes a window to pop up noting precisely: Unable to register servers. Setup will now abort. In other words, the install fails and the user is left scratching their head about why it doesn't 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.

1 4

[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