Common responses

Below is a list of common responses for triaging Firefox bugs. Be warned. it is still a braindump. Use at your own risk.

If the bug has no back trace

Thanks for your bug report. Could you please try to obtain a backtrace by following the instructions on

• https://wiki.ubuntu.com/DebuggingFirefox

This will greatly aid us in tracking down your problem.

If debug symbols are not installed

Thanks for your bug report. Could you please install firefox-dbg and try to obtain a backtrace (or crash report) by following the instructions on https://wiki.ubuntu.com/DebuggingFirefox This will greatly aid us in tracking down your problem.

Which flash package do you have installed? Which Java package do you have installed? Which firefox extensions do you have installed?

Thanks David

If debug symbols are not installed

Thanks for your bug report. Could you please install firefox-dbg (these are the firefox debugging symbols) and try to obtain a backtrace (or crash report) by following the instructions on https://wiki.ubuntu.com/DebuggingFirefox This will greatly aid us in tracking down your problem.

It is of particular interest that you run apport-retrace -d against your crash report before uploading.

Which flash package do you have installed? Which Java package do you have installed? Which firefox extensions do you have installed?

Thanks David

It is of particular interest that you run apport-retrace against your crash report.

Do you have and ati video card?

Ahhh. You must have a ATI card. My IBM T43 had the same problem. Add this to your /etc/bin/firefox: Code: export XLIB_SKIP_ARGB_VISUALS=1 and/or by adding to your /etc/env.d/10MozillaFirefox: Code: LIB_SKIP_ARGB_VISUALS=1 on the first line. Its a problem with xorg when you turned on the composite module.

Lack of information

This issue report lacks information we need to investigate further. We are now going to close the bug - please reopen when you have more information at hand.

Further information can be found at https://wiki.ubuntu.com/DebuggingFirefox

Thanks David

Closing stale bug

I am unable to reproduce this issue.

We haven't heard back from you in 30 days. We are now going to close this issue - please reopen if necessary when you have more information at hand.

Further information can be found at https://wiki.ubuntu.com/DebuggingFirefox

Thanks David

Pinging old bug

Is this still and issue for you? I am trying sort out the older mozilla issues?

Thanks David

Feature request

Thanks for your comment. The changes you are requesting require more discussion and should rather be done on an appropriate mailing list or forum.

http://www.ubuntu.com/community/forums/ might be a good start.

Thanks David

Run retrace

Thanks for your crash report.

Could you please download you crash report, run

apport-retrace -d [filename]

and resubmit it. Instructions can be found at https://wiki.ubuntu.com/Apport Apport-retrace will add many of the debug symbols necessary to get to the bottom of this problem.

I am working my way though all of the firefox issues reports and don't have enough bandwidth to download/upload them all myself;(

Thanks David

Retrace done

Sitsofe has created a symbolized stacktrace so there is no longer a need for you to try to run gdb.

But, if you can reproduce this bug. Could you please run

apport-retrace -d [filename]

on the crashreport and resubmit it. Instructions can be found at https://wiki.ubuntu.com/Apport

I am working my way though all of the firefox issues reports and don't have enough bandwidth to do them all myself;(

Thanks David

Thanks for your issue report.

Crash repeatability

Can you repeat the cash? Does the crash generate a crash report? If so would you please run

apport-retrace -d [filename]

and resubmit it. Information can be found at https://wiki.ubuntu.com/Apport Apport-retrace -d will add many of the debug symbols necessary to get to the bottom of this problem.

Thanks David