Thank you [Alexander Sack] for your reference to the backtrace procedures. I've been too busy with other matters to look into it until today, though I have seen several more crashes. (Pretty much daily now.)
Unfortunately, the instructions for the backtrace procedures are quite complicated. They seem hard to understand, mostly because I don't know where my system currently stands in relation to those procedures. Meanwhile, new versions of various packages will appear... It also seems very likely that this procedure will change the nature of the problem enough that it seems probable that my efforts will be wasted. Then there will be the potential of future problems if I can't reverse the procedures... Sorry, but right now and based on the current level of problems, your request seems to be on the wrong side of reasonable. May I suggest that such crucial packages as Firefox should include a debugging option in the Preferences? It would be a relatively simple option that we could just switch on, so that we could quickly help you collect the information about such crashes. For right now I'm just planning to suffer for the brief period until the actual Firefox 3 arrives, and then see if the problem persists. -- Firefox grays out and crashes https://bugs.launchpad.net/bugs/230922 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
