The crash data sitting in FAF is genuinely useful and it's a shame it doesn't
get the attention it deserves. Removing gnome-abrt feels like giving up on
something that just needs proper investment, not removal.
Milan raises a fair point a backtrace without steps or reporter communication
doesn't get you very far when you can't reproduce the crash locally. But that's
exactly why the reporting workflow needs a redesign, not why the tool should be
dropped. The Bugzilla API key situation has already made most users give up on
manual reporting, so routing directly to GNOME GitLab or Fedora Forge with a
per-package configuration makes much more sense going forward.
The DrKonqi angle is interesting worth reaching out to the KDE team to see if
FAF integration is something they'd consider. Could open the door for other
desktop environments to follow the same pattern.
Rebuilding on top of journald also makes sense long term. The current setup
gets stuck too often and carries more overhead than it needs to. Lighter and
cleaner is the right direction.
It's a bit like doing custom kitchen design in Baltimore
https://msdcontractors.com/ when the layout hasn't been touched in years, the
instinct is to tear it out completely, but most of the time the smarter call is
to rework what's already there, fix the flow, and let the solid foundation do
its job. Same applies here the crash collection works, the pipeline around it
just needs to be rebuilt properly.
The UI PR is a decent starting point but the reporting side needs to come first.
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
