All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: 1.2.16 upgrade: could not open configuration file
Date: Fri,  5 Jun 2026 17:55:14 +0200 (CEST)	[thread overview]
Message-ID: <18b63a660b12be00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18b63a660af36200-webhooks-bot@alsa-project.org>

alsa-project/alsa-lib issue #510 was opened from tekstryder:

After upgrading to the latest tagged release [v1.2.16](https://github.com/alsa-project/alsa-ucm-conf/releases/tag/v1.2.16), I'm seeing the following errors logged:

```
Jun 04 08:01:53 alsactl[721]: alsa-lib utils.c:372:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/USB-Audio/conf.d/0db0-1feb.conf
Jun 04 08:01:53 alsactl[721]: alsa-lib parser.c:79:(uc_mgr_config_load_file) failed to open file /usr/share/alsa/ucm2/USB-Audio/conf.d/0db0-1feb.conf: -2
Jun 04 08:06:02 pipewire[981]: ALSA lib utils.c:372:(uc_mgr_config_load_into) [error.ucm] could not open configuration file /usr/share/alsa/ucm2/USB-Audio/conf.d/0db0-1feb.conf
Jun 04 08:06:02 pipewire[981]: ALSA lib parser.c:79:(uc_mgr_config_load_file) [error.ucm] failed to open file /usr/share/alsa/ucm2/USB-Audio/conf.d/0db0-1feb.conf: -2
```

The device was integrated into `../ucm2/USB-Audio/USB-Audio.conf` long ago.

No such file should be searched for by the parser logic if the `/conf.d` path does not exist.

```
/usr/share/alsa ❯ grep -r 1feb      
ucm2/USB-Audio/USB-Audio.conf: # 0db0:1feb MSI Edge Wifi Z690
ucm2/USB-Audio/Realtek/ALC4080-HiFi.conf: Regex "USB(0b05:(1996|1a5[23c])|0db0:1feb)"
```

Never had a single issue with this device functionality since we first got it working in https://github.com/alsa-project/alsa-ucm-conf/issues/210 years ago.

https://github.com/alsa-project/alsa-ucm-conf/commit/1bb0739acfc9bbfe61ffaf4707ea9a9d98cdb82b seems responsible:

```
/usr/share/alsa ❯ grep conf.d /usr/share/alsa/ucm2/USB-Audio/USB-Audio.conf
# Optional configuration can be stored to USB-Audio/conf.d/{VENDOR}-{DEVICE}.conf files
File "/USB-Audio/conf.d/${var:USBID1}-${var:USBID2}.conf"
```

https://github.com/alsa-project/alsa-ucm-conf/blob/f846a8bba8fc2d21d23caf7eafab5f560f9196fa/ucm2/USB-Audio/USB-Audio.conf#L278-L281

Should check whether folder path `"/USB-Audio/conf.d/"` exists first.

This causes spurious log noise. The device audio is working as intended.

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/510
Repository URL: https://github.com/alsa-project/alsa-lib

       reply	other threads:[~2026-06-05 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18b63a660af36200-webhooks-bot@alsa-project.org>
2026-06-05 15:55 ` GitHub issues - opened [this message]
     [not found] <18b5f46a29504200-webhooks-bot@alsa-project.org>
2026-06-04 18:32 ` 1.2.16 upgrade: could not open configuration file GitHub issues - edited
     [not found] <18b5eeeb661b4700-webhooks-bot@alsa-project.org>
2026-06-04 16:52 ` GitHub issues - edited
     [not found] <18b5ed5cc3d66800-webhooks-bot@alsa-project.org>
2026-06-04 16:23 ` GitHub issues - edited
     [not found] <18b5eb03c3340700-webhooks-bot@alsa-project.org>
2026-06-04 15:40 ` GitHub issues - opened

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18b63a660b12be00-webhooks-bot@alsa-project.org \
    --to=github@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.