i am currently using kubuntu 25.04
i’ve been using linux mint and had this dummy output in the sound settings, tried to figure out to fix that and failed (made a huge “mess” trying to set up the audio, all this mess over audio. but at least i had my timeshift snapshots).
now that i switched to kubuntu, i went into my sound settings and now my sound chips (intel lunar lake-M HD Audio Controller) are finally present thanks to KDE plasma. there’s no need to install pavucontrol but all i need to do is set up alsamixer to make the audio work. but it keeps muting after rebooting, the only way to turn on the audio after rebooting is opening up terminal and manually turn the sound by typing “sudo alsactl restore” which i find it weird because imagine having to listen to music or watching youtube and you have to use the terminal to manually activate the audio. (i’m new to linux and not that used to it)
i tried to do some methods to automatically restore the alsamixer setting like making systemd run this command after rebooting and it fails (i did the same thing on linux mint and it fails).
i still use timeshift and create snapshots in case i mess something up. (i used to reinstall an entire OS to fix things until i discovered timeshift)
what is going on here? could that be pipewire? could that be the kernels? could that my drivers or my fireware? what else could that be?
if you want me to show the details of my firmware, drivers, kernel, etc. through the terminal, let me know and tell me what needs to be solved.
i ran
$ systemctl status --user pipewire service
and got thisis there something else i can solve?
Looks fine to me. I don’t use KDE, but searching, it looks like KDE Plasma’s audio mixer is “plasma-pa”. The “pa” there will stand for “PulseAudio”, so at least at one point, it’ll have been based on PulseAudio. I dunno if it talks natively to Pipewire now.
kagis
https://old.reddit.com/r/kde/comments/v8hbyb/something_like_plasmapa_for_pipewire/
That was three years ago, so might be out of date, but at least then, it still used the PulseAudio API, so it may need pipewire-pulse to be active. In any event, I don’t think that it’d hurt to have pipewire-pulse.
I’d check and make sure that pipewire-pulse is active too, and if so, try using
plasma-pa
to have PipeWire set the volume to whatever it is that you want set to. I assume that once you’ve set a volume with PipeWire, PipeWire will handle restoring it next time you log in. It does on my system.