FireFox crashes routinely karmic i386 with uim

[Dave M G]

There were some other users reporting not being able to run Firefox at all in Karmic since it crashed so much.
Fix uploaded to Lucid with the patch from uim upstream: uim (1:1.5.6-0ubuntu3) lucid
Patch is also in debian uim in unstable (1.5.6-2)

TEST CASE: (waiting)
-----------------------
Binary package hint: firefox-3.5

I'm running FireFox 3.5.4 on Ubuntu 9.10. It is a fresh install on a new machine.

FireFox crashes routinely. It is not predictable in terms of time or number of pages. But it is guaranteed to crash if given enough time and activity.

I've had this problem almost continually with FireFox since at least version 3.0 on all my Ubuntu machines. I've reported bugs before, but was always told to create a clean, extension free profile. Which was a hassle, so I didn't bother.

Until now. Since I just installed Ubuntu and FireFox on a brand new machine, and discovered immediately that the crash problem was still here, I figured this was the time to make a definitive report.

I made a totally extension free profile and then just went around to random web sites. It crashed within a minute.

Because I ran it from the command line, I have all the command line output, which I'll share with you. It's attached in a text file to this bug report.

[Erik Kronberg (eakron)]

Please add computer information such as architecture (32 bit, 64 bit?) and memory (Firefox requiring alot of memory).

[Dave M G (martin-autotelic)]

Ubuntu

Release 9.10 (karmic)
Kernel Linux 2.6.31-14-generic

Hardware

Memory: 2.0GB
Processor 0: Inten(R) Core(TM)2 Quad CPU Q800 @ 2.66GHz
Processor 1: Inten(R) Core(TM)2 Quad CPU Q800 @ 2.66GHz
Processor 2: Inten(R) Core(TM)2 Quad CPU Q800 @ 2.66GHz
Processor 3: Inten(R) Core(TM)2 Quad CPU Q800 @ 2.66GHz

System Status

Available disk space: 286.3 GB

[Erik Kronberg (eakron)]

Please run "apport-collect 477513" (without the quotes). It will collect information for this bug report.

[Dave M G (martin-autotelic)]

Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.4+nobinonly-0ubuntu0.9.10.1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Dave M G (martin-autotelic)]

The new name for this bug is way more boring than my original name. But as long as it gets solved.

I don't have too much to add, except that on my laptop, which is running Xubuntu 9.10 and FireFox 3.5 is also just as crash-tastic. It has been crashing just as routinely as on my desktop for many months now, roughly since installing Xubuntu 9.04, though I can't be exactly sure.

In any case, the point is that FireFox is just as unstable on my laptop, and in the same way, as my Desktop.

One thing is new and different, though, and that's the error message my laptop gives me:

"Sorry, the program "firefox" closed unexpectedly
Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers."

Just thought I'd add that.

[Micah Gersten (micahg)]

Firefox 3.5.5 should be available tomorrow sometime, could you please try that and let us know if it's any better?

[Dave M G (martin-autotelic)]

I'd be happy to.

Are there any fixes that are specifically inspired by this bug, or is it just a general hope that update = better?

In any case, I'll report back here after updating as soon as I feel I can say definitively what, if anything, has changed.

Thanks for all the hard work!

[Dave M G (martin-autotelic)]

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5

On the advice of someone on Launchpad (The Ubuntu bug reporting site), I am cross posting this bug here.
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/477513

FireFox crashes routinely.

Reproducible: Always

Steps to Reproduce:
1. Open FireFox
2. Surf to various sites. That's all that's needed.

Actual Results:
FireFox will crash.

Expected Results:
FireFox should not crash.

Seems to be related to changing pages. If I stay on a site and don't navigate to too many pages, FireFox may stay alive for longer (though not guarunteed).

Surfing to many pages in a shorter period of time increases the likelihood of crashing sooner.

I can reliably crash FireFox in under a minute by randomly surfing without stopping to look too long at the content.

