can't change volume with pipewire-pulse

[IdkeMint]

tried everything at this point, ditching everything, reinstalling, handbook, whatever info i could find, every utility to change audio, it goes back to defaults, sound is okay but my mic is soooooooo low that it can't pick up sounds until i shout

thehassle@void ~ $ pactl info Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 253 Tile Size: 65472 User Name: thehassle Host Name: void Server Name: PulseAudio (on PipeWire 1.4.2) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-0000_21_00.0.analog-stereo Default Source: alsa_input.pci-0000_21_00.0.analog-stereo Cookie: 479b:8faa

[RicardoKovd]

I have the same problem. This problem only occurs on the speakers that come with my laptop. I can change the volume by using a Bluetooth headset. But after I updated the kernel today, the problem became more serious. My system cannot use sound, alsa cannot be initialized correctly, and this message is always thrown into the log:

2025-06-11T05:27:13.05869 daemon.notice: Jun 11 13:27:13 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:13.05873 daemon.notice: Jun 11 13:27:13 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:14.06785 daemon.notice: Jun 11 13:27:14 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:14.06789 daemon.notice: Jun 11 13:27:14 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:15.07652 daemon.notice: Jun 11 13:27:15 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:15.07655 daemon.notice: Jun 11 13:27:15 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:16.08543 daemon.notice: Jun 11 13:27:16 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:16.08548 daemon.notice: Jun 11 13:27:16 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:17.09499 daemon.notice: Jun 11 13:27:17 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:17.09503 daemon.notice: Jun 11 13:27:17 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:18.10433 daemon.notice: Jun 11 13:27:18 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:18.10436 daemon.notice: Jun 11 13:27:18 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:19.11356 daemon.notice: Jun 11 13:27:19 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:19.11362 daemon.notice: Jun 11 13:27:19 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:19.11356 daemon.notice: Jun 11 13:27:19 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:19.11362 daemon.notice: Jun 11 13:27:19 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:19.11356 daemon.notice: Jun 11 13:27:19 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:19.11362 daemon.notice: Jun 11 13:27:19 alsa: Hardware is initialized using a generic method
c2025-06-11T05:27:20.12255 daemon.notice: Jun 11 13:27:20 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:20.12259 daemon.notice: Jun 11 13:27:20 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:20.12255 daemon.notice: Jun 11 13:27:20 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:20.12259 daemon.notice: Jun 11 13:27:20 alsa: Hardware is initialized using a generic method
2025-06-11T05:27:20.12255 daemon.notice: Jun 11 13:27:20 alsa: Found hardware: "acp" "" "" "" ""
2025-06-11T05:27:20.12259 daemon.notice: Jun 11 13:27:20 alsa: Hardware is initialized using a generic method

this is my xuname

$ xuname
Void 6.12.32_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFF

[ACR-Jeff]

I am not sure if this is related to your issue, Similar to yours, I had a lot of issues right after updating broke Xsessions via lightdm on my end, What fixed it for me while using lightdm, modify: /etc/lightdm/Xsession at the bottom replacing: exec $@ with: exec dbus-run-session $@ solved a ton of issues after updating such as networking through file manager to local server over sftp, volume controls via pulseaudio, pipewire and wireplumber was all solved right after this and restarting.

[github-actions[bot]]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

[oliwer]

bump