Hi Jaroslav,
it seems that the recent addition of HDA-Intel.conf in ucm2 caused a regression on our CI tests on KVM. Namely, when this UCM profile is used for a plain HD-audio device on KVM, the device remains muted as default at the fresh desktop start up. Without a UCM profile, PA properly unmutes and raises the volume, but with a profile, it won't.
When the volume was once saved in the pulse local config, it seems restored, though. The tested environment was KDE.
Could you take a look at it?
thanks,
Takashi
Dne 29. 09. 20 v 17:30 Takashi Iwai napsal(a):
Hi Jaroslav,
it seems that the recent addition of HDA-Intel.conf in ucm2 caused a regression on our CI tests on KVM. Namely, when this UCM profile is used for a plain HD-audio device on KVM, the device remains muted as default at the fresh desktop start up. Without a UCM profile, PA properly unmutes and raises the volume, but with a profile, it won't.
When the volume was once saved in the pulse local config, it seems restored, though. The tested environment was KDE.
Could you take a look at it?
Hi,
It seems that the '_boot' command succeed (no-op) in this case so the legacy configuration is skipped in 'alsactl init'. I'll give a look. Thank you for the report.
Jaroslav
participants (2)
-
Jaroslav Kysela -
Takashi Iwai