Well, as long as it gets fixed, I don't mind. It just seems to me that there are way too many regressions to use Pulse as default.

On Tue, Apr 22, 2008 at 8:01 PM, ski <skibrianski@gmail.com> wrote:
Jeremy LaCroix wrote:
> I wouldn't consider using nspluginwrapper on 32-bit a fix just yet, as even
> on a 64-bit install with nspluginwrapper, Flash crashes still brings down
> the entire Firefox instance.

I have never seen that. In all instances where flash crashed on me,
firefox was still responsive and fully functional except for the gray
boxes where flash content was supposed to be(but there might have been
more than one bug that got condensed into this one). There are other
reasons seperate from this bug for using nspluginwrapper or something
like it on 32-bit, namely that flash can run in a seperate process and
therefore utilize a different core, which is very handy when flash is
eating 100% cpu on something and you want to still browse the web.

> I think the only sensible solution is to
> include Pulse Audio, but don't turn it on by default, let the user turn on
> Pulse Audio if they want it. Pulse Audio is way too unstable and incomplete
> to even be considered for an LTS release.

Couldn't disagree more. We have a valid work around for 99% of users. A
LTS system is not a system that never gets updated -- this simply
remains a high priority bug until the Right Fix (tm) comes out. Besides,
removing pulse audio at this late stage of the game is going to
introduce way more breakage than leaving it as is.

--
firefox crashes on flash contents
https://bugs.launchpad.net/bugs/192888
You received this bug notification because you are a direct subscriber
of the bug.