[pulseaudio-discuss] Hpw to start the pa server

Colin Guthrie gmane at colin.guthr.ie
Mon Apr 12 14:39:51 PDT 2010

'Twas brillig, and Gene Heskett at 12/04/10 20:29 did gyre and gimble:
> draksound, re-enabled, was on before by other means, and enabled user 
> switching.  No sound yet.
> pacmd.ls.out attached.

Hmm, what is strange here is that it shows no streams at all - e.g. no
sink inputs. To back this up, all the sinks are in a suspended state.

The volumes are all incredibly high - well over the 100% mark. How were
these volumes set? Most tools only allow volumes up to 150%.

FWIW, It's generally a bad idea to run PA on top of dmix.

It would be interesting to see the output of:
 pulseaudio -vvv
when a detection module is used - you seem to have disabled
module-udev-detect and manually configured your devices in these examples.

If possible, can you restore the auto detection (i.e. the default.pa as
shipped with the package) and provide the above output. (you may have to
run pulseaudio -k to kill the running PA daemon and if autospawning is
enabled, it may respawn again very quickly).

I'm not sure if this well help with the sound playing issue as this
seems to be failing at the first hurdle - in that it cannot connect. Can
you explain your user setup. Are you just logging directly as root, or
logging in as a regular user then trying to play sound? Do really simple
clients like: paplay /usr/share/sounds/startup3.wav work?




Colin Guthrie

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mandriva Linux Contributor [http://www.mandriva.com/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

More information about the pulseaudio-discuss mailing list