ABRT, Faf and current state of bug reporting

[Przemek Klosowski]

On 04/23/2013 01:46 PM, Kevin Fenzi wrote:
> On Tue, 23 Apr 2013 15:27:50 +0200
> Richard Marko <rmarko at 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 and quality of the
>> reports as automated reports are anonymous which is also the reason
>> why they can't contain full backtrace with data.
>
> Well, it's nice to know when things crash, sure... but without more
> information it's very difficult to figure out how to fix that crash.

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, openSCAD, and 
even everything that uses FLTK library because it renders both 2D and 3D 
through OpenGL:

Program received signal SIGSEGV, Segmentation fault.
intel_miptree_unmap (intel=0x18d1960, mt=0x0, level=0, slice=0) at 
intel_mipmap_tree.c:1752
1752	   if (mt->num_samples <= 1)

It's an Intel driver bug that seems pretty severe to me but I don't have 
the graphics chops to fix it:

https://bugzilla.redhat.com/show_bug.cgi?id=922224

I think it would help things if there were reliable statistics on its 
footprint. Is it just my Q45 or all Intel chipsets? is it just my weird 
configuration (two screens? update rather than fresh install? some 
configuration I did and forgot about?).