Please see the bug report on launchpad for crash output and further details.

[Dave M G (martin-autotelic)]

For some reason the Launchpad people made me change bug reports.

The new URL is here:

https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/481237

[Dave M G (martin-autotelic)]

Upgraded to FireFox 3.5.5, and the crashing problem has not improved.

After upgrading and rebooting, I opened my plugin-free profile, randomly went through a few web pages, and it crashed within a minute or so.

Attached is the output from the command line.

[Tyler Downer (tyler-downer)]

You seem to be using a ubuntu build of firefox. These are known to occasionally have their own bugs. Please try using a build from mozilla.com. Once you get one, if it still crashes, you can get a stacktrace, https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report

[Erik Kronberg (eakron)]

Thank you for reporting back on the new version. I know it's a hassle, but it would be a good idea to report it at Bugzilla too, the Mozilla (Firefox) bug tracker. Then you can link this bug report to that one.

[Dave M G (martin-autotelic)]

I've filed a bug report with Mozilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=528153

I hope this can be resolved soon, because FireFox is becoming frustrating to use.

I would have abandoned FireFox already were it not for the plug ins that I need to use.

[Micah Gersten (micahg)]

Thank you for reporting this to Ubuntu. Could you please generate an apport crash report for this?
You can enable apport for one instance like this:
sudo force_start=1 /etc/init.d/apport restart

I am marking this invalid as apport will open a new bug when the crash is generated. If it does not, you can reset the status of this one to New and we will try something else. Please note this bug # when you report the new one as well.

[Dave M G (martin-autotelic)]

Why mark this invalid and start a new bug report? Isn't that just making this more complicated than it needs to be?

Sorry, but I just feel like getting hung up on the bug reporting process and moving information around isn't adding anything to the process of actually solving the bug.

And in any case, the command you gave me doesn't work:

$ sudo force_start=1 /etc/init.d/apport restartsudo force_start=1 /etc/init.d/apport restart
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service apport restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart apport
start: Job failed to start

[Dave M G (martin-autotelic)]

Great, now that this bug is marked closed, the previous apport command won't work either.

apport-collect 477513
Logging into Launchpad... You have to allow "Change anything" privileges.
Downloading bug information...
Bug title: FireFox crashes routinely karmic i386
Ignoring task https://api.edge.launchpad.net/beta/ubuntu/+source/firefox-3.5 because it is closed
No additional information collected.

Way to put up barriers on the bug reporting there.

[Micah Gersten (micahg)]

@Dave M G

Please try this instead:
sudo force_start=1 service apport restart

Then reproduce the crash. I'm sorry, but without knowing why your browser is crashing, we can't fix it. The previous E-Mail did say to set the status of this bug back to 'New' if you had issues.

[Matti-mversen (matti-mversen)]

THe ubuntu build should be nearly identical to Mozila.org build. The crash reporter is only working in Mozilla.org builds, either use such a build or use the Ubuntu instructions in that link to provide a stack trace.

[Dave M G (martin-autotelic)]

I am trying to run the Apport command as instructed, but it comes back with this response before I can initiate a crash with FireFox:

$ sudo force_start=1 service apport restart
[sudo] password for dave:
restart: Unknown instance:

Oh, and the Mozilla guys said I should run their build and not the Ubuntu build. I'm not keen on that as a permanent solution, because I like FireFox updates being handled by the Update Manager.

However, I'll install their build for testing if anything can be gained from comparisons.

[Micah Gersten (micahg)]

The Mozilla Guys always say to try their build if they have no information so they can make sure it's a problem with Firefox and not our libraries.

Here, this command should work:
sudo force_start=1 service apport start

Please try that and reproduce the crash with our firefox.

I'll have to update the documentation for that command and I apologize for all the trouble.

[Dave M G (martin-autotelic)]

Sorry about being a bit snippy earlier. I was having one of those days.

