Comment 14 for bug 60236

Hi Alex,

     Thank you for realizing what I was trying to say. I was actually saying that someone used some of the Firefox Alpha upstream code in the Ubuntu release. Since when I attempted to install the Alpha as a seperate installation it did indeed produce the same error.

To answer Johns comments I never said it would solve the problem, at least not for everyone. This is why I implicitly stated that persons atempting this should first try if this would work as a seperate installation in their /opt directory.

Lastly John my installation of upstream code did not break but rather fix a few Gecko apps. Including the Liferea Feed Reader. Which was not working under the Ubuntu code.

So what I am not saying is that upstream is the final solution. What I am saying is that by installing it I fixed a number of Gecko apps (many of which you said I would break) by installing the Firefox upstream version and offered it as a possible solution for now.

Truthfully told though this raises a number of questions:

What bugfixes were implemented ?

Even though it's officially 2.x how much of the code may be mangled with 3.x (albeit by overenthusiastic coders) ?

Can Ubuntu check the code to ensure it's clean ?
Maybe we can have a code audit ?

Bottom line is this John. This isn't the only post related to Firefox in this fashion. Alot of the other bug reports claiming similiar failures are also claiming the failure of related Gecko apps. So this needs to be addressed. While it is users have to find options and be allowed to return to a more usable environment while they wait.

I know it's not well taken but it is a valid point.

P.S.: If you want to see what I mean install seperate upstream versions of Firefox 2 and Firefox 3.0A in your /opt directory. I will put money on the latter crashes. Take a snapshot of the dump and compare it to what you see here.