This bug was fixed in the package ubuntustudio-default-settings -
24.04.26.6
---------------
ubuntustudio-default-settings (24.04.26.6) noble; urgency=medium
* Fix regression in 24.04.26.5 upgrade (LP: #2063899)
- dpkg-divert rename in wrong maintscript
-- Erich Eickmeyer <eeickme...@ubuntu.com> Sat, 31 Aug 2024 13:36:26
-0700
** Changed in: ubuntustudio-default-settings (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in ubuntustudio-installer package in Ubuntu:
Fix Released
Status in ubuntustudio-default-settings source package in Noble:
Fix Released
Status in ubuntustudio-installer source package in Noble:
Fix Released
Status in ubuntustudio-default-settings source package in Oracular:
Fix Released
Status in ubuntustudio-installer source package in Oracular:
Fix Released
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://launchpad.net/~ubuntustudio-bugs
More help : https://help.launchpad.net/ListHelp
