Hi Paul,

Thanks for your email.

On Thu, Jul 7, 2011 at 2:00 AM, Paul Menzel
<paulepan...@users.sourceforge.net> wrote:
> Dear Joel,
>
>
> Am Donnerstag, den 07.07.2011, 00:38 -0500 schrieb Joel A Fernandes:
>> * Pulseaudio running as per-user is opening audio devices and blocking 
>> everyone else from getting access
>>   to the device. The problem is it doesn't even seem to be allowing 
>> applications to connect to it, this
>>   patch starts it up in system mode instead which is tested and known to work
>
> thank you for the patch. Could you post your error and check with the
> PulseAudio guys what the cause is? There are very responsive on their
> mailing list, which moved to freedesktop.org recently.

Sure, I will follow up with the pulseaudio folks.

>
> As far as I understood system mode can sometimes be the right thing to
> do but most of the time it is just a configuration error. Running PA and
> printing out the debug messages should give you a clue.

Pulseaudio isn't printing any debug messages to syslog or stdout ( -vv
-log-level pulseaudio options )

Here was the thread on BeagleBoard mailing list that discusses this issue:
http://groups.google.com/group/beagleboard/browse_thread/thread/4dc82483a8d000fb/ccbd0e21fa5e89a0

I will post the details of the problem on the pulseaudio mailing list
and try to get some other alternatives.

For now, can we temporarily merge this patch while I followup with them?

> Is that needed? It is an unexpected change for the user having to find
> out that s/he has to make a program under `/usr/bin/` executable to run
> it.

Do you have any suggestions on else we could do it? A patch that rm's
the script?

thanks
Joel

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Reply via email to