All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iorga, Cristian" <cristian.iorga@intel.com>
To: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: PulseAudio in Sato
Date: Wed, 22 Apr 2015 14:48:23 +0000	[thread overview]
Message-ID: <969F26A8BAB325438E7EB80D3C3134FB2F4B178B@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <55367179.8090800@linux.intel.com>

I guess that pulseaudio-client-conf-sato could be added to packagegroup-core-x11-sato or packagegroup-core-x11-sato-extended, so that the pulseaudio-client-conf-sato will get selected only for sato images.

-----Original Message-----
From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Tanu Kaskinen
Sent: Tuesday, April 21, 2015 6:49 PM
To: openembedded-core@lists.openembedded.org
Subject: [OE-core] PulseAudio in Sato

Hi,

I started the work to enable PulseAudio in Sato images (https://bugzilla.yoctoproject.org/show_bug.cgi?id=7517). The first problem I faced is that PulseAudio isn't starting automatically. When using PulseAudio in a graphical session, the normal way to start the server is to rely on autospawning, which means that when the first client tries to use PulseAudio, the server gets automatically started by libpulse. That's not working in Sato, because the graphical session runs as root in Sato, and autospawning is disabled when running as root. Why? 
Well, at least one reason for the disabling is that if the user runs some random stuff with sudo, starting another PulseAudio server in the background for root will likely mess up the audio in the user's main session when the two servers are trying to access the same hardware.

My first thought was that Sato should work more like a normal system, and not run the graphical session as root, but then I thought that there probably are embedded systems with graphics where it makes sense to run everything as root, so that's a valid use case to support. Therefore, it would make sense to modify PulseAudio so that it would allow autospawning for root. That should be configurable, however, and root autospawning should be enabled only on these everything-running-as-root systems.

I'm planning to add a new option to /etc/pulse/client.conf: 
"allow-autospawn-for-root". I'm not sure how to meet the goal of disabling that option by default, and enabling it in Sato. I think it could be done so that the default version of client.conf would be packaged in the main pulseaudio recipe, and then there would be a separate recipe, "pulseaudio-client-conf-sato", which would replace the default pulseaudio-client-conf package. (Currently client.conf is in the libpulse package, so it would have to be split off into its own package
first.) I don't know if this is the best way to do it, feedback would be very welcome.

--
Tanu
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


  reply	other threads:[~2015-04-22 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 15:49 PulseAudio in Sato Tanu Kaskinen
2015-04-22 14:48 ` Iorga, Cristian [this message]
2015-04-23  8:04 ` Burton, Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=969F26A8BAB325438E7EB80D3C3134FB2F4B178B@irsmsx105.ger.corp.intel.com \
    --to=cristian.iorga@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tanu.kaskinen@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.