From Fedora Project Wiki

Stock Bugzilla Responses

Introduction

Bugzilla est utilisé par le projet Fedora pour suivre les bogues du code et les choses plus générales qui nécessitent d'être corrigées pour améliorer Fedora. Beaucoup de bogues dans Bugzilla ne sont pas assorti des informations nécessaire au développeur pour les corriger.

Pour faciliter les demandes d'informations manquantes nous avons créé une page de réponses préparées. Cela aide les trieurs de bogues et les développeurs à réclamer l'information manquante dans un langage clair, amical et cohérent.

N'hésitez pas à ajouter vos propres réponses de manière à améliorer celles que vous trouverez ici.


Note.png
Utilisez le mot maintained (maintenu) plutôt que supported (pris en charge) car cela crée une confusion avec la disponibilité d'une assistance ou d'accords de niveau de service commerciaux.
Note.png
La plus grande part du texte de cette page provient de la page des réponses préparées de l'équipe de chasse aux bogues de Gnome .

Signature du trieur

Cette signature est ajoutée automatiquement par l'extension à Firefox sous votre commentaire et explique que vous êtes :

  1. un volontaire,
  2. pas un mainteneur de paquet.

Cela permet d'éviter les malentendus avec les rapporteurs.

---

Fedora Bugzappers volunteer triage team (Chasseur de bogues volontaire de l'équipe de triage)
https://fedoraproject.org/wiki/BugZappers

Pas de trace de pile

Si le bogue provoque un plantage et qu'aucune trace de pile (ou trace d'appels) n'est fournie avec le rapport.

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.
-----
Merci pour votre rapport de bogue. Malheureusement, sans trace de pile au moment du plantage, il est impossible d'en déterminer la cause. Reportez-vous à http://fedoraproject.org/wiki/StackTraces pour savoir comment obtenir une trace de pile utile avec des symboles de débogage. Même si vous ne savez pas comment reproduire ce plantage volontairement, vous pouvez préparer votre système pour qu'il produise une bonne trace de pile la prochaine fois que le plantage surviendra. Merci.

Comme suggestion additionnelle, vous pouvez demander au rapporteur d'installer yum-utils et d'utiliser debuginfo-install <nom du paquet> (en remplaçant <nom du paquet> par le nom du paquet incriminé) qui installera les RPMs nécessaires à l'élaboration des informations de débogage.

Pas de symboles de débogage

Si la trace de pile est incomplete ou sans les symboles de débogage.

Thank you for taking the time to report this crash. Unfortunately, the stack trace is not very useful in determining the cause of the crash, because it lacks debugging symbols. 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.
-----

Merci d'avoir pris le temps de nous signaler ce plantage. Malheureusement la trace de pile fournie n'est pas très utile pour déterminer la cause du plantage, parce qu'elle ne comporte pas les symboles de débogage. Pour obtenir une trace de pile avec ces symboles, les paquets appropriés au débogage doivent être installés. Pour cela, merci d'exécuter la commande :

debuginfo-install <nom du programme>

Reportez-vous à http://fedoraproject.org/wiki/StackTraces pour plus d'information sur les traces de pile


Le message suggéré ci-dessus n'est pas approprié si la trace a été générée automatiquement par un programme tel que ABRT. Dans ce cas, le fait que ABRT n'installe pas les bons paquets de débogage est un bogue d'ABRT. Parce que ABRT est lançé automatiquement en cas de plantage, le rapporteur peut, ou pas, vouloir diagnostiquer le plantage avec des techniques plus compliquées. Dans une telle situation, ce qui suit peut être utile (remplacez PROGRAMNAMEHERE par le composant approprié) :

Thank you for taking the time to report this crash. Unfortunately, the stack trace is not very useful in determining the cause of the crash, because it lacks debugging symbols. This is most likely due to a problem with ABRT or one of the other components it used to automatically generate this report. I am reassigning this bug to ABRT for initial diagnosis.

If you would like to attempt to manually obtain a usable stack trace, please see: http://fedoraproject.org/wiki/StackTraces. If you succeed in doing so, please file a new bug to track the crash fix, since this one will be tracking the fix in ABRT or related component.
-----

Merci d'avoir pris le temps de nous signaler ce plantage. Malheureusement la trace de pile n'est pas très utile pour déterminer la cause du plantage, car elle ne contient pas les symboles de débogage. Cela est vraisemblablement dû à un problème avec ABRT ou avec un des autres composants qu'il utilise pour générer ce rapport automatiquement. Je réassigne le bogue à ABRT pour un diagnostic initial.

Si vous souhaitez essayer d'obtenir une trace de pile utilisable à la main, reportez-vous à http://fedoraproject.org/wiki/StackTraces. En cas de succès, merci de créer un nouveau rapport de bogue pour suivre la correction de ce plantage, car celui-ci ne permettra de suivre que la correction d'ABRT ou des composants en relation avec lui.

Rapport incomplet

Si le bogue n'est pas décrit correctement :

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.
-----
Merci d'avoir pris le temps de rapporter ce bogue. Malheureusement, nous ne comprenons pas le problème que vous rencontrez. Si vous en avez le temps, et que vous pouvez reproduire le bogue, merci de vous reporter à Remplir un rapport de bogue ou une demande d'amélioration et ajoutez une description à ce bogue pour que nous puissions diagnostiquer ce problème. Merci

