[arch-general] no sound coming from speakers after update
mysatyre at gmail.com
Sun Oct 9 21:39:13 EDT 2011
On Mon, Oct 10, 2011 at 3:25 AM, Madhurya Kakati <mkakati2805 at gmail.com> wrote:
> On Sunday, October 9, 2011, Martti Kühne wrote:
>> > The last entry in mpd.log is from 02 oct. I doubt that will help.
>> > when I try to start mpd I get this error,
>> > [papul at archlinux ~]$ sudo rc.d start mpd
>> > :: Starting Music Player Daemon
>> > [BUSY] /etc/rc.d/mpd: line 6: 9910 Aborted /usr/bin/mpd
>> > /etc/mpd.conf &>/dev/null
>> Usually I put in hashes ('#') into the /etc/rc.d/mpd script to check
>> what output there is destroyed. Could be useful.
> After adding '#' in /etc/rc.d/mpd here's what I get when I try to start it,
> [papul at archlinux ~]$ sudo rc.d start mpd
> :: Starting Music Player Daemon
> [BUSY] listen: bind to '0.0.0.0:6600' failed: Address already in use
> (continuing anyway, because binding to '[::]:6600' succeeded)
> output: No "audio_output" defined in config file
> output: Attempt to detect audio output device
> output: Attempting to detect a alsa audio device
> ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect:
> Connection refused
> alsa: Error opening default ALSA device: Connection refused
> output: Attempting to detect a oss audio device
> oss: Error opening OSS device "/dev/dsp": No such file or directory
> oss: Error opening OSS device "/dev/sound/dsp": No such file or directory
> output: Attempting to detect a pulse audio device
> mpd: src/output/pulse_output_plugin.c:400: pulse_output_wait_connection:
> Assertion `po->mainloop != ((void *)0)' failed.
> /etc/rc.d/mpd: line 6: 27833 Aborted /usr/bin/mpd
wow that fails for several reasons. you should:
1. configure alsa in mpd.conf, then mpd will be mixed over dmix (which
won't fix the actual problem)
2. make sure the user which runs mpd to the audio group
and figure out why both alsa and pulse would refuse the connection.
who (uid/gid) runs those, what other security mechanisms could stick
in between, like a too restrictively configured firewall etc.
oh and you should figure out if mpd is already running, or if this
config option is plain wrong that makes mpd try to "bind to
'0.0.0.0:6600' failed: Address already in use" ... sometimes mpd hangs
up and you have to kill it with SIGABRT / 6.
I'm just at a very similar issue a friend of mine is having with mpd
and jack. you should get those permissions right in the first place...
:) I'll go there and adjust /etc/group until it works, I guess.
More information about the arch-general