Closed alexhaydock closed 6 months ago
I'm going to close this one because it seems like, bizarrely, it might have somehow fixed itself without me doing anything. I have no idea how. I was doing a lot of testing of HDMI/DisplayPort audio and the inbuilt audio device came back. I wonder if I have a bad config somewhere that got rewritten and fixed while I was testing things.
If I work out what I did to trigger this I will re-open it and add more info.
This issue tracker is intended only for Silverblue specific issues. We would like to ask you to try to reproduce the issue on a relevant Fedora Workstation release. If you will be able to reproduce there, then please report it in Red Hat Bugzilla (see How to file a bug) or in upstream (preferred for GNOME projects) and not in this issue tracker.
Describe the bug When rebasing to Silverblue 40 on an 11th Gen Framework laptop, no audio output devices are found by the system. This applies to the internal speakers, but audio out via HDMI/DisplayPort and Bluetooth still work fine. The mic also seems to work fine.
To Reproduce Please describe the steps needed to reproduce the bug:
sudo rpm-ostree rebase fedora:fedora/40/x86_64/silverblue
Expected behavior Audio output works appropriately.
Rebasing back to Silverblue 39 causes the audio device to return appropriately.
Screenshots
OS version:
Additional context
Images tried
I've also tried directly rebasing to the following images:
but all work exactly as above. No audio devices are detected.
dmesg
I can't see anything in
dmesg
that indicates any issues with the audio devices themselves. In fact, they seem to show up:Not reproducible on Workstation 40
I cannot reproduce this issue on Fedora Workstation 40 by booting a Live USB, though I have not tried an actual install of Workstation 40 with corresponding package updates, so it's possible this issue has been introduced in a package update since the 40 Beta images were produced.
I haven't had a chance to compare the packageset of the Workstation 40 image with the Silverblue 40 container but I wonder if it's a case of missing packages or dependencies there.