BugZappers/StockBugzillaResponses

Stock Bugzilla Responses

Introduction

Bugzilla is used by the Fedora Project to track bugs in the code and general things that need to be fixed to make Fedora better. Many bug reports in bugzilla lack sufficient information needed to assist the developer in fixing them.

To increase the speed of requesting missing information we have created a page of stock responses. This helps bug triagers and developers request missing information quickly in a clear, friendly, and consistent manner.

Feel free to add your own stock replies, or improve the ones here if you like.

Use the word maintained instead of supported as this causes confusion about the availability of commercical support or service level agreements.

Much of the text from this page comes from the Gnome bugsquad stock responses page.

Triager Signature

If you don't have GreaseMonkey installed, you can manually add this to the bottom of your comments to indicate you are 1.) a volunteer and 2.) not the package maintainer. This helps avoid misunderstandings with reporters.

---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

No Stack Trace

If the bug is a crasher and no stack trace is provided in the report.

Thank you for the bug report. Unfortunately, without a stack trace from the crash it is impossible to determine what caused the crash. Please see http://fedoraproject.org/wiki/StackTraces for more information about getting a useful stack trace with debugging symbols. Even if you cannot reproduce this crash at will, you can prepare your system now to produce a good stack trace the next time you experience the crash. Thank you.

As an additional hint, you can tell the reporter to install yum-utils and use "debuginfo-install RPMNAMEHERE" which will install the necessary debuginfo RPMs.

No Debugging Symbols

If the stack trace is incomplete or without debugging symbols.

Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there is not a symbolic stack trace. In order to get a symbolic stack trace, the appropriate debuginfo packages need to be installed. In order to accomplish this, you can run the command:

debuginfo-install PROGRAMNAMEHERE

Please see http://fedoraproject.org/wiki/StackTraces for more information about stack traces.

Incomplete Report

If the bug is not described well:

Thank you for taking the time to report this bug. Unfortunately, we do not understand the problem you are having. If you have time and can still reproduce the bug, please read http://fedoraproject.org/wiki/BugsAndFeatureRequests and add a description along those lines to this bug report so we can diagnose the problem. Thank you.

If you can be more specific than this stock response, that would be very helpful for the reporter and also more polite.

Duplicate

If the bug is a duplicate of another bug.

Thank you 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.

Two or more issues per report