I appreciate all the hard work you guys put into Ubuntu/FireFox.

Anyway, still no joy on the command:

$ sudo force_start=1 service apport start
start: Job failed to start

Am I doing something wrong? Does it matter if I start FireFox before or after the command? Am I missing a package or something?

[Dave M G (martin-autotelic)]

I tried downloading a build directly from the FireFox web site and running that.

It went for a while without crashing and I thought maybe it would hang tough.

But then it crashed as well. A bug report thing came up, but I'm not sure if it went to this site or not though.

So, anyway, looks like the bug might be FireFox related, not necessarily to do with the Ubuntu build.

[Timeless-bemail (timeless-bemail)]

https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report

[Dave M G (martin-autotelic)]

I sent two stacktrace reports from FireFox. But now that they are uploaded to this web site, I can't find them to link to them here.

So please don't just tell me I need to file this or that report. I'm trying to give you what you need to fix the bug.

[Tyler Downer (tyler-downer)]

Even though you have submitted the stacktraces, we get thousands of them every day. So, we have no idea which is yours. If you read the link it give instructions on how to go and grab the id so you can past it here.

[Dave M G (martin-autotelic)]

Yeah, so the instructions say:
"To access all of your submitted reports type "about:crashes" into the Firefox address bar and press enter"

So I type "about:crashes", without the quotes, into the Firefox address bar, and press enter, and it says:

"The URL is not valid and cannot be loaded."

So what now?

[Dave M G (martin-autotelic)]

Alright, I got the crash report IDs. I don't know what changed, but after crashing Firefox a couple more times, the "about:crashes" thing magically started working.

bp-b43b361f-87cb-411a-94ee-fb3432091116 09-11-16 11:49 PM
bp-716ba922-b40c-4770-b236-1dec12091116 09-11-16 11:48 PM
bp-b86b95d0-d8ee-4a95-a7d9-0e6e62091116 09-11-16 11:34 PM
bp-cce946ca-cd63-4e8a-b52b-6c36e2091115 09-11-16 12:16 AM
bp-db3ba632-519b-4222-a3d1-fa57b2091114 09-11-15 04:32 AM

[Timeless-bemail (timeless-bemail)]

Signature libgobject-2.0.so.0.2200.2@0x2909a
UUID b43b361f-87cb-411a-94ee-fb3432091116
Time 2009-11-16 06:49:15.93088
Uptime 23
Last Crash 65 seconds before submission
Product Firefox
Version 3.5.5
Build ID 20091102141836
Branch 1.9.1
OS Linux
OS Version 0.0.0 Linux 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 i686 GNU/Linux
CPU x86
CPU Info GenuineIntel family 13 model 23 stepping 10
Crash Reason SIGSEGV
Crash Address 0x9c209a
User Comments
Processor Notes
Related Bugs

Crashing Thread
Frame Module Signature [Expand] Source
0 libgobject-2.0.so.0.2200.2 libgobject-2.0.so.0.2200.2@0x2909a
1 im-uim.so im-uim.so@0x5f01
2 im-uim.so im-uim.so@0x6b34
3 im-uim.so im-uim.so@0x6c10
4 libgtk-x11-2.0.so.0.1800.3 libgtk-x11-2.0.so.0.1800.3@0x11c403
5 libgtk-x11-2.0.so.0.1800.3 libgtk-x11-2.0.so.0.1800.3@0x11c403
6 libxul.so nsWindow::IMESetFocus widget/src/gtk2/nsWindow.cpp:6418
7 libxul.so nsWindow::SetFocus widget/src/gtk2/nsWindow.cpp:1454
8 libxul.so nsGlobalWindow::Focus dom/src/base/nsGlobalWindow.cpp:4314

im-uim.so 8DF4E7F64B5A5088C8F022A809F835C80 im-uim.so

So, you have an input method of sorts. And it's crashing. I'm sorry that you have this software installed. Please file a bug against it.

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.

