Proper PulseAudio installation for KUbuntu 10.4

[Reinhold Rumberger]

On Friday 25 June 2010, Ric Moore wrote:
> On Fri, 2010-06-25 at 05:39 +0200, Reinhold Rumberger wrote:
> > On Friday 25 June 2010, Ric Moore wrote:
> > > Forgive me for being dense, but the comment made which I was
> > > replying to was that it would "be fixed in Maverick", which I
> > > assume is the next release?? Ergo, would it not be fixed for
> > > the LTS release which is Lucid?
> > 
> > It's not supported in Lucid, so it's unlikely to be fixed there,
> > especially since it is an LTS release. Attempting to fix it
> > would introduce more instability.
> > It is, apparently, supported in Maverick, so I'd expect it to be
> > fixed there.
> > 
> > > One thing is for sure, you cannot remove all of the pulseaudio
> > > packages without major breakage to the system, so that leads
> > > me to believe that there is a measure of support for pulse
> > > within the Kubuntu scheme of things, especially if you cannot
> > > remove it.
> > 
> > I can remove everything but two libraries that kmix depends on,
> > and they don't seem to interfere with anything...
> > 
> > > It would suit me just fine to remove it completely and rely on
> > > alsa totally. But, as I just mentioned, that apparently is not
> > > the case. Anyone else want some of this? I suggest it be
> > > totally fixed or totally removed. Let's hear it from the
> > > choir. :) Ric
> > 
> > There shouldn't be a problem with removing the sound daemon, and
> > that's the active part. Remove that, and your applications will
> > be forced to use alsa or whatever. If you can't remove it, I'd
> > like to know the package that depends on PA in such a way that
> > it can't be removed...
> 
> Removing libpulse0 would also remove a pile of KDE packages.

I'm not talking about that lib. To be exact, if you had read my 
previous mail properly, you might have noticed that I mentioned the 
only component that matters is the server component...
Leaving that library just wastes some space and doesn't really do 
anything else.

> Why
> would akonadi-kde-resource-googledata depend on libpulse0? Or
> Kaddressbook?

They don't. They indirectly depend on kmix, which in turn depends on 
libpulse0 and libpulse-mainloop-glib0.

> I really want to know. I've been using Linux since
> the days of the 11 floppy install. When I see such humongous
> depends, I have to believe that someone, who knows better than
> me, has ordained that the package remain for some reason. Then
> the package causes breakages and simple minded folks like me go
> nutz.

Those two libs don't cause breakage. They're just sitting around 
uselessly.

<snip> 

> To me and what a quick google search told me, LTS means support
> for 3 years. What I'm reading here is that within less than 6
> months pulse issues with KDE will be remedied, but to get those
> remedies one would have to abandon LTS security and upgrade to a
> version supported far less? It boggles my mind that it would be
> expected for users to accept that. Maybe I should just STFU, but
> I really want STABLE for development work and not live the life
> of the perpetual beta tester, like the Fedora Users are. Ric

You pretty much have two choices:
 a) Use Lucid the LTS and forget about pulse.
 b) Use Maverick and be able to use pulse.

If you absolutely need pulse you're going to have to go with option 
b, otherwise there is nothing stopping you from using Lucid with 
alsa.

  --Reinhold