[pulseaudio-discuss] pulseaudio 0.9.22

Colin Guthrie gmane at colin.guthr.ie
Thu Jul 21 15:30:32 PDT 2011

'Twas brillig, and Joel A Fernandes at 21/07/11 22:45 did gyre and gimble:
> Hi,
> I wanted to discuss my experience with pulseaudio 0.9.22 is on the
> latest angstrom and BeagleBoard images.
> I noticed in images built using both OE and another assembled by
> Narcissus that the permissions of root directory were not set
> properly, so I was getting a "/root does not belong" error message.
> chown'ing it fixed the problem.
> Then, when I start in session mode (both as root and regular user)
> Running in a session as: pulseaudio --start -DD
> W: main.c: This program is not intended to be run as root (unless
> --system is specified).
> E: module-gconf.c: Unable to read or parse data from client.
> E: module.c: Failed to load  module "module-gconf" (argument: ""):
> initialization failed.
> E: main.c: Module load failed.
> E: main.c: Failed to initialize daemon.

Perhaps try commenting out module-gconf? It's not essential for
operation - it just makes the settings set in paprefs work.

> Running in System mode.
> Loading module-udev-detect by editing /etc/system.pa, I get pulseaudio
> to open the sound devices and startup without problems:

Yeah we've fixed system.pa to use udev in git now :)

> W: main.c: Running in system mode, but --disallow-exit not set!
> W: main.c: Running in system mode, but --disallow-module-loading not set!
> N: main.c: Running in system mode, forcibly disabling SHM mode!
> N: main.c: Running in system mode, forcibly disabling exit idle time!
> W: main.c: OK, so you are running PA in system mode. Please note that
> you most likely shouldn't be doing that.
> W: main.c: If you do it nonetheless then it's your own fault if things
> don't work as expected.
> W: main.c: Please read
> http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an
> explanation why system mode is usually a bad idea.
> But, "pactl list" gives a "Connection failed: Access Denied" message.

Debugging connection issues can be done with "PULSE_LOG=99 pactl stat"

One cause can be SSHing in from another machine running PA and using X11
forwarding which takes with it our xprop based network settings telling
libpulse to connect back to the source machine... or at least try to.
PULSE_LOG=99 helps debug exactly where it's trying to connect to.




Colin Guthrie

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

More information about the pulseaudio-discuss mailing list