Hello,
On 6/5/20 11:44 AM, Jaroslav Kysela wrote:
Dne 02. 06. 20 v 13:59 Jan Pokorny napsal(a):
Problem solved!
The solution was as simple as installing alsa-ucm package.
(Extra credit to Mark Pearson for pointing some recent changes
in that project out to me.)
Color me very embarrassed.
Perhaps the intention of keeping the package set minimal backfired
(EDIT: nope, nothing seems to be actively associated with that
package incl. opt-in ones), but frankly, have never needed this package,
not even heard about it before.
I wonder why there are no pointers anywhere, at least in alsa-info.sh
output that would perhaps make the case clear for the experts amongst
you. Or somewhere else, where it could be raised as a suggestion:
It appears as if you have a card/coded that relies on UCM for it
to be used to the full extent, and UCM does not appear to be
installed. Try installing that software, commonly packaged as
alsa-ucm. Having it up-to-date may also help.
[if not anything else, perhaps at least this makes it on-topic for
the list]
Perhaps even close relationship between alsa-utils and alsa-ucm,
on the suggests/recommends level or something like that?
On the whole it seems more enlightenment towards users is advisable,
on more than one front, mainly for the ignorants like me :-)
Thanks for this analysis. Please, create a Fedora bug for this for the
further analysis / fixes. The alsa-ucm is installed for the workstation
GUIs:
https://pagure.io/fedora-comps/blob/master/f/comps-f33.xml.in
See "Fedora Workstation", "LXDE Desktop", "LXQt Desktop" etc. All
depends on the "multimedia" package group which contains alsa-ucm.
Anyway, it's a distro problem, so move the discussion to the right place.
Yes, filed this wish to have actual functional dependencies more visible
at the distro _and_ deployment level against Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1846787
Thanks everyone for the inputs so far
--
Jan {poki)
