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: No sound, only dummy output since updating alsa-lib to 1.2.14
Date: Sat,  6 Sep 2025 11:55:58 +0200 (CEST)	[thread overview]
Message-ID: <1862a8f06614cc00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <1862a8f0602d8900-webhooks-bot@alsa-project.org>

alsa-project/alsa-lib issue #475 was opened from aaaaadrien:

Hello,

Since an update on Fedora Linux 42, Audio card not detected, GNOME only shows "Dummy Output".
No sound over speakers or HDMI.
I downgraded the package alsa-lib (from alsa-lib-0:1.2.14-3.fc42.x86_64 to alsa-lib-0:1.2.13-4.fc42.x86_64) and now i have sound again.
Tested with OpenSuse Tumbleweed Live ISO GNOME, with libasound2-1.2.14, i reproduce the issue.

So i think it's not a distro issue but an ALSA Issue. That's why i open a bug here.

Laptop model : Dell Latitude 3510
Audio Device : Intel Comet Lake PCH-LP cAVS
driver: sof-audio-pci-intel-cnl
API: ALSA 
version: k6.16.4-200.fc42.x86_64 
status: kernel-api

Reproducible: Always

Steps to Reproduce:
1. Update alsa-lib to 1.2.14-3.fc42.x86_64
2. Reboot
3. See you only have dummy output

Actual Results:
No sound

Expected Results:
Sound always here !

Additional Information:
Laptop model : Dell Latitude 3510
Audio Device : Intel Comet Lake PCH-LP cAVS
driver: sof-audio-pci-intel-cnl
API: ALSA 
version: k6.16.4-200.fc42.x86_64 
status: kernel-api

I opened a bug on Red Hat bugzilla yesterday but i enclose the link if you want to see the commands and checks i tested : https://bugzilla.redhat.com/show_bug.cgi?id=2393552

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

           reply	other threads:[~2025-09-06  9:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1862a8f0602d8900-webhooks-bot@alsa-project.org>]

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=1862a8f06614cc00-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.