Responses
Differences between revisions 2 and 43 (spanning 41 versions)
|
Size: 4409
Comment: Creating Mozilla Bugs Team
|
← Revision 43 as of 2008-08-06 17:00:54 ⇥
Size: 7820
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from FirefoxBugTriageResponses ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| |
<<Include(MozillaTeam/Header)>> |
| Line 4: | Line 3: |
| = Common responses = | ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>|| This page is useful for our bug triagers, below is a list of common responses for triaging Mozilla based bugs. Please be aware that these are merely templates and should be treated as such, try to flesh out the template and try to avoid being blunt with your response as this can be taken unintentionally as being rude. |
| Line 6: | Line 6: |
| Below is a list of common responses for triaging Firefox bugs. Be warned. it is still a braindump. Use at your own risk. | For a list of more generic responses please visit [[Bugs/Responses]] = Open Bug Reports = |
| Line 10: | Line 12: |
| 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. |
{{{ Thank you for the bug report. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs or attach the crash report located in /var/crash. If you dont see a crash report in /var/crash, you can enable apport by running "gksudo gedit /etc/default/apport" without the " and edit the 2nd line from [enabled=0] to read [enable=1] without the []. You need to restart Ubuntu before this takes affect. Now reproduce your crash and file bug using apport dialog. This will greatly aid us in tracking down your problem.}}} |
| Line 16: | Line 19: |
| 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. | {{{ Thank you for the bug report. Could you please install the firefox-dbg package and try to obtain a backtrace (or crash report) by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs This will greatly aid us in tracking down your problem. |
| Line 18: | Line 22: |
| Which flash package do you have installed? Which Java package do you have installed? Which firefox extensions do you have installed? |
Which flash package and version do you have installed? Which Java package and version do you have installed? Which video player and version do you have installed? Which firefox extensions and themes do you have installed?}}} |
| Line 22: | Line 27: |
| 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. |
{{{ Thank you for the 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/MozillaTeam/Bugs This will greatly aid us in tracking down your problem. |
| Line 33: | Line 35: |
| Which firefox extensions do you have installed? | Which video player and version do you have installed? Which firefox extensions do you have installed?}}} |
| Line 35: | Line 38: |
| Thanks David |
|
| Line 38: | Line 39: |
| {{{ | |
| Line 40: | Line 42: |
| Do you have and ati video card? |
Do you have an ati video card? |
| Line 49: | Line 50: |
| on the first line. Its a problem with xorg when you turned on the composite module. | on the first line. Its a problem with xorg when you turned on the composite module.}}} |
| Line 51: | Line 52: |
| == Lack of information == | == Obtain a backtrace from an apport crash report (using gdb) == |
| Line 53: | Line 54: |
| 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. | {{{ You might want to retrace yourself the coredump file with gdb. In that case you have to do the following: |
| Line 55: | Line 57: |
| Further information can be found at https://wiki.ubuntu.com/DebuggingFirefox |
Install the debugging symbols for firefox as: |
| Line 58: | Line 59: |
| Thanks David |
apt-get install firefox-dbg |
| Line 61: | Line 61: |
| == Closing stale bug == | Optionally you might want to install the following packages as: |
| Line 63: | Line 63: |
| I am unable to reproduce this issue. | apt-get install libgtk2.0-0-dbg libnss3-0d-dbg libnspr4-0d-dbg libpango1.0-0-dbg libc6-dbg |
| Line 65: | Line 65: |
| 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. | Copy and paste in a xterm the following sequence of commands: |
| Line 67: | Line 67: |
| Further information can be found at https://wiki.ubuntu.com/DebuggingFirefox |
TMPDIR=$(mktemp -d) apport-unpack /var/crash/_usr_lib_firefox_firefox-bin.1000.crash $TMPDIR gdb -nx /usr/lib/firefox/firefox-bin -core $TMPDIR/CoreDump -ex 'backtrace full' -ex 'thread apply all backtrace full' -ex 'quit' 2>&1 | tee gdb.log rm -fr $TMPDIR |
| Line 70: | Line 72: |
| Thanks David |
That command will run gdb against the coredump file included in the crash report that was generated when firefox crashed. |
| Line 73: | Line 74: |
| == Pinging old bug == | Upload the resulting gdb.log to launchpad. One good thing to do is looking at the gdb output and search for missing dbg libraries or other warnings, install them and run again gdb. Thank you in advance }}} |
| Line 76: | Line 82: |
| Is this still and issue for you? I am trying sort out the older mozilla issues? | == Getting more information == |
| Line 78: | Line 84: |
| Thanks David |
{{{ Thanks for taking the time to report this bug. Unfortunately, we are not able to fix and find the bug because your description of the bug didn't have enough information in it. You may find it helpful to read "How to report bugs effectively", http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. |
| Line 81: | Line 87: |
| Debugging procedures for certain types of problems can be found at https://wiki.ubuntu.com/MozillaTeam/Bugs}}} == Pinging Old (but Open) Bug Reports == {{{ Is this still an issue for you? We are trying to sort out the older Mozilla issues and would like to know if this still happens. If this still happens please report a new bug using Help > Report a problem from Firefox menu and file it against firefox-3.0 }}} == Run retrace == {{{ Thank you for the crash report. I am assigning this bug to myself in order to obtain a symbolized stacktrace of the crash report(s). When I am finished with it I will attach the stacktrace to this bug report. }}} == Crash repeatability == {{{ Thank you for the crash report. Can you repeat the crash? Does the crash generate a crash report? If so would you please attach it to this bug report, so we can process this bug further. }}} = Closing Old Bug Reports = == Crashes == {{{ Thank you for your bug report, but please understand that crashes are not bugs. Many crashes can be attributed to flaky plugins, extension conflicts, or other behavior. I am closing this bug for that reason, please feel free to reopen it if you feel the crash is reproducible. Use one or more of the following criteria: on other releases of Ubuntu, Newer versions of this program, crashes on every load and with up-to-date plugins. }}} == Lack of Information == {{{ Thank you for the bug report however this report lacks information we need to investigate it further. For this reason, we are now going to close the bug - please feel free to reopen when you have more information at hand. Further information can be found at https://wiki.ubuntu.com/MozillaTeam/Bugs}}} == Cannot Reproduce == {{{ Thank you for the bug report. However I am unable to reproduce this issue. We are now going to close this report - please feel free to reopen when you have more information at hand. }}} == Unresponsive Bug Reports == {{{ Thank you for the bug report. It has not been updated after a request for more information in the last 30 days, for this reason we are closing the report. Feel free to reopen it in the future if you have more information and if this is still an issue. }}} = Miscellaneous = |
|
| Line 84: | Line 144: |
| Thanks for your comment. The changes you are requesting require more discussion and should rather be done on an appropriate mailing list or forum. | {{{ Thank you for your feature idea. Anyway, new features of this kind should be implemented by the firefox developers. In order to get features into firefox you need to lobby upstream. Infos on the proper procedure for this can be found on http://forums.mozillazine.org/; read the sticky note about lobbying for features in "Firefox Features" forum. }}} |
| Line 86: | Line 148: |
| http://www.ubuntu.com/community/forums/ might be a good start. | {{{ Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you submit a specification for it. First check whether the idea is already registered <https://launchpad.net/ubuntu/+specs>, and if so, contact the specification's drafter about your ideas. Otherwise, you can start writing a spec yourself. <https://wiki.ubuntu.com/FeatureSpecifications> }}} |
| Line 88: | Line 153: |
| Thanks David |
== Support Request == |
| Line 91: | Line 155: |
| == 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 comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. <https://answers.launchpad.net/questions> }}} |
| Line 122: | Line 160: |
| Thanks for your issue report. | |
| Line 124: | Line 161: |
| == Crash repeatability == | |
| Line 126: | Line 162: |
| 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 |
---- [[CategoryMozillaTeam]], [[CategoryBugSquad]] |
This page is useful for our bug triagers, below is a list of common responses for triaging Mozilla based bugs. Please be aware that these are merely templates and should be treated as such, try to flesh out the template and try to avoid being blunt with your response as this can be taken unintentionally as being rude.
For a list of more generic responses please visit Bugs/Responses
Open Bug Reports
If the bug has no back trace
Thank you for the bug report. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs or attach the crash report located in /var/crash. If you dont see a crash report in /var/crash, you can enable apport by running "gksudo gedit /etc/default/apport" without the " and edit the 2nd line from [enabled=0] to read [enable=1] without the []. You need to restart Ubuntu before this takes affect. Now reproduce your crash and file bug using apport dialog. This will greatly aid us in tracking down your problem.
If debug symbols are not installed
Thank you for the bug report. Could you please install the firefox-dbg package and try to obtain a backtrace (or crash report) by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs This will greatly aid us in tracking down your problem. Which flash package and version do you have installed? Which Java package and version do you have installed? Which video player and version do you have installed? Which firefox extensions and themes do you have installed?
Thank you for the 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/MozillaTeam/Bugs 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 video player and version do you have installed? Which firefox extensions do you have installed?
It is of particular interest that you run apport-retrace against your crash report. Do you have an 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.
Obtain a backtrace from an apport crash report (using gdb)
You might want to retrace yourself the coredump file with gdb. In that case you have to do the following: Install the debugging symbols for firefox as: apt-get install firefox-dbg Optionally you might want to install the following packages as: apt-get install libgtk2.0-0-dbg libnss3-0d-dbg libnspr4-0d-dbg libpango1.0-0-dbg libc6-dbg Copy and paste in a xterm the following sequence of commands: TMPDIR=$(mktemp -d) apport-unpack /var/crash/_usr_lib_firefox_firefox-bin.1000.crash $TMPDIR gdb -nx /usr/lib/firefox/firefox-bin -core $TMPDIR/CoreDump -ex 'backtrace full' -ex 'thread apply all backtrace full' -ex 'quit' 2>&1 | tee gdb.log rm -fr $TMPDIR That command will run gdb against the coredump file included in the crash report that was generated when firefox crashed. Upload the resulting gdb.log to launchpad. One good thing to do is looking at the gdb output and search for missing dbg libraries or other warnings, install them and run again gdb. Thank you in advance
Getting more information
Thanks for taking the time to report this bug. Unfortunately, we are not able to fix and find the bug because your description of the bug didn't have enough information in it. You may find it helpful to read "How to report bugs effectively", http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. Debugging procedures for certain types of problems can be found at https://wiki.ubuntu.com/MozillaTeam/Bugs
Pinging Old (but Open) Bug Reports
Is this still an issue for you? We are trying to sort out the older Mozilla issues and would like to know if this still happens. If this still happens please report a new bug using Help > Report a problem from Firefox menu and file it against firefox-3.0
Run retrace
Thank you for the crash report. I am assigning this bug to myself in order to obtain a symbolized stacktrace of the crash report(s). When I am finished with it I will attach the stacktrace to this bug report.
Crash repeatability
Thank you for the crash report. Can you repeat the crash? Does the crash generate a crash report? If so would you please attach it to this bug report, so we can process this bug further.
Closing Old Bug Reports
Crashes
Thank you for your bug report, but please understand that crashes are not bugs. Many crashes can be attributed to flaky plugins, extension conflicts, or other behavior. I am closing this bug for that reason, please feel free to reopen it if you feel the crash is reproducible. Use one or more of the following criteria: on other releases of Ubuntu, Newer versions of this program, crashes on every load and with up-to-date plugins.
Lack of Information
Thank you for the bug report however this report lacks information we need to investigate it further. For this reason, we are now going to close the bug - please feel free to reopen when you have more information at hand. Further information can be found at https://wiki.ubuntu.com/MozillaTeam/Bugs
Cannot Reproduce
Thank you for the bug report. However I am unable to reproduce this issue. We are now going to close this report - please feel free to reopen when you have more information at hand.
Unresponsive Bug Reports
Thank you for the bug report. It has not been updated after a request for more information in the last 30 days, for this reason we are closing the report. Feel free to reopen it in the future if you have more information and if this is still an issue.
Miscellaneous
Feature request
Thank you for your feature idea. Anyway, new features of this kind should be implemented by the firefox developers. In order to get features into firefox you need to lobby upstream. Infos on the proper procedure for this can be found on http://forums.mozillazine.org/; read the sticky note about lobbying for features in "Firefox Features" forum.
Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you submit a specification for it. First check whether the idea is already registered <https://launchpad.net/ubuntu/+specs>, and if so, contact the specification's drafter about your ideas. Otherwise, you can start writing a spec yourself. <https://wiki.ubuntu.com/FeatureSpecifications>
Support Request
Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. <https://answers.launchpad.net/questions>
MozillaTeam/Bugs/Triage/Responses (last edited 2008-08-06 17:00:54 by localhost)