https://bugs.winehq.org/show_bug.cgi?id=49036
Bug ID: 49036 Summary: Recent updates to Staging break compatibility with VST instruments in LMMS Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mr.lumberg@gmail.com Distribution: ---
System is Debian 10 with Staging 5.7. Recent updates to WINE through Debian repos have rendered virtual instrument plugins unable to load in LMMS 1.2.1 audio workstation. LMMS is an Appimage so I don't have terminal output to show.
https://bugs.winehq.org/show_bug.cgi?id=49036
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
WineHQ.org doesn't provide support for appimages.
Yet, someone might want to try to reproduce the issue with the standard windows version of the application: http://lmms.io/download#windows
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #2 from mr.lumberg@gmail.com --- (In reply to Olivier F. R. Dierick from comment #1)
Hello,
WineHQ.org doesn't provide support for appimages.
Yet, someone might want to try to reproduce the issue with the standard windows version of the application: http://lmms.io/download#windows
Regards.
Issue is not LMMS itself; VST plugins were working until I ran updates from Debian last night, which pushed out updates to winehq-staging, wine-staging, wine-staging-64, and wine-staging-i386:i386. These 4 packages were the only updates that were pushed out yesterday in Debian Stable that were available for my system.
https://bugs.winehq.org/show_bug.cgi?id=49036
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- Is this bug present in upstream (non-Staging) Wine?
(Please see https://wiki.winehq.org/Download if your distribution does not provide upstream Wine packages.)
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #4 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to mr.lumberg from comment #2)
Issue is not LMMS itself; VST plugins were working until I ran updates from Debian last night, which pushed out updates to winehq-staging, wine-staging, wine-staging-64, and wine-staging-i386:i386. These 4 packages were the only updates that were pushed out yesterday in Debian Stable that were available for my system.
Hello,
Yes, I understand that the issue is with the VST plugins loaded externally by the appimage.
I don't know how appimage works but you said that you can't get a terminal output out of the appimage.
I suppose that the appimage is self-contained and can't be modified, so you can't tell it to produce a terminal output.
Unless we can reproduce the issue without the appimage, the bug is invalid and you'll have to ask the appimage maintainers for support.
Using the Windows version of LMMS directly will allow to confirm if the issue is valid and get a terminal output for debugging.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #5 from mr.lumberg@gmail.com --- (In reply to Olivier F. R. Dierick from comment #1)
Hello,
WineHQ.org doesn't provide support for appimages.
Yet, someone might want to try to reproduce the issue with the standard windows version of the application: http://lmms.io/download#windows
Regards.
Issue is not LMMS itself; VST plugins were working until I ran updates from Debian last night, which pushed out updates to winehq-staging, wine-staging, wine-staging-64, and wine-staging-i386:i386. These 4 packages were the only updates that were pushed out yesterday in Debian Stable that were available for my system. (In reply to Zebediah Figura from comment #3)
Is this bug present in upstream (non-Staging) Wine?
(Please see https://wiki.winehq.org/Download if your distribution does not provide upstream Wine packages.)
I can confirm that it's not; a laptop with WINE Stable installed runs these plugins correctly. Feedback on the LMMS forum suggests similar.(In reply to Zebediah Figura from comment #3)
Is this bug present in upstream (non-Staging) Wine?
(Please see https://wiki.winehq.org/Download if your distribution does not provide upstream Wine packages.)
I can confirm that it does not. A laptop of mine using Stable loads them correctly, and feedback from the LMMS forum suggests same.
https://bugs.winehq.org/show_bug.cgi?id=49036
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair@hotmail.com Product|Wine |Wine-staging Component|-unknown |-unknown
--- Comment #6 from Zebediah Figura z.figura12@gmail.com --- Can the application be freely downloaded? Can you please provide instructions to reproduce the problem?
Failing that, can you please provide terminal output?
Performing a regression test between staging and upstream, while time-consuming, is a good way to help the bug get fixed quickly. See https://wiki.winehq.org/Wine-Staging#Reporting_and_debugging_bugs_against_Staging for details.
https://bugs.winehq.org/show_bug.cgi?id=49036
Paul Gofman pgofman@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |pgofman@codeweavers.com
--- Comment #7 from Paul Gofman pgofman@codeweavers.com --- (In reply to mr.lumberg from comment #5)
I can confirm that it's not; a laptop with WINE Stable installed runs these plugins correctly. Feedback on the LMMS forum suggests similar.(In reply to Zebediah Figura from comment #3)
Is this bug present in upstream (non-Staging) Wine?
(Please see https://wiki.winehq.org/Download if your distribution does not provide upstream Wine packages.)
I can confirm that it does not. A laptop of mine using Stable loads them correctly, and feedback from the LMMS forum suggests same.
You are mentioning Stable Wine version here, which is presumably 5.0. Does it work with Wine 5.7 development version?
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #8 from mr.lumberg@gmail.com --- Created attachment 67023 --> https://bugs.winehq.org/attachment.cgi?id=67023 Wine-Staging 5.7 error w/ LMMS/VST
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #9 from mr.lumberg@gmail.com --- (In reply to Olivier F. R. Dierick from comment #4)
(In reply to mr.lumberg from comment #2)
Issue is not LMMS itself; VST plugins were working until I ran updates from Debian last night, which pushed out updates to winehq-staging, wine-staging, wine-staging-64, and wine-staging-i386:i386. These 4 packages were the only updates that were pushed out yesterday in Debian Stable that were available for my system.
Hello,
Yes, I understand that the issue is with the VST plugins loaded externally by the appimage.
I don't know how appimage works but you said that you can't get a terminal output out of the appimage.
I suppose that the appimage is self-contained and can't be modified, so you can't tell it to produce a terminal output.
Unless we can reproduce the issue without the appimage, the bug is invalid and you'll have to ask the appimage maintainers for support.
Using the Windows version of LMMS directly will allow to confirm if the issue is valid and get a terminal output for debugging.
Regards.
I attempted to install LMMS 32-bit release for Windows, which was unsuccessful; please refer to attachment for text of error.
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #10 from mr.lumberg@gmail.com --- (In reply to Zebediah Figura from comment #6)
Can the application be freely downloaded? Can you please provide instructions to reproduce the problem?
Failing that, can you please provide terminal output?
Performing a regression test between staging and upstream, while time-consuming, is a good way to help the bug get fixed quickly. See https://wiki.winehq.org/Wine- Staging#Reporting_and_debugging_bugs_against_Staging for details.
Yes, it's freely available at https://lmms.io/download#linux. At the request of another I've attempted to install the Windows version using WINE and attached the error output.
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #11 from mr.lumberg@gmail.com --- (In reply to Paul Gofman from comment #7)
(In reply to mr.lumberg from comment #5)
I can confirm that it's not; a laptop with WINE Stable installed runs these plugins correctly. Feedback on the LMMS forum suggests similar.(In reply to Zebediah Figura from comment #3)
Is this bug present in upstream (non-Staging) Wine?
(Please see https://wiki.winehq.org/Download if your distribution does not provide upstream Wine packages.)
I can confirm that it does not. A laptop of mine using Stable loads them correctly, and feedback from the LMMS forum suggests same.
You are mentioning Stable Wine version here, which is presumably 5.0. Does it work with Wine 5.7 development version?
I've not attempted to use Development to install yet. My desktop has Staging installed, the Laptop has Stable.
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #12 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to mr.lumberg from comment #9)
I attempted to install LMMS 32-bit release for Windows, which was unsuccessful; please refer to attachment for text of error.
Hello,
--- quote from attachment --- wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. --- end quote ---
Looks like bug 49011. This is a regression in wine-devel/wine-staging 5.7. This may explain the issue with VST plugins too.
Please, downgrade wine-staging to 5.6 and retry.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49036
--- Comment #13 from mr.lumberg@gmail.com --- (In reply to Olivier F. R. Dierick from comment #12)
(In reply to mr.lumberg from comment #9)
I attempted to install LMMS 32-bit release for Windows, which was unsuccessful; please refer to attachment for text of error.
Hello,
--- quote from attachment --- wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. --- end quote ---
Looks like bug 49011. This is a regression in wine-devel/wine-staging 5.7. This may explain the issue with VST plugins too.
Please, downgrade wine-staging to 5.6 and retry.
Regards.
I purged 5.7 and reinstalled 5.6 from the cache about four hours ago, and I can confirm that is it working properly again.
https://bugs.winehq.org/show_bug.cgi?id=49036
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Wine Component|-unknown |wineserver Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
--- Comment #14 from Zebediah Figura z.figura12@gmail.com --- (In reply to mr.lumberg from comment #13)
I purged 5.7 and reinstalled 5.6 from the cache about four hours ago, and I can confirm that is it working properly again.
Okay, marking as a duplicate then. Thanks for testing.
*** This bug has been marked as a duplicate of bug 49011 ***
https://bugs.winehq.org/show_bug.cgi?id=49036
mr.lumberg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |FIXED
--- Comment #15 from mr.lumberg@gmail.com --- (In reply to Zebediah Figura from comment #14)
(In reply to mr.lumberg from comment #13)
I purged 5.7 and reinstalled 5.6 from the cache about four hours ago, and I can confirm that is it working properly again.
Okay, marking as a duplicate then. Thanks for testing.
*** This bug has been marked as a duplicate of bug 49011 ***
Happy to help.
https://bugs.winehq.org/show_bug.cgi?id=49036
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |DUPLICATE Status|RESOLVED |CLOSED
--- Comment #16 from Zebediah Figura z.figura12@gmail.com --- Please don't change the resolution from DUPLICATE; fixed status will be tracked at the corresponding bug.
*** This bug has been marked as a duplicate of bug 49011 ***