During F17 RC testing, twice now [1][2] I've been unable to submit bugs using abrt because the backtrace was considered "unusable" by abrt. 1. Is there a problem with the debuginfo's or abrt functionality during this F17 final RC stage? 2. What happened to the Retrace Server? I don't see that option for F17, only Local GNU Debugger. 3. Can the abrt behavior be changed to allow the bug to be created, but perhaps without the "bad" backtrace, or perhaps marked in some way so it is known to have a "bad" backtrace? It is still helpful to the bug reporter to have abrt create the bug with as much info as possible, with the expectation that better/usable backtraces could be attached later manually if possible. It is frustrating to be informed of a crash by abrt and go through all the effort to submit the bug report via abrt, only to be told "sorry, I'm not going to let you submit this bug report because it doesn't meet our standards of quality". Frankly, it's a waste of the reporter's time and it conditions the user to not care to submit bugs in the future. Thanks, Chuck [1] https://bugzilla.redhat.com/show_bug.cgi?id=823755 [2] https://bugzilla.redhat.com/show_bug.cgi?id=824228 -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
