worked fine before the last update a couple of weeks ago. My hdmi sound output is off when coming out of sleep. The hdmi option for digital stereo hdmi is not avail. However if i select pro, then the option shows back up and can be selected. Running pipewire. It is fine if i reboot. Any ideas?
Your title says why - don’t hibernate the system.
When a device is powered off - it needs to be reinitialised - waking up is not enough.
It was working fine until this last update. Thanks for your input. And it wasn’t hibernation. It was sleep which has worked fine for years. I wouldn’t think it is a kernel thing. Running 6.15. Was on 6.14
1 Like
Try reverting to kernel 6.12 (LTS) and report back whether or not the problem remains.
Think (or don’t think) only after you have ruled it out. 
Regards.
It might be possible to restart one or more pipewire/wireplumber services instead of rebooting system if they show errors after resuming from sleep
systemctl --user -l --no-pager status pipewire pipewire-pulse pipewire-jack wireplumber
1 Like
Sorry - quite often the terms sleep and hibernation is used for the same state (writing RAM to swap and poweroff) while suspend (s2idle) is the state where RAM is kept alive but everything else is powered down. I confuse myself sometimes.
In any case the devices need to reinitialised as they are powered down - but you are right - sometimes it work for an extended period and 
then it doesn’t.
I have long time ago accepted that Linux is fantastic but it has those quirks which annoys the 
out you.
The definition for systemd - excerpt from systemctl --help
sleep Put the system to sleep (through one of
the operations below)
suspend Suspend the system
hibernate Hibernate the system
hybrid-sleep Hibernate and suspend the system
suspend-then-hibernate Suspend the system, wake after a period of
time, and hibernate
Ended up writing a systemd timer that triggered on resume and it fixed the issue for now. hopefully the root cause gets fixed whatever it was. Also, to address something that bothered me with the replies, this has worked just fine for years. Only when the last major update did it break. I patched when i got back from vacation last week. I am in the middle of ddrescue of a blueray right now so i cannot reboot into 6.12 to check if kernel swap did it. However after looking at things, i am doubting that the kernel is at fault.