Si vous pouviez être plus spécifique que cette réponses préparée, ce serait plus utile au rapporteur et également plus poli.

Doublon

Si le bogue fait doublon avec un bogue déjà rapporté :

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.
-----
Merci d'avoir signalé ce bogue. Ce bogue a déjà été rapporté dans notre système de suivi, mais n'hésitez pas à rapporter les autres bogues que vous pourriez découvrir.

Deux problèmes ou plus par bogue

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

Merci d'avoir pris le temps de signaler ce bogue. Afin de permettre un suivi adapté des bogues, les conseils pour la rédaction d'un bogue (https://bugzilla.redhat.com/page.cgi?id=bug-writing.html)invitent les rapporteurs à remplir un rapport de bogue par problème. Il apparaît que ce rapport de bogue évoque de multiples problèmes. Si vous avez le temps, et si vous pouvez reproduire le bogue (ou les bogues), merci de remplir un rapport de bogue par problème séparé. Un des bogues peut rester dans ce rapport, modifiez le sommaire en conséquence. Vous pouvez noter les nouveaux numéros de bogues dans un commentaire à ce bogue.

Merci.

S'il n'est pas évident qu'il s'agit de problèmes différents, une explication plus détaillée serait plus polie. Les choses ne sont pas toujours évidentes pour les non programmeurs, et même parfois pour les experts, cela nécessite de lire le code source.

Composant incorrect

Si le bogue a été atribué à un composant incorrect, vous pouvez utiliser ce message tout en effectuant la correction et en remplaçant dans le message les noms <oldcomponent> et <newcomponent> par les noms réels des composants.

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
-----
Merci d'avoir signalé ce bogue. Néanmoins, ce bogue a été attribué à un composant incorrect. Je réassigne de <ancien composant> à <nouveau composant>. N'hésitez pas à signaler tout nouveau bogue que vos trouveriez dans notre système de suivi.

Assurez-vous de cliquer sur le choix Reassign bug to owner and QA contact of selected component en bas du rapport avant de soumettre ce changement de composant.

Possibly fixed in CURRENTRELEASE

If one or more updates to the package have been released, and no other similar problems have been reported, the bug may no longer exist.

Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update <package>' or using the graphical updater, Software Update.

Fixed in CURRENTRELEASE

If the bug is fixed and there is an 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

Unmaintained Components by Upstream

Upstream no longer maintains this software, the resolution for these reports is CANTFIX

Thank you for your report. This bug is in the <component name>. Fedora does not provide or support this component. We would suggest that you report the problem to the upstream project at <upstream url>, but it does not seem to have been updated since <last date>, so the effort may be wasted. There is unfortunately nothing the Fedora project can do to help you with this problem.

Unsupported Components

If reports are being made to ship proprietary or restricted components or issues that 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 like the "nvidia" video driver.
The open source "nouveau" driver is the recommended alternative. It is used by default in Fedora 11 and later if you remove any customizations that explicitly set the video driver. The older "nv" driver may be needed in some cases. It is also available in older Fedora releases. Install the packages xorg-x11-drv-nouveau or xorg-x11-drv-nv and override the X server's default choice if necessary. See https://fedoraproject.org/wiki/Features/NouveauAsDefault for more information.
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 above called "Add an attachment".
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.

Blocker Bug Addition

When a bug clearly impacts the Fedora Release Criteria, or is considered of sufficient priority/severity to be considered as a release blocker, you may use the following text when adding the bug to the appropriate blocker list. Of course, referencing the specific criteria in question will help facilitate discussion on resolving the issue.

 Please consider this bug as an Fedora 37 [Alpha|Beta|Final]
 release blocker [1].  It impacts the release criterion that "FOO should happen 
 when BAR occurs".
 
[1] https://fedoraproject.org/wiki/Fedora_37_Alpha_Release_Criteria
     or
[1] https://fedoraproject.org/wiki/Fedora_37_Beta_Release_Criteria
     or
[1] https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria

For further details on the process, please see QA:SOP_blocker_bug_process.

Blocker Bug Removal

When a decision is made to drop a bug from a blocker list (e.g. F37Blocker or F37Beta), you may use the following response when removing the bug from the appropriate blocker list.

This bug was reviewed at the 2022-05-20 Fedora blocker review meeting [1].  The
team agreed that this issue does not meet the Fedora [Alpha|Beta|Final] release criteria and
should be removed from the blocker list.  Thank you.
[1] http://meetbot.fedoraproject.org/fedora-bugzappers/2022-05-20/link-to-meeting-log.html

Blocker Bug Downgrade to Target

When a decision is made to downgrade a bug to the Target blocker list (e.g. going from F37Blocker to F37Target), you may use the following response when changing the blocker information.

This bug was reviewed at the 2022-05-20
Fedora blocker review meeting [1].  The team agreed that this issue does not
meet the Fedora [Alpha|Beta|Final] release criteria.  However, the reported
issue is considered a nice-to-have fix and will be included if a fix is 
available in time.  Thank you. 
[1] http://meetbot.fedoraproject.org/fedora-bugzappers/2022-05-20/link-to-meeting-log.html