Responses
|
Size: 3192
Comment:
|
Size: 14728
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Responses == | These standard responses can be used when replying to a bug report if it is ... |
| Line 3: | Line 3: |
| '''If the bug is not described well''' | [[TableOfContents]] |
| Line 5: | Line 5: |
| 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. | == Not described well == |
| Line 7: | Line 7: |
| Debugging procedures for certain types of problems can be found at http://wiki.ubuntu.com/DebuggingProcedures | ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. 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.[[BR]][[BR]] We have instructions on debugging some types of problems. http://wiki.ubuntu.com/DebuggingProcedures [[BR]][[BR]]At a minimum, we need:[[BR]]1. the specific steps or actions you took that caused you to encounter the problem,[[BR]]2. the behavior you expected, and[[BR]]3. the behavior you actually encountered (in as much detail as possible).[[BR]]Thanks! || == Need Steps to Recreate Bug == ||<tablestyle="background-color: #eee">Thank you for taking the time to report this bug and helping to make Ubuntu better. Also, please answer these questions:[[BR]][[BR]]* Is this crash reproducible?[[BR]]* If so, what specific steps should we take to recreate this bug?[[BR]][[BR]]This will greatly aid us in tracking down your problem and resolving this bug.|| === Debugging kernel general === ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.[[BR]][[BR]]Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team: [[BR]]1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.[[BR]]2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report. [[BR]]3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.[[BR]][[BR]]For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance! || or === Debugging Sound Problems === ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.[[BR]][[BR]]Please include the information requested from https://help.ubuntu.com/community/DebuggingSoundProblems as separate attachments.|| or === Debugging ACPI === ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.[[BR]][[BR]]Please include the information requested from https://wiki.ubuntu.com/DebuggingACPI as separate attachments.|| or === Debugging Removable Devices === ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.[[BR]][[BR]]Please include the information requested from https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.|| or === Debugging Hardware Detection === ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.[[BR]][[BR]]Please include the information requested from https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.|| or === Debugging USB Storage === ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.[[BR]][[BR]]Please include the information requested from https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.|| or === Debugging XAutoconfiguration === ||<tablestyle="background-color: #eee">Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.[[BR]][[BR]]Please include the information requested from https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments.|| == Incomplete bugs without a response from submitter == A bug that has been in the "Incomplete" state, meaning it does not have enough information in it, for more than 4 weeks should be set to "Invalid" and have a comment similar to this inserted. ||<tablestyle="background-color: #eee"> We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.|| == Bugs without a package == Sometimes bug will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a variable. ||<tablestyle="background-color: #eee"> Thanks for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME|| == Missing a crash report == ||<tablestyle="background-color: #eee"> Thanks for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is missing. Could you please add the crash report that you received? It will be found in '/var/crash/'. This will allow us to better troubleshoot your bug. Thanks in advance.|| == A duplicate == ||<tablestyle="background-color: #eee"> Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug NUMBER and is being marked as such. Please look at the other bug report to see if there is any information missing that you can add or to see if there is a work around. Feel free to continue to report any other bugs you may find. || == About an obsolete version of the software == ||<tablestyle="background-color: #eee"> Thanks for taking the time to report this bug and helping to make Ubuntu better. However, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. || == Missing a back trace == ||<tablestyle="background-color: #eee"> Thanks for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. || == Need valgrind log == ||<tablestyle="background-color: #eee"> Thanks for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem. || == A bug that should be handled upstream == ||<tablestyle="background-color: #eee"> Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: || == Beryl and beryl related bugs == Beryl is now included in universe for Feisty. However, some users may be using packages from other repositories. So the first step will be to find out which package version they have installed. In the event that it is not from the Ubuntu repository the bug should be set to '''Invalid'''. ||<tablestyle="background-color: #eee">Thanks for taking the time to report this bug and helping to make Ubuntu better. However, this beryl package is not from the official Ubuntu repositories, and as such is not supported here. Please report this bug upstream at http://www.opencompositing.org . Thanks! || == Packages not provided by Ubuntu == Occasionally, bug reporters will report a bug about a version of a package not provided by Ubuntu or even about software not provided by Ubuntu. In which case we can not help them and the bug should be set to '''Invalid'''. ||<tablestyle="background-color: #eee">Thanks for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! [[BR]][[BR]]If you are interested in learning more about software repositories and Ubuntu the following pages should be informative:[[BR]][[BR]]1. http://www.ubuntu.com/community/ubuntustory/components - information about Ubuntu repositories[[BR]]2. https://help.ubuntu.com/community/Repositories - information regarding managing repositories|| == Fixed in Gutsy while still existing in Feisty or Edgy == The bug's state should become '''Fix Released''' and if the package can be backported: ||<tablestyle="background-color: #eee"> Thanks 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 - the Gutsy Gibbon.[[BR]][[BR]] If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages . || The bug's state should become '''Fix Released''' and if the package can not be backported: ||<tablestyle="background-color: #eee"> Thanks 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 - the Gutsy Gibbon. It won't be fixed in previous versions of Ubuntu because the bug doesn't fit requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information. || == Reported by someone not respecting the Code of Conduct == ||<tablestyle="background-color: #eee"> Thanks for your bug report. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. || == A non-trivial feature request == For work that needs planning: ||<tablestyle="background-color: #eee"> 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 || == A support request == Determining whether a bug report is actually a support request can be quite challenging but when it is mark the bug as '''Invalid'''. ||<tablestyle="background-color: #eee"> 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/ubuntu || === Suspected bad ISO download === ||<tablestyle="background-color: #eee"> Thanks for your comments. We appreciate the difficulties you are facing, but it would appear that the CD image (ISO file) you downloaded could be corrupt. There is an easy way to verify the integrity of the Ubuntu ISO files you download. For more information, please visit https://help.ubuntu.com/community/HowToMD5SUM || == A suggestion for changing defaults == ||<tablestyle="background-color: #eee"> Thanks for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use. || == About an incorrect translation == ||<tablestyle="background-color: #eee"> Thanks for your comment. Ubuntu gets its translations from the translations portion of Launchpad (http://translations.launchpad.net/ubuntu/), where translation teams work on making Ubuntu more useful in their language. If you want to change a translation in Ubuntu, [http://translations.launchpad.net/ubuntu/ Rosetta] is the right place. || == Ubiquity == ||<tablestyle="background-color: #eee">Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.[[BR]][[BR]]Please include the information requested from https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments.|| |
| Line 10: | Line 135: |
| '''If the bug is in an obsolete version of the application''' Thanks for the bug report. However, the version you are using is no longer maintained. Please upgrade to the most recent version, and open a new bug if the problem persists. '''If the bug is a duplicate''' Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. OR Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report? '''If the bug report needs to go upstream''' Thanks for your bug report. This particular bug has been filed with the developers of the software. You can see and make comments here: '''If it is a Universe Bug posted in Bugzilla''' Thanks for your bug report. However, <package name> is a part of the 'universe' component, so its bugs are not currently tracked in this system. Bugs for these packages should be reported to Malone: https://launchpad.ubuntu.com/malone/distros/ubuntu For more information about universe packages, contact the MOTU team: https://wiki.ubuntu.com/MOTU '''If people are not respecting the Code of Conduct''' Thanks for your bug report. To improve the overall atmosphere, please be sure to respect http://www.ubuntulinux.org/community/conduct/document_view - conversations in bugs are done by humans, so please bear this in mind. '''If the bug is a feature request''' Thanks for your report. Your idea might get more attention and would rather be implemented, if you would start writing a specification (https://wiki.ubuntu.com/SpecTemplate might be a start) and add it to http://launchpad.net/specs - the more detailed your specification is, the easier it will be for the appropriate developer to implement it. Thanks for taking care of this. '''If the bug is a support request''' Thanks for your comments. We appreciate the difficulties you are facing, it just might make more sense to raise your question at http://launchpad.net/support - I will the close the bug here and thank you for taking care. '''If the bug is a suggestion for changing defaults''' Thanks for your comment. The changes your ask for require more discussion and should rather be done on an appropriate mailing list. ubuntu-devel@lists.ubuntu.com might be a good start. |
== Firefox == ||<tablestyle="background-color: #eee">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 upload the crash report from /var/crash/.[[BR]][[BR]]Also, please answer these questions:[[BR]]Is this crash reproducible? If so, which are the steps that lead to it?[[BR]]Which flash package do you have installed?[[BR]]Which Java package do you have installed?[[BR]]Which firefox extensions do you have installed?[[BR]][[BR]]This will greatly aid us in tracking down your problem.|| |
| Line 62: | Line 141: |
| Other projects have Stock responses as well: | Other projects have standard responses as well: |
| Line 64: | Line 143: |
| * http://live.gnome.org/Bugsquad_2fTriageGuide_2fStockResponses | * http://live.gnome.org/Bugsquad/TriageGuide/StockResponses * https://wiki.ubuntu.com/MozillaTeam/Bugs/Triage/Responses ---- Back to '''["HelpingWithBugs"]'''.[[BR]][[BR]] [:CategoryBugSquad] |
These standard responses can be used when replying to a bug report if it is ...
Not described well
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. 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.BRBR We have instructions on debugging some types of problems. http://wiki.ubuntu.com/DebuggingProcedures BRBRAt a minimum, we need:BR1. the specific steps or actions you took that caused you to encounter the problem,BR2. the behavior you expected, andBR3. the behavior you actually encountered (in as much detail as possible).BRThanks! |
Need Steps to Recreate Bug
Thank you for taking the time to report this bug and helping to make Ubuntu better. Also, please answer these questions:BRBR* Is this crash reproducible?BR* If so, what specific steps should we take to recreate this bug?BRBRThis will greatly aid us in tracking down your problem and resolving this bug. |
Debugging kernel general
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.BRBRPlease include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team: BR1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.BR2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report. BR3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.BRBRFor your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance! |
or
Debugging Sound Problems
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from https://help.ubuntu.com/community/DebuggingSoundProblems as separate attachments. |
or
Debugging ACPI
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from https://wiki.ubuntu.com/DebuggingACPI as separate attachments. |
or
Debugging Removable Devices
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments. |
or
Debugging Hardware Detection
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments. |
or
Debugging USB Storage
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments. |
or
Debugging XAutoconfiguration
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments. |
Incomplete bugs without a response from submitter
A bug that has been in the "Incomplete" state, meaning it does not have enough information in it, for more than 4 weeks should be set to "Invalid" and have a comment similar to this inserted.
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. |
Bugs without a package
Sometimes bug will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a variable.
Thanks for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME |
Missing a crash report
Thanks for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is missing. Could you please add the crash report that you received? It will be found in '/var/crash/'. This will allow us to better troubleshoot your bug. Thanks in advance. |
A duplicate
Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug NUMBER and is being marked as such. Please look at the other bug report to see if there is any information missing that you can add or to see if there is a work around. Feel free to continue to report any other bugs you may find. |
About an obsolete version of the software
Thanks for taking the time to report this bug and helping to make Ubuntu better. However, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. |
Missing a back trace
Thanks for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. |
Need valgrind log
Thanks for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem. |
A bug that should be handled upstream
Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: |
Beryl and beryl related bugs
Beryl is now included in universe for Feisty. However, some users may be using packages from other repositories. So the first step will be to find out which package version they have installed. In the event that it is not from the Ubuntu repository the bug should be set to Invalid.
Thanks for taking the time to report this bug and helping to make Ubuntu better. However, this beryl package is not from the official Ubuntu repositories, and as such is not supported here. Please report this bug upstream at http://www.opencompositing.org . Thanks! |
Packages not provided by Ubuntu
Occasionally, bug reporters will report a bug about a version of a package not provided by Ubuntu or even about software not provided by Ubuntu. In which case we can not help them and the bug should be set to Invalid.
Thanks for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! BRBRIf you are interested in learning more about software repositories and Ubuntu the following pages should be informative:BRBR1. http://www.ubuntu.com/community/ubuntustory/components - information about Ubuntu repositoriesBR2. https://help.ubuntu.com/community/Repositories - information regarding managing repositories |
Fixed in Gutsy while still existing in Feisty or Edgy
The bug's state should become Fix Released and if the package can be backported:
Thanks 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 - the Gutsy Gibbon.BRBR If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages . |
The bug's state should become Fix Released and if the package can not be backported:
Thanks 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 - the Gutsy Gibbon. It won't be fixed in previous versions of Ubuntu because the bug doesn't fit requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information. |
Reported by someone not respecting the Code of Conduct
Thanks for your bug report. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. |
A non-trivial feature request
For work that needs planning:
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 |
A support request
Determining whether a bug report is actually a support request can be quite challenging but when it is mark the bug as Invalid.
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/ubuntu |
Suspected bad ISO download
Thanks for your comments. We appreciate the difficulties you are facing, but it would appear that the CD image (ISO file) you downloaded could be corrupt. There is an easy way to verify the integrity of the Ubuntu ISO files you download. For more information, please visit https://help.ubuntu.com/community/HowToMD5SUM |
A suggestion for changing defaults
Thanks for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use. |
About an incorrect translation
Thanks for your comment. Ubuntu gets its translations from the translations portion of Launchpad (http://translations.launchpad.net/ubuntu/), where translation teams work on making Ubuntu more useful in their language. If you want to change a translation in Ubuntu, [http://translations.launchpad.net/ubuntu/ Rosetta] is the right place. |
Ubiquity
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments. |
Firefox
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 upload the crash report from /var/crash/.BRBRAlso, please answer these questions:BRIs this crash reproducible? If so, which are the steps that lead to it?BRWhich flash package do you have installed?BRWhich Java package do you have installed?BRWhich firefox extensions do you have installed?BRBRThis will greatly aid us in tracking down your problem. |
Links
Other projects have standard responses as well:
Back to ["HelpingWithBugs"].BRBR [:CategoryBugSquad]
Bugs/Responses (last edited 2024-07-16 20:51:28 by paulw2u)