Responses

Differences between revisions 37 and 38
Revision 37 as of 2007-01-18 08:29:52
Size: 5014
Editor: 121-72-135-240
Comment: floating ToC and preformatted responses don't mix
Revision 38 as of 2007-01-18 08:34:03
Size: 4900
Editor: 121-72-135-240
Comment: refactors headings to shorten them
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
These standard responses can be used when replying to bug reports: These standard responses can be used when replying to a bug report if it is ...
Line 7: Line 7:
== If the bug is not described well == == Not described well ==
Line 25: Line 25:
== If the bug is in an obsolete version of the application == == About an obsolete version of the software ==
Line 34: Line 34:
== If the bug has no back trace == == Missing a back trace ==
Line 42: Line 42:
== If the bug is a duplicate == == A duplicate ==
Line 56: Line 56:
== If the bug report needs to go upstream == == One that should be reported upstream ==
Line 63: Line 63:
== If the bug is fixed in Feisty but still exist in Edgy == == Fixed in Feisty while still existing in Edgy ==
Line 87: Line 87:
== If people are not respecting the Code of Conduct == == Reported by someone not respecting the Code of Conduct ==
Line 95: Line 95:
== If the bug is a feature request == == A feature request ==
Line 109: Line 109:
== If the bug is a support request == == A support request ==
Line 117: Line 117:
== If the bug is a suggestion for changing defaults == == A suggestion for changing defaults ==
Line 126: Line 126:
== If the bug points out that a translation is wrong == == About an incorrect translation ==
Line 134: Line 134:
== If it's a packaging request of new software not already in Debian == == A packaging request for new software not already in Debian ==
Line 147: Line 147:

These standard responses can be used when replying to a bug report if it is ...

TableOfContents

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

Thanks for reporting this bug! Unfortunately your report lacks information we would need to investigate the problem further. We are now going to close the bug - please reopen if you have more information at hand.

About an obsolete version of the software

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.

Missing a 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.

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? 

One that should be reported 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:

Fixed in Feisty while still existing in Edgy

If the package can be backported:

Thanks for the bug report.

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

If you need a fix for this bug in Edgy, 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 Feisty.

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

Reported by someone 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.

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.

A support request

Thanks for your comments. This does not appear to be a bug report as
such. We appreciate the difficulties you are facing, but it would
make more sense to raise your question at
http://launchpad.net/support.

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.

About an incorrect translation

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.

A packaging request for new software not already in Debian

Thanks for your suggestion. This is not the right place to request new
software. Please add your suggestion to
        https://wiki.ubuntu.com/MOTU/Packages/Candidates

Other projects have standard responses as well:


Back to ["HelpingWithBugs"].BRBR [:CategoryBugSquad]

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