[Ubuntustudio-bugs] [Bug 2061858] [NEW] Dummy audio device running on new installs
Public bug reported: It has been found on new installs that, despite attempt to disable via debian/postinst, that the dummy audio device is running. This is due to a systemd service being enabled globally for all users. A solution is being worked on to override this via debian/rules. ** Affects: ubuntustudio-installer (Ubuntu) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu. https://bugs.launchpad.net/bugs/2061858 Title: Dummy audio device running on new installs Status in ubuntustudio-installer package in Ubuntu: Triaged Bug description: It has been found on new installs that, despite attempt to disable via debian/postinst, that the dummy audio device is running. This is due to a systemd service being enabled globally for all users. A solution is being worked on to override this via debian/rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2061858/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2063128] Re: Upgrade from mantic to noble shows a debconf prompt
This has never been a problem in previous upgrades, so something in jackd2 must've changed in the debian packaging. We don't maintain this in Ubuntu but rely on syncs from Debian. Furthermore, we usually force this in when upgrading, so I'm surprised this is even happening. Perhaps we can add it as a quirk for `ubuntu-release-upgrader` to help with? ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-nn-incoming ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to jackd2 in Ubuntu. Matching subscriptions: ubuntustudio-bugs: jackd2 https://bugs.launchpad.net/bugs/2063128 Title: Upgrade from mantic to noble shows a debconf prompt Status in jackd2 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Reproducer: * Run Ubuntu Studio Mantic in a VM * Run `do-release-upgrade -d` to upgrade it to Noble * After the package download phase, the packages upgrade starts, and you quickly get prompted by jackd2 asking `Enable realtime process priority?` This can be avoided with `export DEBIAN_FRONTEND=noninteractive`, that's why it didn't show up in the CI, but we can't expect users to rely on this. I've attached a screenshot of the prompt, that contains more details on what exactly is asked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2063128/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2061711] Re: lubuntu noble - full (inc. 3rd party) install is kinda slow
Hey Chris,
If this isn't something that can be fixed with code or with a package
update, and while I don't feel like it is something that *can't* be
fixed, I think the status needs to be "Opinion" because it's certainly
worthy of discussion.
** Changed in: calamares (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares in Ubuntu.
https://bugs.launchpad.net/bugs/2061711
Title:
lubuntu noble - full (inc. 3rd party) install is kinda slow
Status in calamares package in Ubuntu:
Opinion
Bug description:
This is NOT a bug that can be fixed with code.
At most a fix maybe a line in the release notes, that selecting all
3rd party software for inclusion can be SLOW IF you're using 3rd-
world, some aussie NBN or other older/slower internet connections (or
just infrastructure at canonical end anyway).
This report has been filed ONLY for timing purposes; so I can look,
and have record of how long install actually took (with calamares
running)...
A watched kettle always appears to take longer to boil... I was
sitting watching this install & for a long time is stayed at 90% with
slideshow repeating... I switched to show all messages and it didn't
scroll up for maybe 10 mins there either..
I actually CTRL+ALT+T and opened a terminal, made it full screen on
this boxes other display & `sudo apt install iotop` and let that
run... From there I could see downloads taking place (thru write) &
eventually notice `snap download` progress to next package (krita, kf5
etc)... but the installer window remained at 90%.. eventually 92%...
|
Many users may assume the installer is 'looping' or dead...
2024-04-16 - 02:17:35 (start of calamares)
2024-04-16 - 12:17:43 (calamares switched to local time I assume)
2024-04-16 - 12:48:06 (end calamares)
So ~thirty minutes to install, I didn't let it sit at any dialog..
just selected items & continued...
This box may not be quick... but I believe issue is mostly internet
speed & what is required to be downloaded.. something we can't do much
about it..
Is a release note worth including??
Could a end-user think the install has failed is looping, when in fact
it isn't
I don't see how we can change anything, as even viewing the messages
calamares provides I didn't see progress for near 10 mins... thus
why I opened terminal & starting watching progress via `iotop`
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: LXQt
Date: Tue Apr 16 12:48:16 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240415)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.28
calamares-settings-lubuntu 1:24.04.28
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2061711/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2063847] Re: Audacity hangs on launch if calf-plugins package is installed
There's an open Debian bug in regards to that (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063319), but that's a separate bug from this, though it would be justify to fix it as it affects this bug (as noted in that bug). ** Bug watch added: Debian Bug tracker #1063319 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063319 -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to audacity in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/2063847 Title: Audacity hangs on launch if calf-plugins package is installed Status in audacity package in Ubuntu: Invalid Status in calf package in Ubuntu: Triaged Bug description: Audacity hangs on launch when calf-plugins package is installed on system. It started to happen after I installed Easyeffects, and calf-plugins is a dependency of Easyeffects. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: audacity 3.4.2+dfsg-1build4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:33:02 2024 ExecutablePath: /usr/bin/audacity InstallationDate: Installed on 2024-04-08 (18 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) SourcePackage: audacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/2063847/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2063847] Re: Audacity hangs on launch if calf-plugins package is installed
That's fine, but I am working on an SRU (Stable Release Update) of EasyEffects since this is certainly a packaging error that I can fix (not my error, but I have a fairly big hammer). -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to audacity in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/2063847 Title: Audacity hangs on launch if calf-plugins package is installed Status in audacity package in Ubuntu: Invalid Status in calf package in Ubuntu: Triaged Bug description: Audacity hangs on launch when calf-plugins package is installed on system. It started to happen after I installed Easyeffects, and calf-plugins is a dependency of Easyeffects. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: audacity 3.4.2+dfsg-1build4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:33:02 2024 ExecutablePath: /usr/bin/audacity InstallationDate: Installed on 2024-04-08 (18 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) SourcePackage: audacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/2063847/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2063847] Re: Audacity hangs on launch if calf-plugins package is installed
Considering calf hasn't seen a proper release in 5 years, I'm not at all surprised. Only recently have we seen any development activity start back up from them, and I'm not entirely sure where it's going. My advise is to use lsp-plugins as opposed to calf-plugins for now. ** Also affects: calf (Ubuntu) Importance: Undecided Status: New ** Changed in: audacity (Ubuntu) Status: New => Invalid ** Changed in: calf (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to audacity in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs, Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/2063847 Title: Audacity hangs on launch if calf-plugins package is installed Status in audacity package in Ubuntu: Invalid Status in calf package in Ubuntu: Triaged Bug description: Audacity hangs on launch when calf-plugins package is installed on system. It started to happen after I installed Easyeffects, and calf-plugins is a dependency of Easyeffects. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: audacity 3.4.2+dfsg-1build4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:33:02 2024 ExecutablePath: /usr/bin/audacity InstallationDate: Installed on 2024-04-08 (18 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) SourcePackage: audacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/2063847/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2063899] [NEW] Dummy audio device running on new installs
Public bug reported: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. [Test Case] * Run Ardour * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio-audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). ** Affects: ubuntustudio-installer (Ubuntu) Importance: Undecided Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Attachment added: "Screenshot_20240426_163412.png" https://bugs.launchpad.net/bugs/2063899/+attachment/5771168/+files/Screenshot_20240426_163412.png -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: Dummy audio device running on new installs Status in ubuntustudio-installer package in Ubuntu: In Progress Bug description: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. [Test Case] * Run Ardour * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio- audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2063899/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
** Also affects: ubuntustudio-default-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: New => In Progress ** Changed in: ubuntustudio-default-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntustudio-default-settings (Ubuntu) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Description changed: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. + + Additionally, `ubuntustudio-default-settings` needs to add additional + configuations to /etc/adduser.conf so that new users are automatically + part of the audio group and provide the + /etc/security/limits.d/audio.conf file. In the meantime, having Audio + Configuration fix existing users is a good workaround. [Test Case] * Run Ardour * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio-audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). - [Other Information] What really needs to happen here is that `ubuntu-desktop-provision` or `subiquity` needs to add the initial user to the audio group, or at least provide the facility for Ubuntu Studio to configure the initial user to be added as such similar to how Ubiquity did. - - Additionally, `ubuntustudio-lowlatency-settings` (part of ubuntustudio- - default-settings) may need to add an `adduser` hook to add new users to - the audio group and provide the /etc/security/limits.d/audio.conf file. - In the meantime, having Audio Configuration fix existing users is a good - workaround. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio Status in ubuntu-desktop-provision: New Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in ubuntustudio-installer package in Ubuntu: In Progress Bug description: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. Additionally, `ubuntustudio-default-settings` needs to add additional configuations to /etc/adduser.conf so that new users are automatically part of the audio group and provide the /etc/security/limits.d/audio.conf file. In the meantime, having Audio Configuration fix existing users is a good workaround. [Test Case] * Run Ardour * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio- audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). [Other Information] What really needs to happen here is that `ubuntu-desktop-provision` or `subiquity` needs to add the initial user to the audio group, or at least provide the facility for Ubuntu Studio to configure the initial user to be added as such similar to how Ubiquity did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://laun
[Ubuntustudio-bugs] [Bug 2063899] Re: [SRU] Users are not initially configured properly
** Also affects: ubuntu-desktop-provision Importance: Undecided Status: New ** Summary changed: - [SRU] Users are not initially configured properly + [SRU] Users are not initially configured properly for audio in Ubuntu Studio ** Description changed: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. [Test Case] - * Run Ardour - * Ardour will complain about limited memory (see screenshot attached) + * Run Ardour + * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio-audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). + + + [Other Information] + + What really needs to happen here is that `ubuntu-desktop-provision` or + `subiquity` needs to add the initial user to the audio group, or at + least provide the facility for Ubuntu Studio to configure the initial + user to be added as such similar to how Ubiquity did. + + Additionally, `ubuntustudio-lowlatency-settings` (part of ubuntustudio- + default-settings) may need to add an `adduser` hook to add new users to + the audio group and provide the /etc/security/limits.d/audio.conf file. + In the meantime, having Audio Configuration fix existing users is a good + workaround. -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio Status in ubuntu-desktop-provision: New Status in ubuntustudio-installer package in Ubuntu: In Progress Bug description: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. [Test Case] * Run Ardour * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio- audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). [Other Information] What really needs to happen here is that `ubuntu-desktop-provision` or `subiquity` needs to add the initial user to the audio group, or at least provide the facility for Ubuntu Studio to configure the initial user to be added as such similar to how Ubiquity did. Additionally, `ubuntustudio-lowlatency-settings` (part of ubuntustudio-default-settings) may need to add an `adduser` hook to add new users to the audio group and provide the /etc/security/limits.d/audio.conf file. In the meantime, having Audio Configuration fix existing users is a good workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntustudio-bugs] [Bug 2064170] [NEW] [SRU] "Switch Configuration" menu selection inoperable
Public bug reported: [Impact] In Ubuntu Studio Audio Configuration, the "Switch Configuration" selection, which allows a user to switch between the (now considered deprecated) PulseAudio/JACK setup and the modern PipeWire setup, is completely inoperable due to a typographical error in the code. [Test Case] * Open Ubuntu Studio Audio Configuration * Click on "Switch Configuration", click "Continue" * User is not taken to next step, but repeated to main menu. This is not desired. [What could go wrong] This was due to the omission of the letter "n" when looking for a string returned by zenity. This is highly tested and the fix works as expected, if not perfectly, but maybe something else snuck-in. ** Affects: ubuntustudio-installer (Ubuntu) Importance: High Status: Triaged -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu. https://bugs.launchpad.net/bugs/2064170 Title: [SRU] "Switch Configuration" menu selection inoperable Status in ubuntustudio-installer package in Ubuntu: Triaged Bug description: [Impact] In Ubuntu Studio Audio Configuration, the "Switch Configuration" selection, which allows a user to switch between the (now considered deprecated) PulseAudio/JACK setup and the modern PipeWire setup, is completely inoperable due to a typographical error in the code. [Test Case] * Open Ubuntu Studio Audio Configuration * Click on "Switch Configuration", click "Continue" * User is not taken to next step, but repeated to main menu. This is not desired. [What could go wrong] This was due to the omission of the letter "n" when looking for a string returned by zenity. This is highly tested and the fix works as expected, if not perfectly, but maybe something else snuck-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2064170/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
