Bug#808894: pulseaudio: No sound output to headphones even though headphones are detected and pavucontrol shows output.

[Felipe Sateler]

On 7 January 2016 at 09:31, Jerad Simpson <jbsimpson at gmail.com> wrote:
>
> I ran into this issue with the version of pulseaudio in stable and
> solved it last night, but my circumstances may be different, and are
> unsupported by upstream.
>
> Let me explain my fix and my use case, in order to seek advice here
> and/or upstream.
>
> Firstly, I use the unsupported system-instance, as can be seen in my
> /etc/pulse/daemon.conf:
>
> daemonize = yes
> allow-module-loading = no
> allow-exit = no
> system-instance = yes
>
> After some poking around, I appended the following two lines to
> /etc/pulse/system.pa:
>
> ### Switch to headphones on connect
> load-module module-switch-on-port-available
>
> Follow this up with a 'sudo systemctl restart pulseaudio.service'

Unfortunately, this is not the same cause as the other reporter, since
the attached files do load module-switch-on-connect and it is not
using system mode.

>
> A lot of guides elsewhere will tell you that system-instance is
> insecure, and should be avoided.  I use this anyway, because I could not
> come up with a better solution for my use case.
>
> I am the only user of my laptop, however, I do have have other users
> that I 'su' to, and I want those users to be able to also play audio.
> With the system-instance on, and the users in the 'pulse' group,
> everything now works as expected.  With this post, I am soliciting
> advice on how I can make this work with per-user sessions, because I
> previously had no luck there.

On this one you might get better luck asking upstream. I only note
that system mode is not as unsupported as it seems. I think upstream
needs to clear up a bit their messaging. So, it is not a problem to
use system mode.


-- 

Saludos,
Felipe Sateler