Starting firefox likely starts pulseaudio (since it's required for sound in the browser now). One downside to pulseaudio is that it doesn't share the soundcard across users without "extra" configuration. Normally pulse over the network type thing, even if "the network" is loopback / lo / 127.0.0.1.
If you're trying to do HDMI audio with just alsa, it's not likely to be ,0 in the hardware name.
$ egrep -r -i hdmi /proc/asound/*
$ speaker-test -c 2 -l 1 -D hw:0,3
Otherwise pavucontrol like many others have suggested. Pulse is quirky, sometimes you have to disable and re-enable a device to have it magically work. Even though it's the same system and setup you had working previously and technically nothing "changed".
|