Created attachment 1313998 [details] ABRT tarball directory reporter-ureport -vvv 2>&1 | paste http://termbin.com/kd4c Ends with: --------------------------f04bc41da7465b29--^M^J' curl rcvd header: 'HTTP/1.1 400 BAD REQUEST^M^J' curl rcvd header: 'Date: Wed, 16 Aug 2017 08:32:40 GMT^M^J' curl rcvd header: 'Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.1e-fips mod_wsgi/3.4 Python/2.7.5^M^J' curl rcvd header: 'Content-Length: 41^M^J' curl rcvd header: 'Connection: close^M^J' curl rcvd header: 'Content-Type: application/json^M^J' curl rcvd header: '^M^J' curl rcvd data: '{ "error": "uReport data is invalid." }' curl: Closing connection 0 after curl_easy_perform: response_code:400 body:'{ "error": "uReport data is invalid." }' Server odpověděl chybou: 'uReport data is invalid.' Attaching the ABRT report.
*** Bug 1342569 has been marked as a duplicate of this bug. ***
I am also seeing this on Fedora 25 and from what I can tell it happens only for kernel oopses.
Thank you for reporting. Problem is probably in koops backtrace parser in satyr, in resulting ureport are missing backrace frame addresses, which are mandatory. Will look why it doesn't parse.
Created attachment 1334748 [details] reporter-ureport -vvv output Same here, is suspect many ppl hit tihis but never report as it silent, just a bit of system load for a minute, or(and) lazy to do full steps to report.
Created attachment 1337462 [details] reporter-ureport -vvv Don't know if another report is helpful, but I'm seeing the same thing.
See also bug #1532004.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.