> > > Sometimes pulseaudio is the cause..... > > > > $ apt-cache policy pulseaudio > > pulseaudio: > > Installed: (none) > > Candidate: 7.1-2 > > Version table: > > 7.1-2 500 > > 500 http://ftp.debian.org/debian unstable/main amd64 Packages > > What tells: > > dpkg -l | egrep "(alsa|libaso)"
$ dpkg -l | egrep "(alsa|libaso)" ii alsa-base 1.0.27+1 all dummy package to ease purging of obsolete conffiles ii alsa-oss 1.0.28-1 amd64 ALSA wrapper for OSS applications ii alsa-tools 1.1.0-1 amd64 Console based ALSA utilities for specific hardware ii alsa-tools-gui 1.1.0-1 amd64 GUI based ALSA utilities for specific hardware ii alsa-utils 1.1.0-2 amd64 Utilities for configuring and using ALSA ii alsamixergui 0.9.0rc2-1-9.1 amd64 graphical soundcard mixer for ALSA soundcard driver ii gstreamer0.10-alsa:amd64 0.10.36-2 amd64 GStreamer plugin for ALSA ii libalsaplayer0 0.99.81-1+b1 amd64 alsaplayer plugin library ii libasound2:amd64 1.1.0-1 amd64 shared library for ALSA applications ii libasound2:i386 1.1.0-1 i386 shared library for ALSA applications ii libasound2-data 1.1.0-1 all Configuration files and profiles for ALSA drivers ii libasound2-dev:amd64 1.1.0-1 amd64 shared library for ALSA applications -- development files ii libasound2-plugins:amd64 1.1.0-1 amd64 ALSA library additional plugins > > > > Did they disable search engine indexing on those lists? I wasn't able to > > find much useful info for ALSA and this specific issue while searching. > > Also no posts over on those mailing lists turned up... > > Just ask on those lists ;-) Would've done that, but I wouldn't have wanted to be shunned for asking an oft-asked question, since you said this issue was answered multiple times before. > And please ask your searchengine on how > to use emailin mailing lists and learnwhat an email thread is. Exactly how do you think I got to post on alsa's bug report and alsa-user mailing lists? I asked a completely different question by the way. > > If I do that, I get no sound through the analog jack output. What probably > > happens is that the HDMI is used for sound output instead... Somebody at > > the ALSA user mailing list suggested me to use config #2 (from my first > > message in this bug report) just to set the default soundcard without > > setting dmix, but it didn't work... > > Just do as user: > > $ mv $HOME/.asoundrc $HOME/.asoundrc.save Don't have an ~/.asoundrc, so I'll assume I have to do that to /etc/asound.conf > $ cat <<EOF > $HOME/.asoundrc > defaults.pcm.!card PCH > defaults.ctl.!card PCH > EOF That's exactly the same as configuartion #2 that I've tried, and which didn't work... Read my initial message in this bug report, please. But I gave it a spin this time again, in case I messed up something last time (and I did, just not with ALSA). > > As root: > > # service alsa-utils restart That gives me: Failed to restart alsa-utils.service: Unit alsa-utils.service is masked. So I used this instead: # /etc/init.d/alsa-utils restart Which unfortunately didn't seem to change anything, so probably the command I issued didn't work. But after restarting, the sound was the same, but I found out what was causing all these issues: In VLC I've set up a custom device for audio output instead of "Default", and that seemed to hold the sound blocked to one app. After changing it back to "Default", everything works as expected (multiple sound sources, browser add-ons sounds work, WebM/HTML5 players have sound) This can be now closed as it's no longer a bug. The message about missing files led me to think that the ALSA package I got was broken, thus the bug report.