From webmaster at ubuntu.com Fri Nov 2 15:17:02 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Fri, 02 Nov 2012 15:17:02 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_chris-bainbridge?= Message-ID: <20121102151702.1081.42411@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by chris-bainbridge: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=211&rev2=212 Comment: some notes on crash reports not being uploaded to launchpad etc. ==== Stable release ==== - Apport is disabled by default in stable releases. To enable it, edit the file: + Apport is disabled by default in stable releases (note: this is not true, apport is enabled by default in Precise, I have not checked other releases). To enable it, edit the file: {{{ /etc/default/apport }}} @@ -113, +113 @@ {{{ enabled=1 }}} + + Note 1) even when enabled, apport will not upload crash reports to Launchpad for a stable release (this is deliberate, see [[https://bugs.launchpad.net/apport/+bug/997283|bug #997283]]). Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. + + Note 2) apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. === System crash === @@ -221, +225 @@ You will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the `.apport` or `.crash` extension. After copying it to a different system you can file that report using the following command:<
>`ubuntu-bug -c` ''``'' + (note: this does not work for crash reports from stable Ubuntu releases, see [[https://bugs.launchpad.net/apport/+bug/997283|bug #997283]] crash reports "do not get filed to Launchpad any more... we don't want crash reports for the non-development version on Launchpad.") If this is to be added to an existing bug report, also use the -u option:<
>`ubuntu-bug -c` ''``'' `-u` ''``'' From noreply at ubuntu.com Thu Nov 15 17:29:29 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 15 Nov 2012 17:29:29 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Valgrind=22_by_achiang?= Message-ID: <20121115172929.17528.38751@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Valgrind" page has been changed by achiang: http://wiki.ubuntu.com/Valgrind?action=diff&rev1=15&rev2=16 tar -zcf valgrind-logs-.tar.gz valgrind.log* }}} 1. Attach the complete output from Valgrind, contained in valgrind-logs-.tar.gz, in your bug report. + + [[http://valgrind.org/docs/manual/faq.html | Valgrind FAQ]] ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Fri Nov 16 11:57:23 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 16 Nov 2012 11:57:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?= =?utf-8?q?lson?= Message-ID: <20121116115723.9829.50843@mangaba.canonical.com> 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=85&rev2=86 = Reporting Bugs = + == Summary (or tl;dr version) == + + Here is a brief summary of the bug reporting procedure: + + 1. [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Consider_whether_a_support_request_would_be_more_appropriate|Consider whether a support request would be more appropriate than a bug report]] + 2. [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Try_running_in_safe_mode|Try running in safe mode]] or disabling extensions + * If disabling extensions resolves the issue, then please don't report a bug against the application (although if the problematic extension is provided by Ubuntu, please do report a bug against that extension) + 3. If you're sure that your problem is a genuine application bug, please [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Check_if_the_bug_has_already_been_reported|check if the bug has already been reported]] + 4. If your bug hasn't been reported then you should report a new bug. However, please run through this simple checklist before doing so: + * Is my problem with a specific website? + * If so, please have a read of [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Problems_with_a_specific_website|Problems with a specific website?]] + * Is my problem a crash? + * If so, please have a read of [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Crashes|Crashes]] + * Is the application hanging or using a lot of CPU? + * If so, please have a read of [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Hangs.2C_or_excessive_CPU_usage|Hangs or excessive CPU usage]] + * Please check briefly if your problem is related to any of the more specific issues in [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Other_specific_issues|Other specific issues]] + 5. Now you can report a bug! When doing so, please keep in mind the following points: + * [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Use_Apport|Please use Apport]] + * [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Be_specific|Please describe the problem in detail]] + == Introduction == - You can help Ubuntu developers improve Firefox and Thunderbird by providing them with ''useful'' bug reports. This means that you should provide as much information as possible to describe the bug (please see [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to report Bugs]]) + You can help Ubuntu developers improve Firefox and Thunderbird by providing them with useful bug reports. This means that you should provide as much information as possible to describe the bug (please see [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to report Bugs]]) You may find that you need to use the Terminal for some of these commands. If you are not sure how to use a terminal, please see the [[https://help.ubuntu.com/community/UsingTheTerminal|Terminal Guide]] for a basic introduction. + We get a lot of Firefox bug reports from Ubuntu users and a lot of these don't contain sufficient useful information to progress them further, or sometimes even understand what problem the user is reporting. Please understand that we don't have the manpower available to spend time on every bug report to continually ask reporters for information that could be provided up-front. To increase the chances that your bug report attracts the attention of a developer, you '''must''' follow these guidelines. A developer will ask you for the required information that you didn't provide, so following these guidelines will save time for the person who looks at your bug report. - We get a lot of Firefox bug reports from Ubuntu users and the majority of those don't contain sufficient useful information to progress them further, or sometimes even understand what the actual problem is. Please understand that we don't have the manpower available to spend time on every single bug report to continually ask reporters for information that ''could'' be provided up-front. To increase the chances that your bug report attracts the attention of a developer, you '''must''' follow these guidelines. A developer will ask you for the required information that you didn't provide, so following these guidelines will save time for the person who looks at your bug report. - - Here are some instructions you should follow before filing a bug report: == Consider whether a support request would be more appropriate == @@ -32, +50 @@ See also [[http://www.ubuntu.com/community/report-problem|http://www.ubuntu.com/community/report-problem]]. + == Try running in safe mode == + + Some problems are caused by third-party themes, addons and plugins, or customization of hidden preferences in about:config. These customizations can be disabled temporarily by running Firefox or Thunderbird in safe mode. + + 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 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]] + + == Check if the bug has already been reported == + + Please try to make the effort to check if your bug has already been reported. We appreciate that sometimes it is difficult to know what to search for, and it may be difficult to spot duplicates in the presence of so many other bug reports. + + Launchpad has a facility to search the bug database. You can search Launchpad directly from the following links: + + * [[https://bugs.launchpad.net/ubuntu/+source/firefox|For Firefox]] + * [[https://bugs.launchpad.net/ubuntu/+source/thunderbird|For Thunderbird]] + + You may have better luck by using Google directly. If you search from Google, try prefixing your search term with `https://bugs.launchpad.net:` + == Use Apport == - All Firefox and Thunderbird bugs '''must''' be submitted with Apport (unless there is another problem which prevents you from using Apport). For Firefox, you can do this by selecting the "Report a Problem" entry in the Help menu, or pressing Alt+F2 and running `ubuntu-bug firefox`. + All Firefox and Thunderbird bugs '''must''' be submitted with Apport (unless there is another problem which prevents you from using Apport). + + For Firefox, please press Alt+F2 and run `ubuntu-bug firefox`. For Thunderbird, please press Alt+F2 and run `ubuntu-bug thunderbird`. - Using Apport attaches a lot of useful information automatically, and saves time by answering a lot of common questions that developers and bug triagers would normally need to ask. Please do not submit Firefox or Thunderbird bugs using the Launchpad interface. In most cases your bug report will not get any attention at all, and if it does receive any attention this will normally be to close it with a comment asking you to resubmit the bug using Apport. Please don't waste developers or bug triagers time by submitting bug reports using the Launchpad interface. + Using Apport attaches a lot of useful information automatically, and saves time by answering a lot of common questions that developers and bug triagers would normally need to ask. Please do not submit Firefox or Thunderbird bugs using the Launchpad interface. Doing so reduces the chances of your bug report receiving attention from a developer, and your bug report may be closed with a comment asking you to resubmit it using Apport. Please remember that a lot of bug triagers are volunteering in their own time, and appreciate bug reporters helping themselves as much as possible. - == Try running in safe mode == + == Be specific == - Some problems are caused by third-party themes, addons and plugins, or customization of hidden preferences in about:config. These customizations can be disabled temporarily by running Firefox or Thunderbird in safe mode. + 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. + == Multiple problems == - 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`. + Multiple, unrelated bugs '''must be reported as separate bugs'''. Please do not use a single bug report to report or discuss multiple, unrelated bugs. If you do this, then it is highly likely that a developer will close your bug report and ask you to report the problems separately. - 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]] - - == Check if the bug has already been reported == - - Please try to make the effort to check if your bug has already been reported. We appreciate that sometimes it is difficult to know what to search for, and it may be difficult to spot duplicates in the presence of so many other bug reports. == Look for your problem on SUMO == Please have a look on [[http://support.mozilla.org/|http://support.mozilla.org/]], to see if anybody else has asked for support for a problem that is similar to your own. You may find that the problem you are facing isn't really a bug, or the problem has already been reported to developers. You may also find a workaround for your problem too. - - == 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. Please don't assume that just because you experience a bug, that it will be trivial for other people to reproduce. - - == Multiple problems == - - Multiple, unrelated bugs '''must be reported as separate bugs'''. Please do not use a single bug report to report or discuss multiple, unrelated bugs. If you do this, then it is highly likely that a developer will close your bug report and ask you to report the problems separately. == Is the problem Ubuntu specific? == @@ -84, +112 @@ Obviously, for Thunderbird, replace "firefox" with "thunderbird". If the same problem can be recreated in the official Mozilla build that you downloaded, then you can help Ubuntu developers by reporting your bug in the upstream bug tracker. To do this, please have a read through the upstream [[https://developer.mozilla.org/en/Bug_writing_guidelines|bug reporting guidelines]]. - - == 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" == Problems with a specific website == @@ -99, +121 @@ * 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). - You might be surprised that we do get reports about websites not displaying correctly without any of this basic information provided. + You might be surprised that we do get reports about websites not displaying correctly without any of this information provided. If you have a problem with a website, please also do the following: * Try using the website in another (non-Gecko) browser (eg, Chromium or Epiphany). @@ -110, +132 @@ === Some things to consider === - Please don't assume that just because you experience a crash, that everybody else will be able to easily reproduce it too. All crash reports must be submitted with a complete stacktrace, and a description of the steps required to trigger the crash (if it is reproducible). If the problem occurs on a specific website, please also include a URL. + Please don't assume that everybody else will be able to reproduce your crash, just because you experience the issue. All crash reports must be submitted with a complete stacktrace and a description of the steps required to trigger the crash (if it is reproducible). If the problem occurs on a specific website, please also include a URL. + Bug reports which tell us that the application crashes without any other technical information about the crash (ie, a complete stacktrace) are not very useful. - As an example, these types of reports are not useful, and are unlikely to receive any developer attention at all: - - Sometimes after I clicked on a link, firefox crashes and the "report this crash to the devellopers" window opens. - - ...and... - - 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. Please don't do this) === Submitting Crashes to Mozilla === - 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 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 bug tracker, 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 think that the crash is occurring due to an addon shipped by Ubuntu, then you should report the bug in Launchpad. - 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'''. + If you do open a bug report in Launchpad, you '''must''' provide the crash ID of the crash report you submitted, and '''please [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Use_Apport|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. + 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!''' + 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 [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Use_Apport|submit the bug report using Apport]]''' === Run Firefox in a Debugger === @@ -174, +188 @@ == 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 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 consider this before reporting a bug without any technical information about the hang. - 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 it appears to be using excessive CPU, please first try [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Try_running_in_safe_mode|running in safe mode]] or 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]] @@ -230, +244 @@ Please remember to attach the resulting file to your bug report. + == 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" + == 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. Please don't report bugs about memory usage without this information, as it will be the first thing a developer asks for anyway. @@ -249, +269 @@ In these environments, problems with the menus are not always an application bug. - If you experience an issue with the '''content''' of the menubar, menus or menuitems (ie, what the actual text says, what the icons display or the state of any radio or check items), then this should be reported as an application bug (against Firefox or Thunderbird). If you experience an issue with '''actions''' (ie, what happens when you click on a menuitem or invoke an accelerator key), then this might be an application bug too. + If you experience an issue with the ''content'' of the menubar, menus or menuitems (ie, what the actual text says, what the icons display or the state of any radio or check items), then this should be reported as an application bug (against Firefox or Thunderbird). If you experience an issue with ''actions'' (ie, what happens when you click on a menuitem or invoke an accelerator key), then this might also be an application bug. - In general, any problem with the '''view''' of the menubar, menus or menuitems is normally a bug with the desktop shell instead. Examples of this might include: + In general, any problem with the ''view'' of the menubar, menus or menuitems is normally a bug with the desktop shell instead. Examples of this might include: * Alignment of elements in the menu * Colour or theming of the menus * Menus not responding correctly to events (ie, submenus not opening on mouseover or menuitems not highlighting on mouseover) @@ -274, +294 @@ ==== Keyboard type-ahead feature does not work with the global menubar ==== - Gecko has a feature that allows you to select bookmark items from a menu with the keyboard, using a type-ahead like feature. Other toolkits lack this feature though, so this won't work with the global menubar. Please don't report this as a bug against Firefox, as it isn't. This is functionality that needs to be added to the toolkit responsible for drawing the menu + Gecko has a feature that allows you to select bookmark items from a menu with the keyboard, using a type-ahead like feature. Other toolkits lack this feature though, so this won't work with the global menubar. Please don't report this as a bug against Firefox. This is functionality that needs to be added to the toolkit responsible for drawing the menu. See [[https://launchpad.net/bugs/917753|bug 917753]] @@ -282, +302 @@ When downloading a file type that Firefox is unable to view, Firefox presents a dialog that gives you the option of saving the file to disk or opening the file with an application installed on your system ("Open With"). However, "Open With" currently only offers the default handler for the particular file type, and the only way to specify an alternative application is to navigate the filesystem. - This is a Firefox limitation that we're already well aware of. Please don't report new bugs for this problem. + This is a Firefox limitation that we're already aware of. Please don't report new bugs for this problem. See [[https://launchpad.net/bugs/18995|Bug 18995]] === "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. + 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 Certificate Authority. - This could be a problem with the server, or it could be that somebody is impersonating the server. It is generally '''not a bug with Firefox''' + This could be a problem with the server, or it could be that somebody is [[http://wikipedia.org/wiki/Man-in-the-middle_attack|impersonating the server or eavesdropping on your connection]]. It is generally not a bug with Firefox. - 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 if the intermediate certificates do not already exist in your certificate store. + 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 CA), the server must provide the intermediate certificates. Failure to do this will result in this error if the intermediate certificates do not already exist in your certificate store. ==== 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''' + 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''' See [[http://blog.clickssl.com/2010/12/rapidssl-error-on-firefox-this-connection-is-untrusted/|http://blog.clickssl.com/2010/12/rapidssl-error-on-firefox-this-connection-is-untrusted/]] @@ -304, +324 @@ ==== 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]] + 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's certificate is added to the root store shipped with Firefox. There is a [[https://wiki.mozilla.org/CA:How_to_apply|well defined process]] for CA's to request that their certificates are added to the Firefox root store. Adding a certificate to the root store means that the browser places ultimate trust in the certificate owner on our users behalf. - We will not bypass this process under any circumstances, so please don't make these types of requests. Requests of this type '''will be rejected'''. + We don't have our own process for verifying applications for inclusion of new certificates, or a process to ensure the continued integrity of the owning authorities once these certificates have been added. We will not bypass the upstream process under any circumstances, so please don't make these types of requests. Doing this without ensuring the integrity of a CA would undermine the entire trust system on the web. Requests of this type will be rejected. === 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. + 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. To make sure that the profile is not in enforce mode, run `sudo aa-status`. You will see output which looks a bit like this: {{{ @@ -348, +368 @@ 0 processes are unconfined but have a profile defined. }}} - If there are entries starting with "/usr/lib/firefox" in the section "profiles are in enforce mode", then the Firefox profile has been enabled and set to enforce mode. In this case, please set it to complain mode and try again. To do this, please run `sudo aa-complain /usr/bin/firefox`. (Note, you will need to install apparmor-utils to do this) + If there are entries starting with "/usr/lib/firefox" in the section "profiles are in enforce mode", then the Firefox profile has been enabled and set to enforce mode. In this case, please set it to complain mode and try again. To do this, please run `sudo aa-complain /usr/bin/firefox`. (Note, you will need to install apparmor-utils to do this) - If this works and the particular executable is from a software package in the Ubuntu archive, then we may consider adding an exception to the Apparmor profile. In this case, please report a bug using Apport. If the executable is from 3rd party software outside of the Ubuntu archive, then you will need to either keep the Apparmor profile disabled, or add an exception locally in /etc/apparmor.d/local/usr.bin.firefox. + If this works and the particular executable is from a software package in the Ubuntu archive, then we may consider adding an exception to the Apparmor profile. In this case, please report a bug using Apport. If the executable is from 3rd party software outside of the Ubuntu archive, then you will need to either keep the Apparmor profile disabled, or add an exception locally in /etc/apparmor.d/local/usr.bin.firefox. See [[https://help.ubuntu.com/community/AppArmor|AppArmor]] @@ -372, +392 @@ Other symptoms include missing UI elements after an upgrade or other kinds of XML errors in dialogue boxes or on firefox's stderr. - This is one of the things that typically happens if you don't restart your Firefox after an upgrade. Please do not report this as a bug. There is already a bug report open about this. + This is one of the things that typically happens if you don't restart your Firefox after an upgrade. Please do not report this as a bug. There is already a bug report open about this. = Closed Bug Reports = If you find your bug report to be closed, it has been done by someone on our team for specific reasons. If you have a problem or wish to dispute the action, please use the bug report to ask for more information. From noreply at ubuntu.com Sat Nov 17 20:05:41 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 17 Nov 2012 20:05:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspendHibernateR?= =?utf-8?q?esume=22_by_vanessaezekowitz?= Message-ID: <20121117200541.17935.75401@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelSuspendHibernateResume" page has been changed by vanessaezekowitz: http://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume?action=diff&rev1=22&rev2=23 This page is aimed to help you do initial triage and debug of suspend/resume or hibernate/resume bugs as reported by apport. This page presents some background information as to how the reporting works, and then will take you through a series of debug steps recommending information and data which will need to be collected. - The primary source of reports of suspend and hibernate failures arrive via apport. Apport checks at boot time whether there was a suspend or hibernate in progress, if we are booting normally then that was never resumed and therefore has failed. This means that the failure may have occured some time before the report is generated. Bear this in mind when answering the questions below. + The primary source of reports of suspend and hibernate failures arrive via apport. Apport checks at boot time whether there was a suspend or hibernate in progress, if we are booting normally then that was never resumed and therefore has failed. This means that the failure may have occurred some time before the report is generated. Bear this in mind when answering the questions below. == Bug Validation == @@ -21, +21 @@ === Is this a repetition of a previous failure? === - If this is another occurance of a previous reported failure it is best to mark the new bug a duplicate of the first using the Mark Duplicate link on the bug report. + If this is another occurrence of a previous reported failure it is best to mark the new bug a duplicate of the first using the Mark Duplicate link on the bug report. == Information Gathering == @@ -88, +88 @@ [[https://help.ubuntu.com/community/EncryptedHome|https://help.ubuntu.com/community/EncryptedHome|target="https://help.ubuntu.com/community/EncryptedHome"]] - Users installing from Ubuntu 9.10 and selecting the Encrypted Home option will automatically have encrypted swap space. Other users may have also ran sudo ecryptfs-setup-swap. It is important to note that Hibernation will work with an encrypted swap but resume will fail. There are ways around this, but theyinvolve choosing a password to use for your encrypted swap and entering that password every time you boot your system, and sharing that password with anyone else that might want to resume the system. This is a known, wishlist [[https://bugs.launchpad.net/ecryptfs/+bug/432785|issue|target="https://bugs.launchpad.net/ecryptfs/+bug/432785"]] that we hope to solve. If you happen to report or triage this type of issue, please tag the bug '''encrypted-swap'''. For triagers, posting the following comment to a bug may help: + Users installing from Ubuntu 9.10 and selecting the Encrypted Home option will automatically have encrypted swap space. Other users may have also ran sudo ecryptfs-setup-swap. It is important to note that Hibernation will work with an encrypted swap but resume will fail. There are ways around this, but they involve choosing a password to use for your encrypted swap and entering that password every time you boot your system, and sharing that password with anyone else that might want to resume the system. This is a known, wishlist [[https://bugs.launchpad.net/ecryptfs/+bug/432785|issue|target="https://bugs.launchpad.net/ecryptfs/+bug/432785"]] that we hope to solve. If you happen to report or triage this type of issue, please tag the bug '''encrypted-swap'''. For triagers, posting the following comment to a bug may help: ||Thank you for taking the time to report this bug and helping to make Ubuntu better. It is currently a known issue that Hibernation will fail to resume due to an encrypted swap. Please refer to https://help.ubuntu.com/community/EncryptedHome for more information. We will tag this bug "encrypted-swap" so that we can track this issue going forward and possibly request additional testing. Thanks in advance for your patience and cooperation. || == Hibernating from text mode == @@ -154, +154 @@ Please report whether you got any additional messages. Digital photos of the screen are a sensible way to get this into the bug. + = Dead, Blank, or Black Screen on Resume = + + In some cases, a machine can suspend or hibernate just fine, and resume from those states without issue, with the exception of waking up to a blacked-out screen. In other words, the computer is running just fine, but the display appears dead. If nothing else in this article solves that issue, or the text above just doesn't apply to your particular setup, there's one more thing to try - disable Kernel Mode Setting. + + Edit your grub configuration: + + {{{ + sudo nano /etc/default/grub + }}} + + Find the line reading: + + {{{ + GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" + }}} + + Add {{{nomodeset}}} to the end, inside the quotes: + + {{{ + GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" + }}} + + Exit from nano and save the file. Make grub aware of the new changes: + + {{{ + update-grub2 + }}} + + When that exits, reboot the computer normally, then test suspend and/or hibernate. This change will persist across reboots unless you explicitly revert it. In some cases, this will also fix another issue where the screen doesn't dim after a period of inactivity like it should, assuming it is otherwise configured to do so in your desktop environment + = Notes = == Battery drained whilst suspended stock reply == From noreply at ubuntu.com Sat Nov 17 22:19:42 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 17 Nov 2012 22:19:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_logan?= Message-ID: <20121117221942.6162.34745@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by logan: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=363&rev2=364 Comment: change all instances of "Quantal Quetzal" to "Raring Ringtail" Before using this, ''please'' check "rmadison " to see if the package version has changed between when the bug was reported and the current development release. If it has not changed, there is no need to ask. If it has changed, check the changelog (via aptitude changelog $PKGNAME) to see if this issue has been specifically addressed. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Quantal Quetzal. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Raring Ringtail. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| == Missing a crash report or having a .crash attachment == @@ -208, +208 @@ ## Also we are actively promoting testing the development release of Ubuntu so something like this could be added: - ## || The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Quantal Quetzal. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ || + ## || The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Raring Ringtail. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ || == Packages not provided by Ubuntu == @@ -221, +221 @@ The bug's state should become '''Fix Released''' and if the package qualifies for a [[https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|Stable Release Update (SRU)]]: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Quantal Quetzal.<
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.<
><
>[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Raring Ringtail.<
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.<
><
>[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|| The bug's state should become '''Fix Released''' and if the package does not qualify for a SRU because it is considered a minor bug and the package can be backported: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Quantal Quetzal.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Raring Ringtail.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport || The bug's state should become '''Fix Released''' and if the package can not be backported: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Quantal Quetzal. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://wiki.ubuntu.com/UbuntuBackports for more information. || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Raring Ringtail. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://wiki.ubuntu.com/UbuntuBackports for more information. || == Reported by someone not respecting the Code of Conduct == From rodgerspooncer at blueyonder.co.uk Mon Nov 19 15:22:10 2012 From: rodgerspooncer at blueyonder.co.uk (rodger) Date: Mon, 19 Nov 2012 15:22:10 +0000 Subject: HP PSC750 Message-ID: <1353338530.2116.6.camel@rodger-desktop> Hi, Every time I use the HP PSC750 printer under Ubuntu 12.04 I get an error message. When I choose the option to report the error I get a further message along the lines that it has not been possible to determine the package name. Does this mean that the persistent error never gets reported? regards Rodger Spooncer -------------- next part -------------- An HTML attachment was scrubbed... URL: From alanbell at ubuntu.com Mon Nov 19 16:47:00 2012 From: alanbell at ubuntu.com (Alan Bell) Date: Mon, 19 Nov 2012 16:47:00 +0000 Subject: HP PSC750 In-Reply-To: <1353338530.2116.6.camel@rodger-desktop> References: <1353338530.2116.6.camel@rodger-desktop> Message-ID: <50AA6284.3020609@ubuntu.com> On 19/11/12 15:22, rodger wrote: > Hi, > > Every time I use the HP PSC750 printer under Ubuntu 12.04 I get an > error message. > > When I choose the option to report the error I get a further message > along the lines that it has not been possible to determine the package > name. > > Does this mean that the persistent error never gets reported? > yes it does, because it is not part of Ubuntu. I suspect you have installed some software from HP to drive that printer and it is crashing. The issue should really be reported to HP. Alan. -- I work at http://libertus.co.uk From noreply at ubuntu.com Tue Nov 20 19:47:17 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 20 Nov 2012 19:47:17 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Troubleshooting=22_by_bryce?= Message-ID: <20121120194717.31191.63167@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "X/Troubleshooting" page has been changed by bryce: http://wiki.ubuntu.com/X/Troubleshooting?action=diff&rev1=59&rev2=60 * [[X/Troubleshooting/HugeFonts|Fonts displayed way too big]] * [[X/Troubleshooting/IntelPerformance|Intel graphics performance issues]] * [[X/i8xxUnsupported|i855 is Unsupported]] - Explanation of why i845, i855, i865, etc. chips aren't supported - * [[X/HybridGraphics|Hybrid Graphics is Unsupported]] - Not officially supported, but the community has workarounds Input Issues * [[Hotkeys/Troubleshooting|Multimedia hotkey problems]] From noreply at ubuntu.com Thu Nov 22 17:44:41 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 22 Nov 2012 17:44:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=22_by_pe?= =?utf-8?q?nalvch?= Message-ID: <20121122174441.14306.30372@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling" page has been changed by penalvch: http://wiki.ubuntu.com/LibreOfficeBugWrangling?action=diff&rev1=18&rev2=19 Comment: Adding request in Bug Reporting Template for apt-show-versions -r libreoffice* . Please see ## wiki comments for justification due to character limit in "Comment:" field. + ## 20121122 https://launchpad.net/~penalvch When one files a bug via apport against libreoffice via ubuntu-bug libreoffice and did not install the libreoffice meta package, the filed bug report tends not to provide enough information to triage appropriately. Ex. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1080509 one has no idea what specific LO packages they actually have installed. Hence, asking for apt-show-versions -r libreoffice* in the bug reporting template section is an extremely helpful way an original reporter can provide information for triagers to work on the problem without asking for follow up information, and waiting for the response. However, not all packages in https://launchpad.net/ubuntu/+source/libreoffice have libreoffice in the name, so some will be missed (ex. ure, python-uno, etc.). If a more comprehensive command exists to provide all the installed packages for libreoffice with versions compactly, that does not contain the word libreoffice in the package name, please replace. I just have not come across a more relevant one. Thank you for your understanding. + Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it| Italiano]] <> @@ -14, +16 @@ == Bug Reporting Template == - || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is . <
> <
> 4) What happened instead is... <
> <
> I have the following extensions installed: lo-menubar, libreoffice-nlpsolver, ... <
> <
> WORKAROUND: Perform the following steps:...|| + || 1) lsb_release -rd <
> <
> 2) apt-cache policy <
> <
> apt-show-versions -r libreoffice* <
> <
> 3) What is expected to happen in Writer is . <
> <
> 4) What happened instead is... <
> <
> I have the following extensions installed: lo-menubar... <
> <
> WORKAROUND: Perform the following steps:...|| + /!\ Please note the above 1) and 2) are terminal commands to execute, and post the results of when initially filing your bug report. Failure to follow this format will delay in your bug getting addressed as soon as possible. As well, you may need to install the package [[https://launchpad.net/ubuntu/+source/apt-show-versions|apt-show-versions]]. * Please do not stack multiple issues into one bug. * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. Especially, if you have not completed the relevant, below mentioned debugging procedures, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.