wine-bugs June 2025

wine-bugs@winehq.org

1 participants
612 discussions

[Bug 58364] New: Major change from 10.9 to 10.10 with Pegasus Email Program
by WineHQ Bugzilla 28 Jun '25

28 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58364 Bug ID: 58364 Summary: Major change from 10.9 to 10.10 with Pegasus Email Program Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikes(a)kuentos.guam.net Distribution: --- Created attachment 78762 --> http://bugs.winehq.org/attachment.cgi?id=78762 Image after 10.10 installed? Bad Has worked fine with version of 10.9 and before, but now 10.10 comes with an unusable screen. Adding to screen shots with 10.9 and 10.10. Works fine after downgrade back to 10.9? -- 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 42882] New: rs232 port access no working with ubuntu 17.10 worked fine with previous versions of ubuntu
by wine-bugs＠winehq.org 28 Jun '25

28 Jun '25

https://bugs.winehq.org/show_bug.cgi?id=42882 Bug ID: 42882 Summary: rs232 port access no working with ubuntu 17.10 worked fine with previous versions of ubuntu Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arcadeshopper(a)gmail.com Distribution: --- I am able to connect to the serial port via applications in wine but there is never any data received. I can communicate outside of wine without issue using minicom. I am using a ftdi usb to serial adapter that worked fine in previous versions of ubuntu. I am having this problems with all relases of wine I have tried including the default ubuntu package and 2.4 from the PPA -- 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 30

[Bug 58410] New: dotnet35 and dotnet35sp1 fail to install
by WineHQ Bugzilla 28 Jun '25

28 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58410 Bug ID: 58410 Summary: dotnet35 and dotnet35sp1 fail to install Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: sergiolaverde0(a)gmail.com Distribution: --- Created attachment 78820 --> http://bugs.winehq.org/attachment.cgi?id=78820 Console output of `winetricks dotnet35sp1` When trying to install .NET 3.5 in any of its forms it fails. The installer allows you to accept the License, and after hitting next a download bar fills, but then the installer says the installation failed. I have attached the console output of `winetricks dotnet35sp1`, and the output of dotnet35 is nearly identical. The bug persists after deleting the local cache, and .NET 4.8 installed successfully. Winetricks version: 20250102 - sha256sum: 53194dead910f8a5eb1deacaa4773d4e48f5873633d18ab1ecd6fdb0cb92243b Wine version: wine-10.0 -- 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 58420] New: Wine crashes when running msys2 iff CPU's PKU/PKRU feature is enabled
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58420 Bug ID: 58420 Summary: Wine crashes when running msys2 iff CPU's PKU/PKRU feature is enabled Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pipcet(a)protonmail.com Distribution: --- This is a heads-up about a bug in cygwin/msys2 which may be misreported as a wine bug. The Cygwin code assumes CPUID leaf 0x0d to indicate in EBX a 64-byte-aligned value. That may or may not be true on current Windows systems, but on current Linux systems running Wine, with recent CPUs, a CPU feature called "PKU" or "PKRU" (memory protection keys for userspace), enabled by default, indicates an additional 8-byte XSAVE area. This makes the Cygwin code attempt to xsave to a non-64-byte aligned area, which causes a segfault and abnormal program termination. While this is clearly a bug, it's a bug that apparently cannot be triggered by current Windows systems. This means Wine fails to be bug-for-bug compatible in this case. I don't think there's an easy way around that: we'd have to trap XGETBV and CPUID instructions to pretend that a feature that is enabled by Linux actually isn't available. It would have been nice if the Linux kernel had provided a way to disable the pku feature on a per-process basis, but AFAICT, it didn't. The nopku kernel command line argument makes things work, but requires a reboot and disables the very useful PKU feature for the entire system. So I don't think there's a good workaround here, but maybe we should suggest to the Linux kernel people to allow per-process activation of any future XCR0 features? -- 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 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 58343] New: Kathy Rain 2 - Soothsayer: Screen is completely black, making the game impossible to play
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58343 Bug ID: 58343 Summary: Kathy Rain 2 - Soothsayer: Screen is completely black, making the game impossible to play Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: memax(a)gmx.fr Distribution: --- Created attachment 78721 --> http://bugs.winehq.org/attachment.cgi?id=78721 Terminal output Game: Kathy Rain 2: Soothsayer Unity 2022 engine GOG.com DRM-free Windows version OS: Ubuntu 24.04 LTS NVIDIA Driver Version (proprietary): 570.133.07 (Performance mode) Windowing system: X11 Wine: wine-10.9 development version Default Wine configuration, unmodified Clean Wine prefix Description: You can hear the music, but the screen is completely black, making the game impossible to play. Workaround: Installing DXVK using winetricks solves the issue. -- 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 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 58321] New: Launch of windows application no longer works after upgrading to Wine version 10.9
by WineHQ Bugzilla 27 Jun '25

27 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=58321 Bug ID: 58321 Summary: Launch of windows application no longer works after upgrading to Wine version 10.9 Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: craigaschulstad(a)gmail.com Distribution: --- Created attachment 78679 --> http://bugs.winehq.org/attachment.cgi?id=78679 Log of application launch before and after 10.9 update After installing the latest version of Wine (10.9) on my Linux Mint virtual machine, launching a windows game application no longer worked. Fortunately, I had made a backup of my virtual machine image back in mid-May which had version 10.7, I was able to restore and reset my virtual machine and then walk through the point where my game application no longer worked. Once reset, I manually launched my game application from a terminal window and the game worked fine. Next, I ran the Linux update manager and updated all software components and operating system updates except for Wine 10.9. Once those updates were done, I again manually launched my game application from a terminal window and the game still worked fine. I next then used the Linux update manager and applied the Wine 10.9 update. After the update was completed, I once again manually launched my game application from the terminal window. I briefly saw the dialog box indicating my Wine configuration was being updated, and then the process ended without starting the game application. I retried launching the application but again the process ended. I am attaching some log snippets that detail the successful launch of the game application and subsequently the failure. What I did see in the logs that might provide a clue was that after the update to Wine 10.9, file "libEGL.so.1" could not be found. While awaiting an answer back, I am going to investigate this clue. Thank you in advance. -- 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 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

← Newer
1
2
3
4
5
6
7
8
...
62
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 June 2025