Alternatively, I'd suggest you find a way to disable im-uim, as I'm certain that the vast majority of our users aren't using it.

[Dave M G (martin-autotelic)]

I'm not sure I understand your claim that it is UIM that is crashing.

*Only* Firefox crashes. I use UIM/Anthy to switch input methods when I type in Japanese. I use UIM/Anthy in every software package I have where I type in text, and Firefox is the only software that crashes on my system.

Further, not once has Firefox crashed when I have been inputting Japanese. It has only ever happened when I open and close pages.

In fact, for the times that I have been testing the Firefox build that you recommended I download straight from you instead of from the Ubuntu repositories, I have never even typed anything in, at all, ever. I would open it, surf to random web sites until it crashed, and that's it.

If your claim is that the mere presence of UIM on my system is enough to cause Firefox to crash, regardless of whether or not I am actually using it, then I suppose that might be the case, as that would be consistent with my experience.

However, since UIM has no other problem with any other software, I think that puts the onus on Firefox to show why it has a problem, not UIM.

[Matti-mversen (matti-mversen)]

A stacktrace shows the last steps of an application before the application crashed and the first line in the stack trace is the position that crashed.
The stacktrace clearly shows that Firefox isn't the cause of the crash, it's either bug in libgobject-2.0.so.0.2200.2 (frame0) or more likely im-uim.so (frame1-3)

The last Firefox code is in frame6 and that means that Firefox code can not be the cause of the crash. Every Developer who knows C, C++ will confirm this.

BTW: I'm not a developer but I learned to parse Stack traces to find the right bugzilla products/components.

[Timeless-bemail (timeless-bemail)]

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.

[Dave M G (martin-autotelic)]

The Firefox guys are now saying that UIM is the problem. I'm skeptical of that, but if you guys can make sense of what they are saying, that might help:

https://bugzilla.mozilla.org/show_bug.cgi?id=528153

[Dave M G (martin-autotelic)]

You make a fair point and I'll tell you exactly why I am arguing your analysis.

I am a programmer and I do debugging as well, and I am not unfamiliar with the complexities of debugging. I know full well that just because a problem manifests down the line does not mean the problem was further up the code.

I am also fully aware that in situations where people are doing technical support for a lot of people, their first objective is to keep their inbox clear by finding someone else to blame.

You raise the analogy of a doctor. If I went to a doctor and I said my foot hurt, and he did some kind of scan of my body and said the problem was my hand, I would argue the point even though I am not a doctor.

You want me to go to the people who code UIM and say "I need to report a bug with your software that is not activated by actually interacting with your software in any way, does not manifest in any other software but Firefox, and only causes Firefox to crash when I'm using Firefox without touching any of your components".

I wouldn't blame them if they said "you know, I think your problem might be Firefox..."

[Matti-mversen (matti-mversen)]

We don't do support here, bugzilla is a place for the developers.
The difference between support and us is that the support tries to help if people have issues with software and it doesn't matter what caused the problem in the first place. In bugzilla we try to identify bugs in the code of our product and fix the bugs in the code.

Your crash is identified by 2 independent people as bug in im-uim.so and not in our code. Sorry if you are not happy with he resolution of this bug (invalid) but do not change it back.
- https://bugzilla.mozilla.org/page.cgi?id=etiquette.html -> point 2.2

>You want me to go to the people who code UIM and say "I need to report a bug
>with your software that is not activated by actually interacting with your
>software in any way, does not manifest in any other software but Firefox, and
>only causes Firefox to crash when I'm using Firefox without touching any of
>your components".

Sure that is expected by us, and you should post them the stack trace as argument and they should confirm the case.

And finally you can thrust timeless words more than my words. He is a very respected developer earns his money with developing software (not paid by Mozilla.org) and he analyzed and fixed hundreds of Gecko crashes in the past while I'm only a bug triager in bugzila for several (8+) years .

[Reed Loden (reed)]

