On Fri, 2015-07-31 at 03:06 +0800, Yuqing Zhu wrote: > Pulseaudio is always started by autospawn, which is there is default process > in system, > it will start the pulseaudio daemon and the session is always exist, so > pulseaudio daemon will be closed. > > But in yocto, pulseaudio only can be started by boot up script, there is no > process to start the pulseaudio daemon. > But this patch remove the starting PA in script, then pulseaudio will be > started in yocto.
Sorry, I don't understand what you're trying to say in the commit message. The patch indicates that you're having trouble with starting PulseAudio. It looks like autospawning isn't working in your setup. The likely explanations for that are that either you have disabled autospawning, or you're trying to access PulseAudio as root. If you have disabled autospawning, then to be able to offer advice, I'd need to know why you have disabled it. If you're trying to access PulseAudio as root, then I suppose you're running a graphical session as root (start-pulseaudio-x11 is relevant for graphical sessions only). That doesn't work out of the box, because in multi-user environments running PulseAudio as root can easily cause trouble for other users, so autospawning is not allowed for root. If there are no regular users in the system, however, you can enable autospawning for root by adding "allow-autospawn-for-root = yes" to client.conf. The sato images use that option, see pulseaudio-client-conf-sato.bb. -- Tanu -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
