- 1 Stock Bugzilla Responses
- 1.1 Introduction
- 1.2 No stack trace
- 1.3 No debug symbols
- 1.4 Incomplete report
- 1.5 Incomplete crasher
- 1.6 Duplicate
- 1.7 Two or more issues per report
- 1.8 Incorrect Component
- 1.9 Fixed in CURRENTRELEASE
- 1.10 Upstreaming
- 1.11 Upstreaming Duplicate
- 1.12 End of Life (EOL) product
- 1.13 Unsupported Components
- 1.14 Nvidia Driver
- 1.15 Unanswered NEEDINFO bugs
- 1.16 X Server Problems
Stock Bugzilla Responses
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.
No stack trace
If the bug is a crasher and no stack trace is provided in the report.
Thank you for the bug report. 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.
As an additional hint, you can tell the reporter to install yum-utils and use debuginfo-install <rpm> which will install the necessary debuginfo RPM's
No debug 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 issue: Please see http://fedoraproject.org/wiki/StackTraces for more information about stack traces.
If the bug is not described well
Thank you 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 http://fedoraproject.org/wiki/BugsAndFeatureRequests and add a more useful description to this bug. Thank you.
If the bug is a crasher and not described well
Thank you 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 http://fedoraproject.org/wiki/BugsAndFeatureRequests and add a more useful description to this bug. You'll also need to add a stack trace; please make sure you have debuginfo packages installed and see http://fedoraproject.org/wiki/StackTraces for more information about getting a useful stack trace. Thank you.
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. However, this bug report isn't very useful because it contains more than one issue. If you have time and can still reproduce the bug (or bugs), please submit them as separate bugs for each of your separate issues. This is even recommended in the bug writing guidelines: https://bugzilla.redhat.com/page.cgi?id=bug-writing.html Thank you.
If the bug has been reported to the incorrect component
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, 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. Please feel free to report any further bugs you find. You can obtain the updated package by typing 'yum update <package>' or using the graphical updater, Software Update.
The bug is not a packaging bug, you have 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://bugs.freedesktop.org/||Freedesktop apps, including Xorg|
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
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.
The bug is not a packaging bug, you have 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 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 no longer maintains this version of Fedora. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to CLOSED:WONTFIX
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. Kindly post in Fedora community support forums or mailing list or consider using a commercially supported product
Should we include a line about commercial products or specifically RHEL?
Specifically for bugs concerning the proprietary nvidia driver, the following detailed response can be given
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).
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. Thank you in advance.
X Server Problems
Suggested text for bugs relating to Xorg's X11 Server. Thanks to mcepl for this. Updated as per airlied suggestions.
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 dmesg output to the bug report as individual uncompressed 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.