March 2025 - Wine-bugs - list.winehq.org

[Bug 55138] New: msys2: bash.exe is not able to fork/start another process.
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=55138 Bug ID: 55138 Summary: msys2: bash.exe is not able to fork/start another process. Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 74697 --> https://bugs.winehq.org/attachment.cgi?id=74697 allocation stacks in parent and child bash.exe This is a followup to bug 47808. If I understand it right, bug 47808 was primarily about native libraries getting called at a win32 stack which was not yet committed. Those native libraries then jumped over the guard page, therefore the stack got not grown, instead a crash reported. This aspect was fixed by using the syscall interface and therefore bug 47808 was closed. But there is another issue that causes a msys2-forked process crashing, because after the stack was grown it still misses the PAGE_READWRITE flags. For this Zeb Figura included in the first attachement to bug 47808 "always expand the stack if within the stack reserve" a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE" to the page that gets the VPROT_GUARD removed in grow_thread_stack. This modification still enables a forked process to run. The issue can be reproduced with an unmodified wine by just - running msys2 bash.exe interactively - then trying to start e.g. notepad from it. Attached file shows the stack when the stack gets allocated - in a working msys2-parent process and - in a failing msys2-forked child process. Therefore it looks like the forked stack get really setup differently, but it is still not clear if or when this memory gets the READ/WRITE added in native windows. -- 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 37131] New: Clang Static Analyzer: Division by zero
by wine-bugs＠winehq.org 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=37131 Bug ID: 37131 Summary: Clang Static Analyzer: Division by zero Product: Wine Version: 1.7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lukebenes(a)hotmail.com Clang Static Analyzer identifies Division by zero File: dlls/winex11.drv/palette.c Location: line 601, column 43 Description: Division by zero #define NB_RESERVED_COLORS 20 ... static void X11DRV_PALETTE_FillDefaultColors(....) { ... int i = 0, idx = 0; int red, no_r, inc_r; ... if (palette_size <= NB_RESERVED_COLORS) return; while (i*i*i < (palette_size - NB_RESERVED_COLORS)) i++; no_r = no_g = no_b = --i; ... inc_r = (255 - NB_COLORCUBE_START_INDEX)/no_r; //Clang: Division by zero ... } The code will continue executing if the palette_size variable is larger than or equal to 21. With the value 21, the 'i' variable will be first incremented by one and then decremented by one. As a result, the 'i' variable will remain equal to zero, which will cause the division-by-zero error. -- 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 5

[Bug 31212] New: Some VST instruments crash when reloaded in Mixcraft
by wine-bugs＠winehq.org 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=31212 Bug #: 31212 Summary: Some VST instruments crash when reloaded in Mixcraft Product: Wine Version: 1.5.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: s_chriscollins(a)hotmail.com Classification: Unclassified In Mixcraft, some VST instruments crash when loaded a second time on a track. However, the same instruments work fine when loaded for the first time on a track. The following can be reproduced easily in Mixcraft: 1. Start Mixcraft and select "Build Virtual Instrument Tracks" from the "New Project" window. 2. Click on the keyboard icon next to the first track name, which will bring up the instrument selection window. 3. Select "<VSTi Instruments>" from the left pane and then "Messiah" from the right pane. This sets the track to use the Messiah VSTi synth. 4. Now select "Acoustica Instruments" from the right pane. 5. Once again, select "Messiah" from the right pane. Mixcraft will pop up an error box with the title "An instrument has crashed" containing the following text: "A crash has been detected in the instrument "Messiah." This plug-in has been muted. We recommend you save your project and re-start Mixcraft to avoid losing your work." Unfortunately, no helpful terminal output seems to be generated in relation to the plugin crash. I have provided more detailed notes on VST behavior in Mixcraft here: https://docs.google.com/document/d/1YEPh0mkd_ip1whAJXcRIl4HYny5D8LSeGo3qgzV… ** My System ** OS: Kubuntu 12.04 64-bit w/ KDE SC 4.8.4 Motherboard: ASRock X58 Extreme3 (Intel X58 chipset) CPU: Intel Core i7 (2.8 GHz quad-core) RAM: 12GB DDR3 Video: Dell NVIDIA GeForce 7800 GTX w/ 256 MB RAM (PCI Express) Sound Card #1: Sound Blaster Audigy 2 ZS Gold Sound Card #2: Echo Gina3G Linux Kernel: 3.2.0-26-generic NVIDIA video driver: 302.17 Screen Resolution: 1280 x 960 -- 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 16

