[Ubuntu Wiki] Update of "MozillaTeam/Bugs" by chrisccoulson

Ubuntu Wiki noreply at ubuntu.com
Fri Apr 20 11:00:58 UTC 2012


Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "MozillaTeam/Bugs" page has been changed by chrisccoulson:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=72&rev2=73

  To run Firefox in safe mode, ensure that you have closed all instances of Firefox, press Alt+F2 and run `firefox -safe-mode`.
  To run Thunderbird in safe mode, ensure that you have closed all Thunderbird windows, press Alt+F2 and run `thunderbird -safe-mode`.
  
- If the problem goes away in safe mode then it is caused by one of your addons or customizations.  In this case, please do not report the bug to Launchpad.  If you have time, you could try to isolate which addon or customization causes your problem, and contact the developer of the problematic addon.
+ If the problem goes away in safe mode then it is caused by one of your addons or customizations.  In this case, please do not report the bug against Firefox or Thunderbird in Ubuntu.  If you have time, you could try to isolate which addon or customization causes your problem, and contact the developer of the problematic addon.
  
  [[http://support.mozilla.com/en-US/kb/Safe%20Mode|Link to Mozilla Documentation]] 
  
  == Be specific ==
  
- Try to make sure that the developer will be able to reproduce the bug you are seeing.  Provide every detail you can regarding the bug, especially an explicit statement of exactly which sequence of user actions are needed to reproduce the bug.
+ Try to make sure that the developer will be able to reproduce the bug you are seeing.  Provide every detail you can regarding the bug, especially an explicit statement of exactly which sequence of user actions are needed to reproduce the bug.  Please don't assume that just because you experience a bug, that it will be trivial for other people to reproduce.
  
- == For problems with specific websites ==
+ == Problems with a specific website ==
  
  If a website does not display correctly in Firefox, you '''must''' provide the following information where possible:
   * A screenshot clearly showing the problem.
    * Please remember that the problem may not always be obvious to somebody else who isn't familiar with how the website should normally appear.  In this case, please describe exactly what is wrong.
    * You probably want to remove personal information from any screenshots.
-  * The URL of the page causing the problem (preferably a URL which doesn't require signing in, although we appreciate this is not always possible)
+  * The URL of the page causing the problem (preferably a URL which doesn't require signing in, although we appreciate this is not always possible).
  
  You might be surprised that we do get reports about websites not displaying correctly without any of this basic information provided.
  
@@ -68, +68 @@

  
   Since my automatic upgrade to Mozilla Firefox browser  7.01. I'm not now able to play promotional  videos on websites. When attempting to play a video, firefox browser crashes completely .And then you have to restart firefox.
  
- (these are real examples)
+ (These are real examples. Please don't do this)
  
  === Submitting Crashes to Mozilla ===
  
- The preferred way to submit crash data is to send it directly to Mozilla when the crash dialog appears.  To find your submitted crash data, go to about:crashes in the browser.  In most cases it isn't necessary to open a bug in Launchpad when you do this, especially if the crash report you submitted is already linked to a bug report in the upstream Bugzilla, or the crash is being experienced on non-Ubuntu systems (eg, other Linux distros, or even Windows or Mac OS). If the crash you submit appears to be unique to Ubuntu and it doesn't have a bug open in the upstream Bugzilla (or you just feel that Ubuntu developers need to be made aware of it), then feel free to open a bug in Launchpad.
+ If you are using the release or beta channel, the preferred way to submit crash data is to send it directly to Mozilla when the crash dialog appears.  In most cases it isn't necessary to open a bug in Launchpad when you do this, especially if the crash report you submitted is already linked to a bug report in the upstream Bugzilla, or the crash is being experienced on non-Ubuntu systems (eg, other Linux distros, or even Windows or Mac OS). If the crash you submit appears to be unique to Ubuntu and it doesn't have a bug open in the upstream Bugzilla (or you just feel that Ubuntu developers need to be made aware of it), then feel free to open a bug in Launchpad.
  
- If you do open a bug report in Launchpad, you '''must''' provide the crash ID of the crash report you submitted.
+ If you do open a bug report in Launchpad, you '''must''' provide the crash ID of the crash report you submitted, and '''please use Apport'''.
  
  To find the ID's of crash reports that you have submitted, go to Help -> Troubleshooting Information and click on the about:crashes link in the "Application Basics" section. This is applicable to Firefox and Thunderbird.
  
+ Note that the Apport hook provided from Firefox and Thunderbird 13  will automatically attach the ID's of crash reports you submitted to Mozilla, so you don't need to look for these manually '''as long as you submit the bug report using Apport!'''
+ 
  === Run Firefox in a Debugger ===
  
+ If you are using Aurora or Nightly builds (which don't have the crash reporter turned on), then you will need to get a stacktrace manually using gdb.  In some cases, a developer may ask you to do this in order to see local stack variables, which aren't visible in the upstream Socorro interface.
+ 
+ To begin, please install gdb
+ 
+ {{{
+  sudo apt-get install gdb
+ }}}
+ 
- Install the necessary debugging symbols
+ Then install the necessary debugging symbols.
  
  For Firefox:
  {{{
@@ -96, +106 @@

  }}}
  
  After closing all instances of Firefox, start Firefox from the terminal with the following command: {{{
- firefox -g 2>&1 | tee ~/tmp/gdb-firefox.txt
+  firefox -g 2>&1 | tee ~/gdb.txt
- ... # some output
+  (gdb) handle SIG33 pass nostop noprint
+  (gdb) set pagination 0
- (gdb) run
+  (gdb) run
  ... # run and reproduce crash
- (gdb) bt full
+  (gdb) bt full
- ... # full backtrace output
- (gdb) thread apply all backtrace full 
+  (gdb) thread apply all backtrace full
- ... # all threads full backtrace output
+  (gdb) info registers
- (gdb) quit
+  (gdb) quit
  }}}
-  2. Now ~/tmp/gdb-firefox.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report.
+  2. Now ~/gdb.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report.
  
  Please use the same steps for Thunderbird, but replacing "firefox" with "thunderbird" instead.
  
+ == Hangs, or excessive CPU usage ==
+ 
+ If Firefox or Thunderbird appears to completely lock up, you must provide a stacktrace of the hung process with your bug report.  In most cases, hangs are quite random and non-reproducible, so please don't submit reports without this information.
+ 
+ If it appears to be using excessive CPU, please first try disabling addons and plugins.  If the problem is with Firefox, are you viewing pages with Flash or video content, animated gif's or other animations?  Does the problem stop when you no longer view these?
+ 
+ If none of your addons are causing excessive CPU usage, and you're not viewing videos or Flash content, then there are a couple of things you can do to make your bug report more useful.  First, please get a stacktrace whilst the process is spinning the CPU.  Secondly, it would be great if you could try to use something like sysprof, which is available in the Software Center (see [[http://sysprof.com/|Sysprof, System-wide Performance Profiler for Linux]]
+ 
+ Some people also run the application in strace when reporting issues with excessive CPU usage.  In general, the output of strace is not all that useful when debugging an issue where the process is CPU bound.
+ 
+ === Getting a stacktrace of a hung process ===
+ 
+ Getting a stacktrace of a hung process is quite easy.  First, please install gdb and the required debugging symbols as advised in [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Run_Firefox_in_a_Debugger|Run Firefox in a Debugger]].
+ 
+ If the hang is reproducible, just run Firefox or Thunderbird as described in [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Run_Firefox_in_a_Debugger|Run Firefox in a Debugger]] and get a stacktrace when the application has hung.
+ 
+ If the hang is not reproducible and you want to get a stacktrace of an already hung process, you will need to attach gdb to it.  To do this, first run:
+ 
+ {{{
+  pidof firefox
+ }}}
+ 
+ ..or..
+ {{{
+  pidof thunderbird-bin
+ }}}
+ 
+ ...to get the PID of the process.  Then do:
+ {{{
+  gdb 2>&1 | tee ~/gdb.txt
+  (gdb) handle SIG33 pass nostop noprint
+  (gdb) set pagination 0
+  (gdb) attach <pid>
+ }}}
+ 
+ ...now you can get a stacktrace as advised below (assuming the process was hung before attaching gdb)
+ 
+ {{{
+  (gdb) bt full
+  (gdb) thread apply all backtrace full
+ }}}
+ 
+ If you're debugging excessive CPU rather than a hang, please repeat the following steps a few times:
+ 
+ {{{
+  (gdb) continue
+ ...# now press CTRL+C to interrupt it again
+  (gdb) bt full
+  (gdb) thread apply all backtrace full
+ }}}
+ 
+ Then:
+ {{{
+  (gdb) quit
+ }}}
+ 
+ Please remember to attach the resulting file to your bug report.
+ 
+ == Excessive memory usage ==
+ 
+ If you are reporting a bug about excessive memory usage, you '''must''' copy and paste the contents of "about:memory" in to your bug report, once you have reported this with Apport.
+ 
+ In the future, we hope to automate this step.
+ 
+ Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]] and [[https://developer.mozilla.org/en/Debugging_Mozilla_with_Valgrind|Debugging Mozilla with Valgrind]]
+ 
+ == Check the Error Console ==
+ 
+ Some bugs may result in unhandled JS exceptions or other error messages being logged to the error console, and these may provide a strong clue as to the cause of a bug. To view these, open the error console from "Tools -> Web Developer -> Error Console", and select "Errors".
+ 
+ Note, you many need to enable the menuitem to access the error console. To do this, open "about:config", and set "devtools.errorconsole.enabled" to "true"
+ 
+ == Other specific issues ==
- == "Secure Connection Failed" errors ==
+ === "Secure Connection Failed" errors ===
  
  If you see a warning with the title "Secure Connection Failed" and the text "The certificate is not trusted because the issuer certificate is unknown (Error code: sec_error_unknown_issuer)" when visiting a website with a https URL, then this means that Firefox is not able to chain the websites certificate to a trusted CA.
  
@@ -118, +201 @@

  
  If a site provides a certificate signed by an intermediate CA (one which is not in the root store, but with a trust chain to an existing root), the server must provide the intermediate certificates. Failure to do this will result in this error.
  
- === For certificates signed by RapidSSL (Geotrust) ===
+ ==== For certificates signed by RapidSSL (Geotrust) ====
  
  On December 9, 2010, Geotrust updated their certificate signing process and all certificates issued after this date require the installation of the RapidSSL intermediate on the server. Some sites forget to do this, which results in this error. This is a '''bug with the website'''
  
@@ -126, +209 @@

  
  [[https://knowledge.geotrust.com/support/knowledge-base/index?page=content&actp=CROSSLINK&id=SO9557|This]] online validation tool can tell you which intermediate a server is missing
  
- === Requests for inclusion of new CA's ===
+ ==== Requests for inclusion of new CA's ====
  
  In some cases when experiencing "unknown issuer" errors when visiting certain sites, it may be tempting to open a bug report to request that the issuer CA is added to the root store shipped with Firefox. Doing this would defeat the whole trust system. There is a '''well defined''' process for CA's to request that their certificate(s) be added and be shipped with Firefox. Details of this can be found at [[https://wiki.mozilla.org/CA:How_to_apply|https://wiki.mozilla.org/CA:How_to_apply]]
  
- '''We will not bypass this process under any circumstances''', so please '''do not''' make these types of requests. Requests of this type '''will be rejected'''.
+ '''We will not bypass this process under any circumstances''', so please make these types of requests. Requests of this type '''will be rejected'''.
  
- == Problems launching external applications ==
+ === Problems launching external applications ===
  
  Ubuntu ships an Apparmor profile with Firefox, but this is disabled by default. If you have problems opening files in external applications from Firefox, or problems with extensions which need to start external helpers, then please make sure that the Apparmor profile is disabled or in complain mode before reporting a bug.
  
@@ -178, +261 @@

  
  See [[https://help.ubuntu.com/community/AppArmor|AppArmor]]
  
- == Check the Error Console ==
+ === "The bookmarks and history system will not be functional" ===
  
- Some bugs may result in unhandled JS exceptions or other error messages being logged to the error console, and these may provide a strong clue as to the cause of a bug. To view these, open the error console from "Tools -> Web Developer -> Error Console", and select "Errors".
+ If you see this error when starting Firefox and you are unable to access or modify your bookmarks, please take a look at this support article: [[http://support.mozilla.org/en-US/kb/The%20bookmarks%20and%20history%20system%20will%20not%20be%20functional|The bookmarks and history system will not be functional]].
  
+ This is not usually a bug, but is normally caused by a corrupt places.sqlite or broken permissions in your profile folder.  Please don't report a bug about this, unless you are unable to resolve the issue by following the steps in the support article.
- Note, you many need to enable the menuitem to access the error console. To do this, open "about:config", and set "devtools.errorconsole.enabled" to "true"
- 
- == For problems with memory usage ==
- 
- If you are reporting a bug about excessive memory usage, please copy and paste the contents of "about:memory" in to your bug report, once you have reported this with Apport.
- 
- In the future, we hope to automate this step.
- 
- Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]] and [[https://developer.mozilla.org/en/Debugging_Mozilla_with_Valgrind|Debugging Mozilla with Valgrind]]
- 
- == Specific issues ==
  
  === XML errors and broken UI after upgrade ===
  



More information about the Ubuntu-bugsquad mailing list