[pulseaudio-discuss] Pulseaudio module initialization failed...

[aji.kumar at accenture.com]

Hi Tanu,

> -----Original Message-----
> From: Tanu Kaskinen [mailto:tanu.kaskinen at intel.com]
> Sent: Thursday, April 25, 2013 1:06 PM
> To: Kumar, Aji
> Cc: pulseaudio-discuss at lists.freedesktop.org
> Subject: Re: [pulseaudio-discuss] Pulseaudio module initialization
> failed...
>
> On Wed, 2013-04-24 at 17:18 +0000, aji.kumar at accenture.com wrote:
> > Hi Tanu,
> >
> > -----Original Message-----
> > From: Tanu Kaskinen [mailto:tanu.kaskinen at intel.com]
> > Sent: Wednesday, April 24, 2013 7:37 PM
> > To: Kumar, Aji
> > Cc: pulseaudio-discuss at lists.freedesktop.org
> > Subject: Re: [pulseaudio-discuss] Pulseaudio module initialization
> failed...
> >
> > On Wed, 2013-04-24 at 13:48 +0000, aji.kumar at accenture.com wrote:
> > > Hi Tanu,
> > >
> > > Thanks.. please find it attached.
> >
> > Before each "Failed to load module" error there's this:
> >
> > D: [pulseaudio] sink-input.c: Assertion
> 'pa_format_info_to_sample_spec(data->format, &ss, &map) == 0' failed at
> pulsecore/sink-input.c:295, function pa_sink_input_new.
> >
> > That's a bug that probably has been fixed in more recent PulseAudio
> > versions.
> >
> > >>> I did try pulseaudio 3.0 but it was crashing when trying to load
> "module-alsa-card" so could you suggest a version or approach in which
> I can avoid the issues in both since I am looking for immediate
> solution.
> > >>>Can I take this file from 3.0 and try to integrate the fix into
> 2.1 version.
>
> First of all, would it be possible for you to configure your mail
> client
> to use "normal" quoting? That is, prefix each quoted line with "> ".
> The
> default Outlook quoting style makes it very hard to follow the
> discussion when not using the "top-posting" style (and most technical
> mailing lists, including this one, strongly discourage top-posting).
>
> So, PulseAudio 3.0 is crashing. Do you have any details about the
> crashes? A stack trace would be great.

This with initial analysis was looking similar to a discussion that I read involving you on a crash on Pandaboard ES regarding alsa-lib migration.
Will send the stack trace when I test it again, currently working on pulse 1.1 version.
>
> Backporting the relevant fixes from 3.0 to 2.1 should be possible. I
> don't know what the relevant fixes are, though. I wonder if this bug
> still exists in current code, because I didn't spot any promising
> commits after 2.1 with a quick look at the sink-input.c, format.c and
> module-loopback.c history:
>
> http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/src/pulsecore/sin
> k-input.c
> http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/src/pulse/format.
> c
> http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/src/modules/modul
> e-loopback.c

I did a quick search could not find exact mapping subject line in the above listed, links.

Currently testing version 1.1 by patching udev patch and getting a new error after I do Handsfree audio testing using Bluetooth.
"Failed to handle SIGBUS", and pulse stops running after this.

Please also tell the configure lines I should use for building pulse from source, currently I am using these line, please correct me if I am wrong!!

find . -name "Makefile.in" | xargs sed -i "s|(libdir)/@PACKAGE@|(libdir)/pulse|"
./configure --prefix=/usr   --sysconfdir=/etc  --localstatedir=/var  --libexecdir=/usr/lib  --with-module-dir=/usr/lib/pulse/modules --enable-alsa
make
make install

> Tanu
>
> ---------------------------------------------------------------------
 Intel Finland Oy
 Registered Address: PL 281, 00181 Helsinki
 Business Identity Code: 0357606 - 4
 Domiciled in Helsinki
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

______________________________________________________________________________________

www.accenture.com