Thank you for taking the time to report this bug. In order to provide suitable tracking of bugs, the bug writing guidelines (https://bugzilla.redhat.com/page.cgi?id=bug-writing.html) ask that reporters file one bug per issue. It appears that this bug contains multiple issues. If you have time and can still reproduce the bug (or bugs), please submit them as separate bugs for each of your separate issues. One bug can remain in this report; simply edit the summary to reflect this. You can note the new bug numbers in a comment for this bug.

Thank you.

If it is not obvious how the problems are different, a more detailed explanation would be polite. This is not always obvious to non-programmers, and even for experts sometimes figuring this out requires reading the source code.

Incorrect Component

If the bug has been reported to the incorrect component, you can use this message inserting the appropriate component names:

Thank you for the report. However this has been reported to the incorrect component. Reassigning from <oldcomponent> to <newcomponent>. Feel free to report any further bugs you find to our bug tracking system.

In the future, in order to find the correct component, you can refer to: http://fedoraproject.org/wiki/BugZappers/CorrectComponent

Make sure you click on "Reassign bug to owner and QA contact of selected component" choice in the bottom of the report before you submit this component change.

Fixed in CURRENTRELEASE

If the bug is fixed and there is a updated package:

Thank you for the bug report. This particular bug was fixed and a update package was published for download for this Fedora release.

You can obtain the updated package by typing 'yum update <package>' or using the graphical updater, Software Update. Please feel free to report any further bugs you find, or make further reports if this bug is not fixed after you install the update.

Upstreaming

The bug is not a packaging bug, the package maintainer has no plans to work on this in the near future, and there is an upstream bug tracking system other than the Red Hat Bugzilla.

Thank you for the bug report. At the moment, the Fedora developers are busy fixing other issues and may not have time to work on this one. The best way to make sure your problem will get looked on is to report it to the authors of the program. Most upstream authors use a bug tracking system like Bugzilla, and more people who know the code will be looking at the bug report there.

The upstream bug tracking system to use is:

LINK HERE

You are requested to add the bugzilla link here for tracking purposes. Please make sure the bug isn't already in the upstream bug tracker before filing it.

Then add a link to the upstream bug tracker system. Here is a list of some common bug tracking systems:

http://bugzilla.gnome.org/	Gnome
http://bugs.kde.org/	KDE
https://bugzilla.mozilla.org/	Mozilla
http://bugs.freedesktop.org/	Freedesktop apps, including Xorg
http://qa.openoffice.org/issue_handling/project_issues.html	OpenOffice

Evolution (together with evolution-data-server, gtkhtml3, libgal2, libsoup and the connector) was originally tracked upstream at http://bugzilla.ximian.com/ but as of April 9th 2005 the public bugs there were moved to http://bugzilla.gnome.org/. Bug numbers were changed according to the formula: new_bgo_bug_number = old_bxc_bug_number + 200000 Bugzilla.ximian.com will now redirect show_bug.cgi queries for bugs in the migrated products to bugzilla.gnome.org. Bug-buddy mails sent to bugzilla.ximian.com are automatically forwarded to bugzilla.gnome.org as well.

If you think its important you can even file the bug upstream and add a link to the upstream bug report. Then you could use something like:

Thank you for the bug report. At the moment, the Fedora developers don't have time to work on this particular issue. The best way to make sure your problem will get looked on is to report it to the authors of the program. Most upstream authors use a bug tracking system like Bugzilla, and more people who know the code will be looking at the bug report there.

I have filed this bug for you at:

LINK HERE

If you want to follow what happens to the bug, you can add yourself to the upstream report.

Upstreaming Duplicate

The bug is not a packaging bug, the package maintainer has no plans to work on this in the near future, and there is an upstream bug for this already.

Thank you for the bug report. This particular bug has already been reported to the author of the software, and the Fedora developers don't plan to work on it at the moment. You can help out by adding any helpful additional information you have to the upstream bug report at:

LINK HERE

If you want to follow what happens to the bug, you can add yourself to the upstream report.

End of Life (EOL) product

The bug is reported against a version of Fedora that is no longer maintained.

Thank you for your bug report.

We are sorry, but the Fedora Project is no longer releasing bug fixes or any other updates for this version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora, which is available from:

http://fedoraproject.org/get-fedora

Unsupported Components

If reports are being made to ship proprietary or restricted components or issues are beyond the control of the Fedora Project, the following response can be given

Thank you for the bug report. However, Fedora Project only ships and maintains Free and Open Source software. Issues such as these are beyond the control of Fedora developers.

You may find assistance in the Fedora community support forums or mailing list, or you might consider using a commercially supported product.

Nvidia Driver

Specifically for bugs concerning the proprietary nvidia driver, the following detailed response can be given. This is not intended for the open source xf86-video-nouveau driver.

Thank you for the report. Fedora does not provide or support proprietary drivers. For users who are experiencing problems installing, configuring, or using the unsupported 3rd party proprietary "nvidia" video driver, Nvidia provides indirect customer support via an online web based support forum. Nvidia monitors these web forums for commonly reported problems and passes them on to Nvidia engineers for investigation. Once they've isolated a particular problem, it is often fixed in a future video driver update.

The NVNews Nvidia Linux driver forum is located at:

http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14

Once you have reported this issue in the Nvidia web forums, others who may have experienced the particular problem may be able to assist. If there is a real bug occurring, Nvidia will be able to determine this, and will likely resolve the issue in a future driver update for the operating system releases that they officially support.

While Fedora does not support the proprietary Nvidia driver, users requiring technical help may also find the various X.Org and Fedora mailing lists helpful in finding assistance:

X.Org mailing lists:

http://www.freedesktop.org/XOrg/XorgMailingLists

Fedora mailing lists:

http://fedoraproject.org/wiki/Communicate#ML

Setting status to "CANTFIX" (unsupported).

ATI/AMD fglrx Driver

For bugs concerning the proprietary fglrx driver:

Thank you for the report. Fedora does not provide or support proprietary drivers. For users who are experiencing problems installing, configuring, or using the unsupported 3rd party proprietary "fglrx" video driver, ATI/AMD may provide technical support at: http://support.amd.com/

While Fedora does not support the proprietary fglrx driver, users requiring technical help may also find the various X.Org and Fedora mailing lists helpful in finding assistance:

X.Org mailing lists:

http://www.freedesktop.org/XOrg/XorgMailingLists

Fedora mailing lists:

http://fedoraproject.org/wiki/Communicate#ML

Setting status to "CANTFIX" (unsupported).

Unanswered NEEDINFO bugs

A suggested text for bugs relating to old versions of Fedora that are no longer supported or that have been in a NEEDINFO state for more than thirty (30) days:

The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem.

Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.

X Server Problems

Suggested text for bugs related to Xorg's X11 Server.

Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf), X server log file (/var/log/Xorg.*.log) and the output of "dmesg" to the bug report as individual uncompressed text/plain file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thank you in advance.

KMS/Radeon Problems

Suggested text for bugs related to KMS/Radeon problems.

Could you please try the following test :

First, boot into runlevel 3 by adding this to the kernel command line :

3

and then run the following commands :

modprobe -r radeon drm

modprobe drm debug=1

modprobe radeon modeset=1

At this point, please save dmesg and add it to this bug if at all possible.

init 5

At this point, please upload Xorg.0.log (ssh'ing to the machine if at all possible). Any partially run test is useful if you can get the logs.

Request for a package to be added to Fedora

If the bug is requesting a particular package to be added to Fedora.

Thank you for your bug report. Requests for packaging are kept at: https://fedoraproject.org/wiki/Package_maintainers_wishlist

Please add this package to this list if it isn't there already. Setting this report to CLOSED:NOTABUG.