hi everyone, almost everything is in the title. I can’t report anymore crashes or bugs , it always fail .
almost nothing is in the title.
what desktop environment? What tool are you using to report bugs? what is the error message you are receiving? Are you trying to report to bugzilla.redhat? Are you using an API key for authentication?
1 Like
hello as i don’t have crash to report yet i couldn’t make a screen shot, i’m on fedora 40. gnomw x11, and using the Problem reporting app as it’s the only i know to be on my system > as soon as i’m facing a new crash i’ll populate the details
make sure you login into bugzilla.redhat.com, generate an API key, and paste the API key in the ABRT app (problem reporting app). That is the only way to authenticate you and enable bug reporting.
1 Like
so i finally had to report a new bug , i went to the red hat bugzilla to revoke my previous API key and generate a new one that i put in the configuration panel of problem reporting . I did taht 2 days ago tried to report , again same message with error . I thought that may be the API key need time to be effective and did wait until today and again error impossible to report . Let me know what u think about that ?
That is saying that there is already a bug report about this issue, and it tried to add you to that report, but that report is marked private so it couldn’t do it. ;(
So, the issue has been reported at least… but that error isn’t the best.
1 Like
I kind of feel like, even if there’s a duplicate PRIVATE report, Abrt should go ahead and create a new public one anyway. That way, other reporters will have a bug they can “me too” instead of everyone hitting the same roadblock just because someone decided to mark everything private by default.
I agree in principle, but it can be problematic as well when there are relatively common bugs that may be triggered in slightly different circumstances. This can flood Bugzilla with duplicate tickets that in the end probably never get resolved.
An example of this are gnome-shell SIGSEGVs tickets of which there are about 150 currently that are all similar but are triggered by various apps or extensions crashing the shell. This list will likely keep growing and that would be counterproductive too.
But that isn’t a public/private issue, it’s an issue of abrt’s ability to deduplicate in general. Abrt either can or can’t recognize those as duplicates, even if they’re public. That’s a totally separate conversation.
My only argument was, when abrt does find a bug that it KNOWS would be a duplicate, but fails to attach additional info only because that first bug has been marked as private, it should create one additional public duplicate, so that everyone can access the reported details. And then anyone else with the same bug can then attach their info to that bug, instead. (Obviously, the problem there would be if the current user is also trying to mark their report as private. In that case, refusing to create an additional private dupe would be the way to go.)
Worst-case, for this scenario, would be a maximum of two copies of each bug — if the first one is private, then a second public copy is created. The latter would then collect any further reports of the same bug as automatic “me too” comments.
But it’s incredibly frustrating when Abrt says, “Oh, hey, I found a bug for this issue already, attaching your info instead of creating a new bug. — Oops, sorry, can’t do that! It’s private!” …How does that help anyone?
(I’m not big on private bugs in public projects period, TBH, but I can accept them as a necessary evil. I’m just not willing to let them interfere with the public bug-reporting process.)