[pulseaudio-tickets] [PulseAudio] #720: No audio in E17-compiz
PulseAudio
trac-noreply at tango.0pointer.de
Mon Nov 16 01:36:58 PST 2009
#720: No audio in E17-compiz
-----------------------+----------------------------------------------------
Reporter: Vincente | Owner: lennart
Type: defect | Status: new
Milestone: | Component: daemon
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment(by coling):
Replying to [ticket:720 Vincente]:
> I cannot understand how a program can be so ill-thought out and flawed.
Good way to start a post asking for support!
99.99% of the time, sound problems with PA result from a poorly configured
default system. Distros have traditionally done a pretty poor job at
integrating PA and Ubuntu is probably the worst offender, but are
thankfully beginning to improve.
I'd suggest you try a live CD from other distros to see if the problem
will be the same there. As the person responsible for sound integration on
Mandriva and as a release has just been made, I can only recommend trying
a "Mandriva One" flavour of your choice:
http://torrent.mandriva.com/public/2010.0/
Failing that, the general order of things is:
1. Ensure that pure alsa is working: {{{pasuspender -- aplay -Dhw:0,0
/usr/share/sounds/startup3.wav}}} If this doesn't work the problem is
unrelated to PulseAudio.
2. If ALSA works, then check the Output Devices tab in pavucontrol. If it
says "Dummy Output" or similar it means that another application is
hogging the sound device and PA cannot use it. You can find out which
application is hogging the device via {{{fuser /dev/dsp}}} and {{{fuser
/dev/snd/*}}} commands.
3. If your real sound card shows up in pavucontrol's Output Devices tab,
then check the "Configuration" tab and ensure the correct profile is used.
Lastly, the configuration and handling of ALSA mixers is a very tricky and
error prone business. Users almost always do not know what the various
sliders and controls in the ALSA mixers actually do and getting sound
working is usually a matter of tweaking everything and eventually getting
sound output! This is far from ideal and PA is trying to rationalise that
and hide everything from users, but due to the massive amount of different
hardware out there, we cannot cover all bases and need user feedback to
solve these problems and improve the situation for everyone. This is how
free software works and it's is expected of users who participate in the
free software ecosystem to provide this kind of feed back and appreciate
the development model without getting upset or angry.
So if the above does not help you, please provide the output from:
1. {{{pulseaudio -k; pulseaudio -vvvvv}}} (run as a single command and
you may have to repeat it a few times to get past the "PID file" error due
to the system trying to automatically respawn PA for you).
2. When PulseAudio is running the output from {{{pacmd ls}}}
--
Ticket URL: <http://pulseaudio.org/ticket/720#comment:1>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
More information about the pulseaudio-bugs
mailing list