Re: ABRT, Faf and current state of bug reporting

2013-04-24 Thread Stephan Bergmann
On 04/23/2013 03:27 PM, Richard Marko wrote: This allows us to get accurate statistics of crashing applications while not forcing every user to report to bugzilla. This is a trade-off between getting accurate statistics and quality of the reports as automated reports are anonymous which is also

Re: ABRT, Faf and current state of bug reporting

2013-04-24 Thread Richard Marko
On 04/23/2013 07:46 PM, Kevin Fenzi wrote: On Tue, 23 Apr 2013 15:27:50 +0200 Richard Marko rma...@redhat.com wrote: Hi all, I'll try to explain how crash reporting currently works in Fedora. Typical reporting process looks like this: - crash is reported to Faf server which responds with

Re: ABRT, Faf and current state of bug reporting

2013-04-24 Thread Richard Marko
On 04/23/2013 09:53 PM, Kevin Fenzi wrote: On Tue, 23 Apr 2013 15:45:34 -0400 Przemek Klosowski przemek.klosow...@nist.gov wrote: Well, here's an example why I think such information is highly useful: currently on my system every program using 3D (openGL/Mesa) crashes; that means everything:

Re: ABRT, Faf and current state of bug reporting

2013-04-24 Thread Richard Marko
On 04/24/2013 09:43 AM, Stephan Bergmann wrote: On 04/23/2013 03:27 PM, Richard Marko wrote: This allows us to get accurate statistics of crashing applications while not forcing every user to report to bugzilla. This is a trade-off between getting accurate statistics and quality of the reports

ABRT, Faf and current state of bug reporting

2013-04-23 Thread Richard Marko
Hi all, I'll try to explain how crash reporting currently works in Fedora. Typical reporting process looks like this: - crash is reported to Faf server which responds with 'known' or 'unknown' reply; - in case it responds with 'known' and the bug was already reported to both the server and

Re: ABRT, Faf and current state of bug reporting

2013-04-23 Thread Kevin Fenzi
On Tue, 23 Apr 2013 15:27:50 +0200 Richard Marko rma...@redhat.com wrote: Hi all, I'll try to explain how crash reporting currently works in Fedora. Typical reporting process looks like this: - crash is reported to Faf server which responds with 'known' or 'unknown' reply; - in case

Re: ABRT, Faf and current state of bug reporting

2013-04-23 Thread Przemek Klosowski
On 04/23/2013 01:46 PM, Kevin Fenzi wrote: On Tue, 23 Apr 2013 15:27:50 +0200 Richard Marko rma...@redhat.com wrote: This allows us to get accurate statistics of crashing applications while not forcing every user to report to bugzilla. This is a trade-off between getting accurate statistics

Re: ABRT, Faf and current state of bug reporting

2013-04-23 Thread Kevin Fenzi
On Tue, 23 Apr 2013 15:45:34 -0400 Przemek Klosowski przemek.klosow...@nist.gov wrote: Well, here's an example why I think such information is highly useful: currently on my system every program using 3D (openGL/Mesa) crashes; that means everything: Blender, Avogadro, pymol, FreeCAD,

Re: ABRT, Faf and current state of bug reporting

2013-04-23 Thread Rave it
From: Richard Marko rma...@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: ABRT, Faf and current state of bug reporting Message-ID: 51768c56.2080...@redhat.com Content-Type: text/plain; charset=ISO-8859-1 Hi all, I'll try to explain

Re: ABRT, Faf and current state of bug reporting

2013-04-23 Thread Alec Leamas
On 2013-04-23 22:26, Rave it wrote: From: Richard Marko rma...@redhat.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: ABRT, Faf and current state of bug reporting Message-ID: 51768c56.2080...@redhat.com Content-Type: text/plain; charset=ISO-8859-1