I tried lot’s of suggestions online, discovered it was a common issue in the past.
I have an AMD Ryzen 4800U laptop with I believe Realtek audio, not Intel.
Nothing I tried solved the issue. So I used TimeShift (phew!!) to go back to last week (4nov).
This solved it for me. I then created a backup of /etc/modprobe.d/alsa-base.conf and /etc/modprobe.d/blacklist.conf, performed the update, rebooted, again had the Dummy Output issue, copied those two backupped files to /etc/modprobe.d, rebooted: still had the Dummy Output issue
For now I restored with TimeShift again and I will not perform an update. Please let me know what information I can gather to figure out the root cause.
I tried 5.4 (something .42 or .52) and 5.8.18 (which I need for this machine as it is Ryzen 4000). No difference.
I don’t see related errors in boot.log or dmesg after a boot.
Those are the likely candidates … basically systemd or the alsa packages. Probably the latter.
It’s worth just test installing gnome-control-center first. Then install each package in turn until you find the culprit. You will need to reboot between each package install.
losing sound happened to me.
i was running mint.
and then ubuntu budgie.
happened in both.
i finally hooked up my monitor through hdmi, and it sees my graphics card output.
my monitor has an audio jack for my speakers.
so i’m good.
it’s not uncommon as stated and as i found out.
just glad for me my workaround worked.
I want to do that, but after installing gnome-control-center, nothing appears in my App overview. When I launch gnome-control-center from console window, it just opens Settings? And there is no new item in Settings…
Thanks I will try that but first want to figure out which package is the culprit here.
Yeah I totally misread his message as gnome-control-center is just one of them to test. I have now reduced it to being one (or more) of these: alsa-utils libasound2 libasound2-data
The rest installed fine and no issues after reboot. Will continue testing these three.
Afterwards you can use synaptic to pin the previous version of the package so that you can continue updating as normal but not upgrade the problem package until Canonical can issue a new release.
install the specific previous versions over the updated ones.
pin the packages : sudo apt-mark hold libasound2 libasound2-data
I didn’t know about the apt-mark hold command. Or how to install specific versions with aptname=versionnumber. Learning a lot via this Discourse. Thanks!
Is kind of amazing! I haven’t installed it yet, but it seems to be ideal for most people, in combination with TImeShift. I prefer ext4 because copying files and random read/writes are much faster compared to BTRFS. Until that changes, I will probably not use that autosnap tool, seems a bit much to create snapshots with rsync all the time (TimeShift-rsync once a week is enough for now). But still a very cool idea that he has developed.