ABRT, Faf and current state of bug reporting

[Richard Marko]

On 04/23/2013 09:53 PM, Kevin Fenzi wrote:
> On Tue, 23 Apr 2013 15:45:34 -0400
> Przemek Klosowski <przemek.klosowski at 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,
>> 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
> Which seems to be also:
> https://bugzilla.redhat.com/show_bug.cgi?id=946960
> and
> https://retrace.fedoraproject.org/faf/problems/786379/
>  
>> 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?).
> That would be nice, but alas, we don't know and faf doesn't tell us.

It's not easy to implement this because of privacy issues. There was
already such request though so we'll consider implementing this.

>
> We know that there have been 32 instances of this crash recorded by
> faf. That doesn't tell us anything at all about the hardware or
> installed packages or screens or other info about those instances. All
> we know is that it happened 32 times (I suppose we don't even know it's
> 32 different machines even, could one person report a crash 32times?)

Correct. List of installed packages related to the crash will be available.

-- 
Richard Marko