Stock responses for incomplete bugs

As of Bugzilla 2.20 we now have the opportunity to have the stock responses pasted at once into the comment text field. Hence this page is mostly obsolete. If you have bugedit permissions you should see the paste buttons just beneath the text input box, if the bug has the status UNCONFIRMED or NEEDINFO.

Here are some responses to cut and paste into bugzilla for common situations. The whole lot is available as a text file to download.

When changing the stock responses please file a bug here to ensure bugzilla.gnome.org is updated as well. This is needed as the stock responses are now integrated into bugzilla.gnome.org, but must be updated manually.

If the bug is a crasher and no stack trace is provided

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

If the bug is not described well

If the bug is not described well and it's a crasher

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read https://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so.
Thanks in advance!

If the stack trace is incomplete or without debugging symbols

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

If the bug is in an obsolete version of the application

Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.

If the bug hasn't been touched for more than a year AND its status is UNCONFIRMED AND It is not an enhancement bug

This stock response has to be incorporated by bugzilla, see 591222.

This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it.
Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field?

Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE after 6 weeks.

If the stack trace indicates a mozilla crash

Thanks for taking the time to report this bug.
This trace indicates that Mozilla (which was being used by the program) was responsible for the crash, or alternatively that the program was compiled against a different version of Mozilla. Make sure the program was built against the most recent mozilla, and if you can duplicate the crash in mozilla itself, report the bug to http://bugzilla.mozilla.org/

If the bug is not GNOME

Thanks for taking the time to report this bug.
However, this application does not track its bugs in the GNOME bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!

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.

Thanks for taking the time to report this bug.
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 in order to help the developers?

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

AND remember to change the summary of the original bug to include keywords or a better way to explain the problem from the duped bug, in order to prevent more duplicates.

NEEDINFO bugs without a response from submitter

If, after 6 weeks, the reporter still hasn't responded, the bug status should be changed to "RESOLVED" and the resolution to "INCOMPLETE" with a comment similar to:

Closing this bug report as no further information has been provided after more than 6 weeks. Please feel free to reopen this bug if you can provide the information asked for. Thanks!

Evince rendering bug, missing concerned file and poppler version

Thanks for the bug report. Unfortunately it lacks some information that may help us in finding the cause of the bug. Can you, if possible, attach the file causing the crash? Also this may be a Poppler Bug (the backend used by Evince to render PDF), could you please supply the poppler version and type? You can find it in the Help->About menu in Evince.