ABRT seems to open bugs for packages (or better rpms) installed from non-Fedora sources when the same package exists also in Fedora. See bug 908470 for an example - it's upstream packaged CodeBlocks IDE, not the package we havbe in Fedora.
That's unfortunate, but I really don't see any good solution here. We can prevent reporting of non-Fedora packages to bugzilla, but it's open source so the client side can be easily altered to bypass this check.
*** Bug 911904 has been marked as a duplicate of this bug. ***
I understand there is no good solution, but at least a warning should be presented to the reported when the rpm containing the crashing binary is not coming from Fedora. Wasn't there a check in ABRT whether the rpm is signed with Fedora key some time ago?
(In reply to comment #3) > I understand there is no good solution, but at least a warning should be > presented to the reported when the rpm containing the crashing binary is not > coming from Fedora. Wasn't there a check in ABRT whether the rpm is signed > with Fedora key some time ago? - it just checks if the package is signed by ANY of installed keys - I suggest to save the rpm %vendor tag and add a condition that reporting to bugzilla is only allowed for "Fedora Project" and Red Hat
FWIW, this can happen for packages that aren't available in Fedora at all [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1038995 -- fish is in Fedora now, but it wasn't when the bug was filed.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This has gotten completely out of control. With the shiny new retrace infrastructure, I get spammed with utter BS like this: https://retrace.fedoraproject.org/faf/reports/748335/ This is NOT A FEDORA PACKAGE. Hey, look, all 103 reports are on CentOS 7, and there is no fish-anything.el7. Yes, I realize that an annoying user can upload whatever they want, but please fix the default so that abrt doesn't upload non-Fedora crashes or at least flags them as such.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
The %{vendor} tag and the GPG signature key has been added to the collected elements in upstream commit https://github.com/abrt/abrt/commit/451e57fc509f401bb586e7db88256923d47c38f7
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.