Description of problem: abrt tries to report kerneloops and: --- Running report_uReport --- Server responded with an error: 'Invalid JSON file' reporter-ureport failed with exit code 1 ('report_uReport' exited with 1) in /var/tmp/abrt/oops-2014-08-16-08:26:15-718-0 I do reporter-ureport -vvv and I get: Loaded option 'URL' = 'https://retrace.fedoraproject.org/faf' Failed to parse operating system release string Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 928176 [details] another one
Thank you for the report. Can you please post the "reporter-ureport -vvv ..." output for the kerneloops crash if you still have it? What is the name-version-release of satyr?
Sorry, I did not realize you already included the whole output in the description. Can you attach the file "os_info" from /var/tmp/abrt/oops-2014-08-16-08:26:15-718-0?
interesting fact is the os_info file is missing but other dirs would have it, and it would look like: AME=Fedora VERSION="22 (Rawhide)" ID=fedora VERSION_ID=22 PRETTY_NAME="Fedora 22 (Rawhide)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:22" HOME_URL="https://fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=Rawhide REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=Rawhide but! sometimes I see it is empty
Created attachment 954501 [details] reporter-ureport -vvv
here is one(reporter-ureport.1.txt) the fails and has os_info: NAME=Fedora VERSION="22 (Rawhide)" ID=fedora VERSION_ID=22 PRETTY_NAME="Fedora 22 (Rawhide)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:22" HOME_URL="https://fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=Rawhide REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=Rawhide
The last failure seems to be caused by bug #1141549 (notice the squares in the json report), which should be fixed in abrt-2.3.0-4.fc22. Can you still reproduce the bug where os_info is empty?
with os_info empty it sill fails.
I apologize for stupid wording of my last question. Let me rephrase: Does it still happen that crashes create directories under /var/tmp/abrt, and those directories have no os_info?
no, it seems that all dirs now have os_info
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.