Manjaro is usually configured to use PulseAudio by default to allow multiple audio streams
to use the same audio device
If you set a package to play direct to an ALSA device it is likely to take exclusive control of the audio device
From your description I suspect you have Clementine using an ALSA device exclusively
so Audacious is not able to use the same device
and VLC cannot access the device via ALSA ‘default’ (PulseAudio) for the same reason
Data shows the systemd service for PulseAudio is running OK, but that may no longer be the case.
pulseaudio.service can fail if command pulseaudio -k is used instead of systemctl restart pulseaudio.service
ALSA data for playback devices shows onboard audio as:
card 1: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Subdevices: 1/1 indicates analog audio subdevice is available and active in ALSA
but I would expect it to show as 0/1 (unavailable/active) if PulseAudio was active and accepting an output stream connection from PulseAudio
It is common to see HDMI as first audio device, to allow it to retain default device status
so audio streams revert to fallback device if HDMI is unplugged disconnects
and streams reconnect to HDMI when it is plugged in and available
Onboard audio cannot be completely unplugged in the same way and does not need
to be first on the ALSA device list
If HDMI audio is not supported or not wanted, usually just need to set the PulseAudio Profile to Off and PulseAudio will use the available output sink as default
I suggest you run
sudo alsactl nrestore
to rescan audio devices
with root access to rewrite ALSA settings file /var/lib/alsa/asound.state it should be able to update ALSA configuration to include any changes from update packages