Hello Brian, or anyone else affected, Accepted studio-controls into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/studio- controls/2.3.1-0ubuntu2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: studio-controls (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to studio-controls in Ubuntu. https://bugs.launchpad.net/bugs/1969827 Title: Studio Controls doesn't actually switch to FFADO Status in studio-controls package in Ubuntu: Fix Committed Status in studio-controls source package in Jammy: Fix Committed Bug description: [Impact] * Users of Studio Controls, specifically Ubuntu Studio users using Firewire audio interfaces, are running into issues where using Studio Controls to switch to the FFADO driver as provided by libffado (as opposed to the ALSA firewire driver) are unable to do so. * The dropdown menu in Studio Controls that switches between the two is supposed to add a blacklist item into /etc/modprobe.d to blacklist the ALSA Firewire driver, which is in direct conflict with the FFADO driver required by some Firewire audio interfaces and must be blacklisted. Currently, this dropdown menu has no effect. * The uploaded package fixes this by refactoring the copying mechanism. This has already been fixed in a future release of Studio Controls. [Test Plan] * Launch Studio Controls * In the System Tweaks tab, switch "FireWire Module select (reboot to switch):) menu to "Use FFADO FireWire Modules" * Reboot * Login, launch Studio Controls * Notice FireWire Module Select is back on ALSA. * 'ls /etc/modprobe.d/' will not show 'blacklist-studio.conf' * Expected behavior: FireWire Module select should be on FFADO and 'blacklist-studio.conf' should exist in '/etc/modprobe.d/' [Where problems could occur] * Although great care has been taken to avoid this, the 'blacklist-studio.conf' file could get stuck and remain blacklisting ALSA firewire modules. If this does cause such a regression, a further upload will fix this. However, this is unlikely as it merely invokes code that was not being invoked before that already existed as this is merely correcting a regression. [Other Info] * Original Description: Choosing the drop-down to switch the FireWire module from ALSA to FFADO doesn't appear to actually do anything. No blacklist-studio.conf file ever gets created in /etc/modprobe.d. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: studio-controls 2.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30 Uname: Linux 5.15.0-24-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 21 20:07:06 2022 InstallationDate: Installed on 2022-04-20 (1 days ago) InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: studio-controls UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1969827/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
