** Changed in: alsa-utils (Ubuntu)
Status: Incomplete => Triaged
** Changed in: alsa-utils (Ubuntu)
Importance: Undecided => Wishlist
** Summary changed:
- alsactl depends on X11
+ alsactl should ignore the pulse plugin
--
alsactl should ignore the pulse plugin
https://bugs.launchpad
Well, if there are no processes running with "pulse" in their name, I
ran "alsactl", and the error message mentions the contents of $HOME or
"failure to initiate an X11 connection" - I'm not sure how that's
"clearly" pulse to a normal person who's not familiar with every string
in libpulsecommon.so
Why would it rule it out? The error message is very clearly from pulse:
"Home directory /home/sauer not ours."
--
alsactl depends on X11
https://bugs.launchpad.net/bugs/557016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
So, if I kill pulseaudio on the system (which was previously running),
and if ssh isn't forwarding anything from my workstation, shouldn't that
rule pulse out?
sa...@hotrod:/var/lib/mythtv/videos$ sudo alsactl store
Home directory /home/sauer not ours.
sa...@hotrod:/var/lib/mythtv/videos$ sudo -i
This is highly unlikely to be an alsa-utils issue. Rather, at least one
end seems to be routed through the pulse plugin (configuration shipped
by the pulseaudio binary package). I suppose we could hack the alsactl
utility to also ignore pulse (i.e., what we do with amixer and
alsamixer).
** Change
