How to proceed with MiniDebugInfo
Adam Williamson
awilliam at redhat.com
Thu May 31 02:22:46 UTC 2012
On Sat, 2012-05-26 at 16:12 +0200, Jan Kratochvil wrote:
> On Sat, 26 May 2012 12:50:31 +0200, Richard W.M. Jones wrote:
> > - You're in IRC or email, and all the bug reporter has given you is a
> > random copy and paste from their terminal. They don't care to open
> > a bug; they don't much care about anything except getting a fix.
> >
> > Minidebuginfo would help here.
>
> This is a bug of ABRT again. The crash should have been already reported
> without asking anything. (Not going to discuss some security claims.)
> You could just look up BZ(*) with the person's bugreport at that moment.
> (*) Maybe such mass bugreports should not end up in BZ as the first place.
And how are you going to stop the user _then_ creating a manual report
with the random copy/pasted message _after_ the automatic report has
reported it without them noticing? How is the maintainer to know it's a
dupe without minidebuginfo? Your answer appears to be insufficient. :)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
More information about the devel
mailing list