When trying to report a crash in pidgin with ABRT I get an error from report_uReport:
report_uReport
--- Running report_uReport --- The server at 'https://retrace.fedoraproject.org/faf' encountered an internal error (got error 500) ('report_uReport' exited with 1)
We will try and figure out where to direct this.
Perhaps @msuchy could say?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
@msrb is now responsible for ABRT. I can assist him with running the playbook though. But this is likely issues with the code. Michal can you check it?
Hmm, thanks for bringing this up to my attention. I reverted to the previous version, so everything should be good now :thumbsup:
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
Maybe this is what was hiding behind that 500 error but now I get:
--- Running report_uReport --- Server responded with an error: 'Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing' ('report_uReport' exited with 1)
The core_backtrace retrieved from coredumpctl likely has stack frames without filenames in it. Please open a bug for "abrt" component and, if possible, attach the core_backtrace file from the problem directory. Thanks ;)
Let us know if we can do anything more here... thanks @msrb!
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.