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.
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.
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.
http://bugs.winehq.org/show_bug.cgi?id=58373
Bug ID: 58373
Summary: Bejeweled 3 runs but the screen is black
Product: Wine
Version: 10.10
Hardware: x86-64
URL: https://store.steampowered.com/app/78000/Bejeweled_3/
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: 260346a9160568004b9cb123608fb988c30623f1
Distribution: ArchLinux
This is a regression in Wine-10.10 caused by the commit that fixed bug #58064
for me:
commit 260346a9160568004b9cb123608fb988c30623f1
winex11: Remove old window drawable lookup and check.
If a surface has already been created, the window would have a pixel
format set already and the if above this would be taken already.
After starting Bejeweled 3, the game runs because I can hear the music, but the
screen remains black.
Occurs in virtual desktop and full-screen mode too.
Disabling CSMT works around the problem for me.
The game can be launched without Steam running.
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 575.57.08
X.Org X Server 1.21.1.16
XFCE/XFWM 4.20
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58381
Bug ID: 58381
Summary: "musl: Use __builtin_rint if available" breaks clang
builds (except aarch64)
Product: Wine
Version: 9.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
CC: piotr(a)codeweavers.com
Regression SHA1: ee6e83dca874491329c5b376c2f9563093e3c69f
Distribution: ---
Since "musl: Use __builtin_rint if available",
ee6e83dca874491329c5b376c2f9563093e3c69f, any calls to rint end up in infinite
loops, when built with Clang (except on aarch64).
If Clang doesn't have any good implementation of "__builtin_rint", it generates
a function call to "rint", even if built with -fno-builtin. See
https://gcc.godbolt.org/z/aYb3c1Ks1 for examples of the generated code. Only on
aarch64, Clang generates an inline implementation.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=58372
Bug ID: 58372
Summary: EZNEC pro2+ 7.0 runs, but calculations have errornous
exponential values
Product: Wine
Version: 10.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: johann.woeckinger(a)linznet.at
Distribution: ---
Created attachment 78782
--> http://bugs.winehq.org/attachment.cgi?id=78782
In the value list, one can see, that the calculated value of the wavelength is
wrong by a factor of 10^12 (should be 29.5653)
Application can be downloaded from:
https://eznec.com/v7download/pro2+download.php
The application runs without error messages, but the results of the calculation
have wrong exponent values - see example in the attachment. The mantissa values
are correct.
The program runs well and calculates correct in native windows or in a vm
guest.
--
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.
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.
http://bugs.winehq.org/show_bug.cgi?id=58344
Bug ID: 58344
Summary: Magic The Gathering Arena: Black screen in wine-10.9
Product: Wine
Version: 10.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: aguertin+wine(a)aguertin.net
Distribution: ---
Magic the Gathering Arena is showing a (mostly) black screen with no graphics,
starting in wine 10.9. The cursor is still shown, and hovering over where UI
elements should be plays the expected audio.
The regressing commit is:
d0fd9e87cf6152fbf14889a044e5a56415b1172c is the first bad commit
commit d0fd9e87cf6152fbf14889a044e5a56415b1172c (HEAD)
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Mon May 19 16:54:51 2025 +0800
d3d11: Add ID3D11Device3 stub.
Before the main UI loads, there are two loading screens. One of them is also
displaying as completely black instead of the expected image and text, but the
other one does display correctly (it shows the words "Waiting for the server"
and a spinner).
System info:
Wine 10.8/10.9/git
mesa git
kernel 6.15.1
GPU AMD RX 9070
--
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.
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.
http://bugs.winehq.org/show_bug.cgi?id=58356
Bug ID: 58356
Summary: Doom I & II Enhanced (2019 re-release based on Unity
engine) crashes after the intro videos
Product: Wine
Version: 10.9
Hardware: x86-64
URL: https://store.steampowered.com/app/2280/DOOM__DOOM_II/
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: julliard(a)winehq.org
Regression SHA1: 9d05345d4419aa29e6d4b15456bfeab510d39823
Distribution: ArchLinux
Created attachment 78744
--> http://bugs.winehq.org/attachment.cgi?id=78744
terminal output
Doom I and Doom II Enhanced (2019) crash after playing the intro videos, before
the main menu could be displayed.
The crash occurs due to
commit 9d05345d4419aa29e6d4b15456bfeab510d39823
msvcrt: Define C++ type info using RVAs for PE builds.
I'm on Arch and using gcc-15 and mingw-15.1.0 to compile Wine.
The crash happens both in the new and old WOW64 modes, regardless if I compile
Wine with "-O2" or "-O0".
On Steam the game is available in the Doom + Doom II bundle, *but you have to
select "previous-re-rerelease" beta branch to obtain this specific version that
crashes.*
Still present in wine-10.9-214-g19441ac8046.
--
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.