Comment 36 for bug 477513

I'm not sure why you're coming here asking for help (which is not our job, we are not http://support.mozilla.com) without being willing to accept our analysis.

If you'd like to learn about how debuggers work and how to read stack traces, I'll gladly give you lessons, however if you're going to act like an end user, then please do us the favor of trusting us.

It's rude to ask a doctor "please diagnose my problem" and when he says "you have the flu", say "oh, why should i believe you?"

Note that I've already provided instructions you can follow to analyze this for yourself. I'll repeat them because I'm feeling generous.

> To debug this further you will have to install symbols for:
> libgobject-2.0.so.0.2200.2
> im-uim.so
> libgtk-x11-2.0.so.0.1800.3

> (these should come from your "karmic" vendor)
> and then you should take the generated crash report (good luck) and report it
> in your "karmic" vendor's bug reporting system.

Please keep in mind, we're under no obligation, please read:
  https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

If you're willing to trust our documentation, you're free to read:
https://developer.mozilla.org/En/Debugging_Mozilla_on_Linux_FAQ

It's the google top hit for "Linux Debugging FAQ" and "Unix debugging faq" so perhaps it's trustworthy. OTOH, you're free not to trust our content.

Resolved: INVALID. Do not comment without a stack trace that includes debugging symbols for the crashing frames. Most likely you will be best able to achieve this by asking your vendor for support. However, this bug has more than enough information for you to do it yourself.