2 ms·
> I remember the days before we had reportbug. Over and over and over again, I would get bug reports from users that wouldn’t have the basic information needed
by smacktoward 8y ago
> I remember the days before we had reportbug. Over and over and over again, I would get bug reports from users that wouldn’t have the basic information needed to investigate. reportbug gathers information from the system: package versions, configurations, versions of dependencies, etc. A simple web form can’t do this because it doesn’t have a local agent.
You control the operating system. Couldn't you build a web form that integrates with a local agent?
- Boulth 8y agoActually using Native Messaging it's not that hard. For example Mailvelope (OpenPGP browser extension) uses Native Messaging to talk to locally running GnuPG.
- Conan_Kudo 8y agoIn Fedora, we have a web form configuration with a basic bug reporting template in the Red Hat Bugzilla (which we share with Red Hat, since it's useful to cross-link bugs between RHEL and Fedora). In addition, we created the Automatic Bug Reporting Tool (ABRT)[1] to handle program and system crashes and report them so developers can look at them. We have hooks in various parts of the system to help generate useful bug reports of serious issues with crash data, machine information, and so on. They get submitted as private bugs by default to the bug tracker, and the Fedora retrace server[2] kicks in to request the debuginfo data remotely to get traces as needed and include those in the bug report. ABRT also helps you strip sensitive data (if any) from information being sent remotely before sending it. You can see pretty charts about the crash analysis too: https://retrace.fedoraproject.org/faf/summary/ https://retrace.fedoraproject.org/faf/summary/ [1]: https://abrt.readthedocs.io/en/latest/ https://abrt.readthedocs.io/en/latest/ [2]: https://fedoraproject.org/wiki/Features/RetraceServer https://fedoraproject.org/wiki/Features/RetraceServer