[Bug 55019] New: kernel32:process - Accents cause test_Environment() to fail on Windows
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=55019 Bug ID: 55019 Summary: kernel32:process - Accents cause test_Environment() to fail on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:process - Accents cause test_Environment() to fail on Windows: process.c:1267: Test failed: Parent-env string CI_COMMIT_AUTHOR=Bernhard Klbl <besentv(a)gmail.com> isn't in child process process.c:1267: Test failed: Parent-env string CI_COMMIT_DESCRIPTION= Signed-off-by: Bernhard Klbl <besentv(a)gmail.com> isn't in child process process.c:1267: Test failed: Parent-env string CI_COMMIT_MESSAGE=mf/tests: Remove duplicate call to MFStartup(). Signed-off-by: Bernhard Klbl <besentv(a)gmail.com> isn't in child process process.c:1292: Test failed: Child-env string CI_COMMIT_AUTHOR=Bernhard K"lbl <besentv(a)gmail.com> isn't in parent process process.c:1292: Test failed: Child-env string CI_COMMIT_DESCRIPTION= Signed-off-by: Bernhard K"lbl <besentv(a)gmail.com> isn't in parent process process.c:1292: Test failed: Child-env string CI_COMMIT_MESSAGE=mf/tests: Remove duplicate call to MFStartup(). Signed-off-by: Bernhard K"lbl <besentv(a)gmail.com> isn't in parent process See https://test.winehq.org/data/patterns.html#kernel32:process These failures happen in about 15% of the runs and in all of them the environment variable was supposed to contain an accent. This also explains why the failures: * Are always about the GitLab environment variables: in our regular test configurations environment variables don't contain accents. * Only happen on the GitLab CI Windows test VM: this VM is the only one where the environment variables change from one run to the next, mostly due to CI_COMMIT_XXX. * Always happen in both the 32- and 64-bit tests of a given build. -- 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 57020] New: Anritsu Software Toolbox doesn't install properly
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=57020 Bug ID: 57020 Summary: Anritsu Software Toolbox doesn't install properly Product: Wine Version: 9.14 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Download: https://dl.cdn-anritsu.com/en-us/test-measurement/files/Software/Drivers-So… To test - Run the installer in clean WINEPREFIX - Uncheck "Check for Updates" - Select all components (default) - When it asks something about the "NI VISA" runtime, select "Yes" In the install folder (default .wine/drive_c/Program Files (x86)/Anritsu) there hsould be folders like "Line Sweep Tools" and other. On Wine, those are missing. The problem can be worked around by using "winetricks -q dotnet35" before attempting the install. Not sure why it can't use wine-mono. Another way to possibly test: You can unpack the installer exe with 7-zip, then the $TEMP folder contains the installers, e.g. LST_V1.71_Installer.exe If you run those, they will complain about missing .NET 3.5 as well. -- 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 57656] New: CryptMsgGetParam() with CMSG_SIGNER_AUTH_ATTR_PARAM/CMSG_SIGNER_UNAUTH_ATTR_PARAM returns success with 0 buffer size
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=57656 Bug ID: 57656 Summary: CryptMsgGetParam() with CMSG_SIGNER_AUTH_ATTR_PARAM/CMSG_SIGNER_UNAUTH_ATTR_PA RAM returns success with 0 buffer size Product: Wine Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- This is currently triggered by wintrust tests from test_wintrust_digest(). The issue is that GetParam returns TRUE when there is no attributes to return. That leads to malloc(0) and then attempt to read attributes from that. I don't know how to write a proper test for this at crypt32 side, so filing a bug instead. -- 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 42033] New: Fallout 3: Radio music not playing
by wine-bugs＠winehq.org 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=42033 Bug ID: 42033 Summary: Fallout 3: Radio music not playing Product: Wine Version: 2.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aaronbpaden(a)gmail.com Distribution: --- Created attachment 56507 --> https://bugs.winehq.org/attachment.cgi?id=56507 log When listening to the radio in Fallout 3, the DJ's voice works, but the songs don't. Sometimes you'll hear the song start for a second, but then it stops and the DJ's voice starts up again. This happens both on GNR and the enclave station. -- 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 32

[Bug 50278] New: Diggles: The Myth of Fenris (GOG version) crashes on launch
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=50278 Bug ID: 50278 Summary: Diggles: The Myth of Fenris (GOG version) crashes on launch Product: Wine-staging Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lcaffe(a)inbox.lv CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68826 --> https://bugs.winehq.org/attachment.cgi?id=68826 When runnning main executable 'Diggles.exe' Game Diggles: The Myth of Fenris https://www.gog.com/game/diggles_the_myth_of_fenris Crashes on startup (log attached), the screen becomes black for a second or two. -- 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 57802] New: 10 is not saving WordPro's "view Settings"
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=57802 Bug ID: 57802 Summary: 10 is not saving WordPro's "view Settings" Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com Distribution: --- Dear Support, SmartSuite-N99.8.0208.0800 Fedora 41 wine-stable-10.0.0-1.1.x86_64 winehq-stable-10.0.0-1.1.x86_64 Wine stable 10 is not saving Word Pro's "View setting". You have to set up your view settings in a Windows virtual machine and export the view setting from regedit. Then import them into Wine's regedit: for example: REGEDIT4 [HKEY_CURRENT_USER\SOFTWARE\Lotus\WordPro\99.0\lwpuser.ini\WordProUser] "ViewMode"="256" "ViewPreference2"="514" "ViewPreference"="527945365" The above is margin width and show tabs. These entries were all missing in Wine until I regedit imported them. Please fix. Many thanks, -T -- 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 56128] New: Genshin Impact: after changing to another window and back, input does not work anymore
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=56128 Bug ID: 56128 Summary: Genshin Impact: after changing to another window and back, input does not work anymore Product: Wine Version: 8.0.2 Hardware: x86-64 URL: https://genshin.hoyoverse.com/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 9427421240(a)posteo.net Distribution: --- Created attachment 75800 --> https://bugs.winehq.org/attachment.cgi?id=75800 Log After changing to another window and then back to the game (with Alt + TAB, for example), no input will be accepted anymore. Neither keyboard, mouse, nor gamepad will work until the game is restarted. After switching to another window, this will be added to the log multiple times, until returning to the game: "0238:fixme:win:NtUserGetKeyboardLayout couldn't return keyboard layout for thread 0074" There are multiple menu-options in the game that start a webbrowser, after which this issue will happen, so it is probably quite likely to happen during normal play once in a while. If i press the screenshot-key on my keyboard to access the screenshot-UI of GNOME, use it with the mouse-pointer, and then go back to the game, input will still work; this is the only exception i noticed. It is more like an overlay than a window, so i guess the focus still remains on the game while using it. Desktop-environment: GNOME (Wayland) Operating-system: Debian GNU/Linux Testing (Trixie) Wine-versions tested: 8.0.2, devel 8.18, 9.0-rc-3 Game-version: 4.3 -- 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