The verification of the Stable Release Update for studio-controls has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- 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 Released 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
