> > > > > I suspect that the "Front" volume and mute elements can be used to > > > control the line out without affecting the headphones. The problem is > > > that PulseAudio's alsa configuration assumes that the "Front" element > > > affects both line out and headphones (there's a comment saying that "on > > > some machines Front is actually a part of the Headphone path"). > > > > > > /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf > > > contains this: > > > > > > [Element Front] > > > switch = mute > > > volume = zero > > > > > > If you change that to > > > > > > [Element Front] > > > switch = off > > > volume = off > > > > > > does that fix the problem for you? > > > > > > > Indeed this fixes my problem, thanks! > > > > I'm a bit confused by the comment in the .conf file though. So, despite > > PA detecting the rear line out port exactly as it states, this "Element > > Front" is actually part of the headphones "paths"? that is rear line out > > is considered as part of "Element Front"? > > I'm not sure what you mean with your last question. The rear line out > isn't a "part" of the "Front" mixer element, it's the other way around. > You have two paths, headphones and line out. PulseAudio considers the > "Front" mixer element to be part of both paths, even though on your > machine it's only a part of the line out path. > > I'm not sure if we can fix this upstream. To me it would seem logical > for the kernel to promise that "Front" only refers to line out, and if > on some machine it also affects the headphone path, then that should be > considered a kernel bug, and the kernel should rename the element. > David, what do you think? > <a href="http://www.alsa-project.org/db/?f=d57c2c52e03841877dbb1dba005f9f1ebee43f58">http://www.alsa-project.org/db/?f=d57c2c52e03841877dbb1dba005f9f1ebee43f58</a> Dell inspiron 660s desktop with alc662 codecs have three jacks at rear panel which support surround 5.1 and front panel headphone Headphone and line out share "Front Playback Volume"