Hi, I’m using up-to-date Tumbleweed. Nvidia card with Nouveau (which works better than the proprietary generally). The TV is my monitor and sound goes through the HDMI cable. However, after waking up from suspend, I get no sound again unless I log out and log in. Not even restarting pipewire works, at least not the commands I saw listed here. I saw other posts in this forum but they’re from way back when, before pipewire and stuff. Any idea how to fix it, or where to report it as a bug if it can’t be fixed? (KDE, or the kernel, or…?)
Perhaps try a more comprehensive command that restarts both PipeWire and its session manager, WirePlumber . Try this:
systemctl --user restart wireplumber pipewire pipewire-pulse
I have not tested this myself (as I do not have your issue) so I do not know if it will work.
Chances are that the HDMI port is on the Nvidia chip and that doesn’t properly suspend and resume. Please post the result of inxi -GCSzso we can better understand what is in your system.
Guys, I figured out what happens in more detail: it’s not exactly from suspend, it’s when I turn my TV off and on again. And it can work again, it’s just that after turning the TV on again the settings change: before, when it was working, it was “Stereo digital HDMI” etc (my setup is in Portuguese but it’s something like that); afterward it’s changed to “Pro Audio”, and it doesn’t work until I set it back to the HDMI setting.
So I guess it’s not exactly something to do with pipewire but with the settings themselves… At this point I think it’s a KDE Bug? Anything I could try first?
@OrsoBruno here’s the output of the command, by the way; and yes, the HDMI cable is connected to the card.
System:
Kernel: 6.15.8-1-default arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.4.3 Distro: openSUSE Tumbleweed 20250727
CPU:
Info: 6-core model: AMD Ryzen 5 3500X bits: 64 type: MCP cache: L2: 3 MiB
Speed (MHz): avg: 1763 min/max: 571/4121 cores: 1: 1763 2: 1763 3: 1763
4: 1763 5: 1763 6: 1763
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] driver: nouveau v: kernel
Device-2: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo
type: USB
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
dri: nouveau gpu: nouveau resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: nouveau,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 25.1.6 renderer: NV106
API: Vulkan v: 1.4.321 drivers: N/A surfaces: N/A
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
From your last description I’m not sure it is even a bug? We can rule out an Nvidia resume issue (apparently video works once you switch the TV on again?).
When no HDMI active connection is found the audio system switches to a default sink, or just the first one still active, and then doesn’t switch back automatically to the HDMI sink, but that HDMI audio is still recognized and selectable manually.
That might be a legitimate behavior (don’t automatically switch to whatever connector is plugged in but let the user choose) and I think I witnessed something similar but cannot check ATM.
I’m not a regular user of KDE or AMD HW, so cannot elaborate further; maybe others know if there is a config somewhere to change the default behavior.
Hmm I get what you’re saying. It is rational for it to change the setting since the HDMI connection is no longer available. However, since I have no other audio output, once HDMI audio is available again it should change automatically, I think? But I understand this is more of a feature request, at least in terms of KDE’s sound settings.
If CLI pipewire allows it, I’ll try and chatgpt-fu some sort of script for reselecting the appropriate audio device/profile once the TV is turned back on. Thanks a lot for the attention and help, and sorry for the false alarm!
You have no other audio (physical?) output, but the system thinks that something called “Pro Audio” is active.
You may try inxi -Aaz and pw-top and possibly install helvum and look if anything named “Pro Audio” shows up.
Yep, no other audio output. No cable, no bluetooth. And absolutely no sound if I play anything. I don’t know what that’s about, always thought it was some sort of placeholder for the audio jacks.
Wait are you saying that if I get rid of this Pro Audio thing I should get it switched to HDMI automatically once the TV turns on, since it would go from no audio sink to one (and then the system would assume I’d want that, and change)?
So, I figured out some important details that might help others in the future. I still wonder if there’s anything actionable here though in terms of bug reporting or feature requesting.
Doing things in the right order
Here’s what happens: when I leave the computer for a while, I suspend it and turn the TV off.
In my experience, at least, there is no way to suspend the computer once the screen is off. So, I always must first suspend and then turn the TV off.
Here’s the kicker: if, upon returning to the PC, I first wake the computer and then turn on the TV, the TV says that the connection is DVI, not HDMI. This explains why KDE’s config settings won’t show there’s an HDMI setting at all for this output device; I suspect no DE’s settings would. Pavucontrol does show there’s an HDMI setting, but it shows as unplugged / unavailable.
In my testing, the only way to restore proper audio settings is doing things in this order:
- Suspend the PC
- Turn TV off
- Turn TV on
- Wake the PC
This ensures HDMI device is chosen and it’s set correctly. I can play audio right away, immediately after the screen is on.
Resetting the device if TV is turned off with the PC on
If I turn the TV off and on without suspending the PC first, it will disable the HDMI device but won’t re-enable it afterward. I have to manually go to sound settings, re-enable the device, and re-set it to HDMI output (instead of “Pro audio”).
Can one recover from the DVI thing?
I haven’t tested if, after botching the setup by doing things in the “wrong” order, I can set it up correctly again by doing things in the right order. If I recall correctly only logging out of the session and in again (or rebooting, of course) would make things right, likely because wayland is restarted (?) and perhaps the TV recognises an HDMI connection again? I don’t know.
Is this a bug?
I also do not know if this is supposed to happen this way; my guess is that it’s not. Even then, I don’t know if it’s a problem with my hdmi cable, an Nvidia card problem, a Nouveau problem, a kernel issue, or a pipewire issue. If anyone thinks this is worth investigating further let me know, I can do some more digging.
I’ll keep checking if doing things in the right order will always get me good results, or maybe I was just lucky. Conversely, I just tried reproducing the wrong order thing and… audio config worked this time. I’m guessing there needs to be some time between events (e.g. the TV has to be off for some time) for this issue to emerge.
1 Like
Quick update: after resuming / turning the TV on in the wrong order, if you redo the whole thing in the right order TV recognises an HDMI connection and everything works again.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.