Take bug 418073 for example... Firefox crashed, but the cause of the crash was clearly im-uim, so a fix upstream at the im-uim level was required.

[Micah Gersten (micahg)]

Debdiff for Lucid attached

[Micah Gersten (micahg)]

Forgot to mention, test build in my PPA:
https://edge.launchpad.net/~micahg/+archive/ftbfs-test/+packages

[Launchpad Janitor (janitor)]

This bug was fixed in the package uim - 1:1.5.6-0ubuntu3

---------------
uim (1:1.5.6-0ubuntu3) lucid; urgency=low

  * 08_uim_gtk_fix_bug_477513.dpatch: patch from upstream to fix firefox crash (LP: #477513)
 -- Micah Gersten <email address hidden> Mon, 23 Nov 2009 22:14:32 -0600

[Micah Gersten (micahg)]

Built fine in my PPA:
https://edge.launchpad.net/~micahg/+archive/ftbfs-test/+packages

[Micah Gersten (micahg)]

Fixed changelog entry to 80 character width.

[John Dong (jdong)]

ACK from MOTU-SRU for the debdiff, proceed to get it uploaded in Karmic.

However, at the same time, please revise the original description of the bug to include the information outlined in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

[Dave M G (martin-autotelic)]

(In reply to comment #21)

Fix confirmed!!

I was able to download the new UIM fix through a PPA repository offered by an Ubuntu developer, and I have been torture testing Firefox for the last hour or so. There was one freeze (probably because of the web site), but no crashes.

I ran Firefox from the command line, and there was no output whatsoever indicating any errors, which is completely different than what I was experiencing before.

I am confident enough in Firefox's performance now to say that for me the bug seems to be fixed, and Firefox is no longer unstable.

Thank you to everyone who helped to diagnose and fix the problem. Your hard work is much appreciated.

[Dave M G (martin-autotelic)]

Sorry, but I don't understand the process for a package to become available in the repositories. I keep seeing messages here on this bug report saying "fix released", but I haven't actually seen any fix.

Around when will UIM 1.5.7 be available for download?

I'm dying to be able to use Firefox without it crashing.

[Micah Gersten (micahg)]

@Dave M G

You can try the karmic package from my PPA with the patch for uim. Please let us know if this fixes the issue for you. Also, if you have steps to recreate the current crash, that would be helpful.
https://launchpad.net/~micahg/+archive/ftbfs-test/

[Dave M G (martin-autotelic)]

@Micah Gersten

I added your PPA for Karmic, and reloaded the repositories, but UIM does not show as being updated.

My currently installed version is 1:1.5.6-0ubuntu1.1, which is what it has been since the start of the bug report. I also notice that the version number in your PPA is 1:1.5.6-0ubuntu1.1.

Do I need to force a reinstall in order to update or change?

As for steps to recreate the crash, I don't know how to break it down any more than what I originally reported. All I need to do is use Firefox for a period of time, and it will crash. No one particular page does it or activity causes it, but use over time inevitably leads to a crash. The faster I change and load pages, the sooner the crash.

[Micah Gersten (micahg)]

@Dave M G

You were correct. I didn't notice the upload in proposed. I pushed a new version to my PPA which includes both patches. You should be able to update your package now. Thanks.

[Dave M G (martin-autotelic)]

Fix confirmed!!

I was able to download the new fix through the updated PPA, and I have been torture testing Firefox for the last hour or so. There was one freeze (probably because of the web site), but no crashes.

I ran Firefox from the command line, and there was no output whatsoever indicating any errors, which is completely different than what I was experiencing before.

I am confident enough in Firefox's performance now to say that for me the bug seems to be fixed, and Firefox is no longer unstable.

Thank you to everyone who helped to diagnose and fix the problem. Your hard work is much appreciated.

[Dave M G (martin-autotelic)]

Fix confirmed!!

I was able to download the new fix through a Debian package offered by an Ubuntu developer's PPA, and I have been torture testing Firefox for the last hour or so. There was one freeze (probably because of the web site), but no crashes.

I ran Firefox from the command line, and there was no output whatsoever indicating any errors, which is completely different than what I was experiencing before.

I am confident enough in Firefox's performance now to say that for me the bug seems to be fixed with the updated UIM, and Firefox is no longer unstable.

Thank you to everyone who helped to diagnose and fix the problem. Your hard work is much appreciated.

[Micah Gersten (micahg)]

Debdiff updated to uim_1.5.6-0ubuntu1.2 based on package currently in -proposed

[Fabrice Coutadeur (fabricesp)]

Uploaded to -proposed. Waiting for an archive admin ack.

[Scott Kitterman (kitterman)]

Accepted uim into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[grigori (gexi-deactivatedaccount)]

hmm, read the bug-report plus comments for the first time now. seem to have the same problem. i didn't bother because i couldn't find out what's causing the crashes or how to reproduce them. however, i've activated karmic-proposed and still have this problem.

well. after looking through the report and my configuration again, i found out that i haven't even installed this uim package. am i in the wrong bug report? 'cause it's the only one i found descibing my problem accurately.

i have a frequently crashing firefox (3.5.7~hg20091204r26644+nobionly-0ubuntu1~umd1~karmic) on an i386-karmic installation since changing from ff3 to ff3.5. that was on jaunty. i did a clean install of karmic in november, but the problem stayed the same.

[Micah Gersten (micahg)]

@grigori

Could you see if the uim package in -proposed fixes this for you? The comment about yours explains how to enable -proposed.

[grigori (gexi-deactivatedaccount)]

hi,

i installed uim from karmic-proposed yesterday. looks really good: no crashes so far. of course i had no time to really test it, primarily because of all the slightly alcoholic christmas-family-joy and blah, i'll keep you guys updated if anything changes. but thanks so far and merry christmas.

[grigori (gexi-deactivatedaccount)]

well,

unfortunately ff just crashed four or five times in a row. when starting from the terminal i get:

$ firefox
(firefox:3030): GLib-WARNING **: g_set_prgname() called multiple times
Segmentation fault

ff crashes with the segmentation fault error message.

[Micah Gersten (micahg)]

I'm guessing you have a different bug, could you please generate an
apport crash report for this?
You can enable apport for one instance like this:
sudo service apport start force_start=1

Then generate the crash again.
Please mention this bug number so that we can see if it's the same crash
or not.

On 12/25/2009 07:08 AM, grigori wrote:
> well,
>
> unfortunately ff just crashed four or five times in a row. when starting
> from the terminal i get:
>
> $ firefox
> (firefox:3030): GLib-WARNING **: g_set_prgname() called multiple times
> Segmentation fault
>
> ff crashes with the segmentation fault error message.
>
>

[Martin Pitt (pitti)]

grigori, did you get those crashes already before this proposed update, or is this a new problem?

[arneko (goblinpower)]

If you are looking for a pretty foolproof way to get firefox crashing - my kids play a flash game every day, but it doesn't seem to work on my machine - I have UIM installed and it crashes every time they end their game.
The URL is
http://radaoz.mybrute.com

if you finish one game and try to start another one it will crash immediately.

Now I'll try the solution, since ff crashes for me too from time to time.

Thanks

[Christopher (soft-kristal)]

I'm having trouble in both Karmic and Lucid. It seems to be confined to when I am in a form, such as this one.

In Karmic, it usually logs me off but I go to an 'active' black screen in Lucid, requiring a reboot. If there has been a fix, it hasn't solved my problem as I was logged out by a Firefox (Karmic) crash about 15 minutes ago at a very inconvenient time; interviewing a client.

[Micah Gersten (micahg)]

Christopher, this bug is specifically for a crash in Firefox caused by
uim. I suggest filing a new bug about being logged off. Thanks.

On 12/27/2009 12:29 PM, Christopher wrote:
> I'm having trouble in both Karmic and Lucid. It seems to be confined to
> when I am in a form, such as this one.
>
> In Karmic, it usually logs me off but I go to an 'active' black screen
> in Lucid, requiring a reboot. If there has been a fix, it hasn't solved
> my problem as I was logged out by a Firefox (Karmic) crash about 15
> minutes ago at a very inconvenient time; interviewing a client.
>
>

[Gary Davis (gary-gbdavis)]

I have Ubuntu 9.10 as the OS with Firefox 3.5.6. When I am using the browser, it suddenly crashes and gives me a message when I re-open the browser of something like "being embarrassed and would I like to restore my session or start a new one."

[John Rose (johnaaronrose)]

Martin,

I'm getting same crash as grigori. I've also tried Firefox 3.6 from mozillateam's ppa with same result. I'll now try Micah's suggestion of logging new bug using apport.

[John Rose (johnaaronrose)]

Micah,

I just ran 'sudo service apport start force_start=1' in terminal. It came up with 'apport start/running'. I started firefox and it came up with the g_set_prgname warning and stopped as usual. Has any information been received by Canonical?

[Micah Gersten (micahg)]

@John Rose

Apport should pop up and ask you to submit a bug. If you didn't see that, then we didn't get the bug. Could you check /var/crash to see if there's an entry for firefox? You can use that to submit the bug by doing:
ubuntu-bug /var/crash/CRASH_FILE_GOES_HERE
and substituting your crash file name there.

[John Rose (johnaaronrose)]

Micah,
Apport didn't pop up and ask me to submit a bug. There are no files in /var/crash. What next?
PS I then set enabled =1 in /etc/default/apport and tried Firefox again. Same result i.e. crash without apport pop up.

[Micah Gersten (micahg)]

Please file a new bug: 'ubuntu-bug firefox-3.5' with your symptoms.
We'll diagnose there. No need for everyone on this bug to have the bugmail.

On 02/01/2010 09:02 AM, John Rose wrote:
> Micah,
> Apport didn't pop up and ask me to submit a bug. There are no files in /var/crash. What next?
> PS I then set enabled =1 in /etc/default/apport and tried Firefox again. Same result i.e. crash without apport pop up.
>
>

[John Rose (johnaaronrose)]

Micah,
I have run 'ubuntu-bug firefox-3.5'. It displayed a window about sending a report to which I confirmed send. Please let me know that the report has been received as I was not asked about the symptoms.

[Micah Gersten (micahg)]

I apologize, I keep forgetting that you can't use ubuntu-bug if your
browser isn't working.

Here are the instructions for manually filing a bug on Launchpad:
https://help.ubuntu.com/community/ReportingBugs#Filing bugs at Launchpad.net

On 02/01/2010 10:08 AM, John Rose wrote:
> Micah,
> I have run 'ubuntu-bug firefox-3.5'. It displayed a window about sending a report to which I confirmed send. Please let me know that the report has been received as I was not asked about the symptoms.
>
>

[John Rose (johnaaronrose)]

Micah,
I've reported a new bug: 515620.

[Ohad (ohadle)]

I'm getting this crashing with firefox 3.5.8 on karmic 32 bit.

[Micah Gersten (micahg)]

@Ohad
Do you have uim installed?

On 03/09/2010 04:03 PM, Ohad wrote:
> I'm getting this crashing with firefox 3.5.8 on karmic 32 bit.
>
>

[Martin Pitt (pitti)]

It's still not clear from current feedback whether the newly reported crash is something that the proposed update *introduced* (which would be a regression) or whether it happens with karmic final as well.

[Martin Pitt (pitti)]

Anyone who can test this and clarify whether above feedback was a regression or also happening on lucid final? If there is no further feedback, I'll remove the proposed version again. Thanks!

[Martin Pitt (pitti)]

Removed from karmic-proposed after 243 days, no positive, and some negative feedback.