Am Mittwoch, den 05.05.2010, 00:46 +0200 schrieb Mathieu Bridon: > On Wed, May 5, 2010 at 00:36, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > > Orcan Ogetbil wrote: > >> Hmm, this is what I did this a couple times, i.e. I forward the > >> backtrace to upstream without including any other information, since > >> the user does not provide any. > >> > >> What I receive from upstream is that they need more info. Then I go > >> back to the user asking once more to get information to reproduce the > >> bug. The user does not respond again. > >> > >> What do I do? > > > > You close the bug as INSUFFICIENT_DATA. It's all you can do. > > Or you can let it open, watch the CC list get bigger as ABRT detects > duplicate crashes and hope that one of the new affected users will be > able to provide a way to reproduce the crash. I have some of this kind of bugs... The CC list grows, but that's it. No comments are made. So I leave them open, till the bugzappers close it after reaching EOL (Maybe if I have more bugs like this, I'll close them as INSUFFICIENT DATA after some months of waiting...) I guess, you can't do more in these cases... Thomas -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
