Responses

Differences between revisions 24 and 25
Revision 24 as of 2006-04-28 15:24:58
Size: 4830
Editor: 84
Comment:
Revision 25 as of 2006-04-29 19:59:44
Size: 4904
Editor: ottawa-hs-64-26-167-206
Comment: Word-wrap at 78 characters
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
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. Thanks for taking the time to report this bug. Unfortunately, we are not able
to fix and find the bug because your description of the bug didn't have
enough information in it. You may find it helpful to read "How to report
bugs effectively", http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
We'd be grateful if you would then provide a more complete description of the
problem.
Line 11: Line 16:
Debugging procedures for certain types of problems can be found at http://wiki.ubuntu.com/DebuggingProcedures Debugging procedures for certain types of problems can be found at
http://wiki.ubuntu.com/DebuggingProcedures
Line 15: Line 21:
Your bug lacks information we would need to investigate further. We are now going to close the bug - please reopen if you have more information at hand. Your bug lacks information we would need to investigate further. We are now
going to close the bug - please reopen if you have more information at hand.
Line 20: Line 27:
Thanks for the bug report. However, the version you are using is no longer maintained. Thanks for the bug report. However, the version you are using is no longer
maintained.
Line 22: Line 30:
Please upgrade to the most recent version, and open a new bug if the problem persists. Please upgrade to the most recent version, and open a new bug if the problem
persists.
Line 27: Line 36:
Thanks for your bug report. Could you please try to obtain a backtrace by following the instructions on http://wiki.ubuntu.com/DebuggingProgramCrash - thanks. Thanks for your bug report. Could you please try to obtain a backtrace by
following the instructions on http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.
Line 32: Line 43:
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 which you find. 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 which you find.
Line 36: Line 49:
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers do need more information to fix the bug. Could you please answer the questions which are in the other report? Thanks for the bug report. This particular bug has already been reported
into our bug tracking system, but the maintainers do need more information
to fix the bug. Could you please answer the questions which are in the other
report?
Line 41: Line 57:
Thanks for your bug report. This particular bug has been filed with the developers of the software. You can track this and make comments here: Thanks for your bug report. This particular bug has been filed with the
developers of the software. You can track this and make comments here:
Line 49: Line 66:
Line 50: Line 68:
If you need a fix for this bug in Breezy, please follow the instructions in the "How to request new packages" section of the Backports wiki page:
If you need a fix for this bug in Breezy, please follow the instructions in
the "How to request new packages" section of the Backports wiki page:
Line 56: Line 76:
Line 57: Line 78:
Line 58: Line 80:
See https://wiki.ubuntu.com/UbuntuBackports for more informations. See https://wiki.ubuntu.com/UbuntuBackports for more information.
Line 63: Line 85:
Thanks for your bug report. To maintain a respectful atmosphere, please be sure to follow http://www.ubuntu.com/community/conduct/ - conversations in bugs are done by humans, so please bear this in mind. Thanks for your bug report. To maintain a respectful atmosphere, please be
sure to follow http://www.ubuntu.com/community/conduct/ - conversations in
bugs are done by humans, so please bear this in mind.
Line 68: Line 92:
Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you would submit a specification for this. You should first check whether it already exists at the Ubuntu specs page (https://launchpad.net/distros/ubuntu/+specs) in Launchpad. If that is the case, feel free to contact the drafter of that spec about your comments/suggestions. Otherwise you can start writing a spec following the steps described in https://wiki.ubuntu.com/FeatureSpecifications. Thanks for your report. Your idea might get more attention and have the
possibility of being implemented if you would submit a specification for this.
You should first check whether it already exists at the Ubuntu specs page
(https://launchpad.net/distros/ubuntu/+specs) in Launchpad. If that is the case,
feel free to contact the drafter of that spec about your comments/suggestions.
Otherwise you can start writing a spec following the steps described in
https://wiki.ubuntu.com/FeatureSpecifications.
Line 73: Line 103:
Thanks for your comments. This does not appear to be bug related. We appreciate the difficulties you are facing, however it might make more sense to raise your question at http://launchpad.net/support - I will close the bug here and thank you for taking care. Thanks for your comments. This does not appear to be bug related. We appreciate
the difficulties you are facing, however it might make more sense to raise your
question at http://launchpad.net/support.

I will close the bug here and thank you for taking care.
Line 78: Line 112:
Thanks for your comment. The changes you are requesting require more discussion and should rather be done on an appropriate mailing list or forum. http://www.ubuntu.com/community/forums/ might be a good start. Thanks for your comment. The changes you are requesting require more discussion
and should rather be done on an appropriate mailing list or forum.
http://www.ubuntu.com/community/forums/ might be a good start.
Line 83: Line 119:
Thanks for your comment. Ubuntu gets its translations from http://launchpad.net/rosetta - this is the place where translation teams actively work on making Ubuntu more useful in their language. If you want to change a certain text, Rosetta is the right place for it. Thanks for your comment. Ubuntu gets its translations from
http://launchpad.net/rosetta. This is the place where translation teams actively
work on making Ubuntu more useful in their language. If you want to change a
certain text, Rosetta is the right place for it.
Line 88: Line 127:
Thanks for your suggestion. This is not the right place to request new software. Please add your suggestion to http://wiki.ubuntu.com/UniverseCandidates - thanks a lot. Thanks for your suggestion. This is not the right place to request new software.
Please add your suggestion to http://wiki.ubuntu.com/UniverseCandidates.

Standard Responses

The following standard responses can be used when replying to bug reports:

If the bug is not described well

Thanks for taking the time to report this bug. Unfortunately, we are not able
to fix and find the bug because your description of the bug didn't have
enough information in it.  You may find it helpful to read "How to report
bugs effectively", http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
We'd be grateful if you would then provide a more complete description of the
problem.

Debugging procedures for certain types of problems can be found at
http://wiki.ubuntu.com/DebuggingProcedures

or in case of aged NeedsInfo bugs

Your bug lacks information we would need to investigate further. We are now
going to close the bug - please reopen if you have more information at hand.

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 has no back trace

Thanks for your bug report. Could you please try to obtain a backtrace by
following the instructions on http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.

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 which you find.

OR

Thanks for the bug report. This particular bug has already been reported
into our bug tracking system, but the maintainers do need more information
to fix the bug. Could you please answer the questions which are 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 track this and make comments here:

If the bug is fixed in Dapper but still exist in Breezy

If the package can be backported:

Thanks for the bug report.

I'm closing this bug because it has been fixed in Dapper.

If you need a fix for this bug in Breezy, please follow the instructions in
the "How to request new packages" section of the Backports wiki page:
https://wiki.ubuntu.com/UbuntuBackports

If not:

Thanks for the bug report.

I'm closing this bug because it has been fixed in Dapper.

It won't be fixed in Breezy since this bug doesn't fit backports requirements.
See https://wiki.ubuntu.com/UbuntuBackports for more information.

If people are not respecting the Code of Conduct

Thanks for your bug report. To maintain a respectful atmosphere, please be 
sure to follow http://www.ubuntu.com/community/conduct/ - 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 have the
possibility of being implemented if you would submit a specification for this.
You should first check whether it already exists at the Ubuntu specs page
(https://launchpad.net/distros/ubuntu/+specs) in Launchpad. If that is the case,
feel free to contact the drafter of that spec about your comments/suggestions.
Otherwise you can start writing a spec following the steps described in
https://wiki.ubuntu.com/FeatureSpecifications.

If the bug is a support request

Thanks for your comments. This does not appear to be bug related. We appreciate
the difficulties you are facing, however it might make more sense to raise your
question at http://launchpad.net/support.

I will 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 you are requesting require more discussion
and should rather be done on an appropriate mailing list or forum.
http://www.ubuntu.com/community/forums/ might be a good start.

If the bug points out that a translation is wrong

Thanks for your comment. Ubuntu gets its translations from
http://launchpad.net/rosetta. This is the place where translation teams actively
work on making Ubuntu more useful in their language. If you want to change a
certain text, Rosetta is the right place for it.

If it's a packaging request of new software

Thanks for your suggestion. This is not the right place to request new software.
Please add your suggestion to http://wiki.ubuntu.com/UniverseCandidates.

Other projects have standard responses as well:


Back to HelpingWithBugs

Bugs/Responses (last edited 2025-09-18 13:12:42 by sally-makin)