Created attachment 916270 [details] The dmesg lines that triggered the oops Description of problem: Uploading my latest kernel oops (really locking problem) fails. Version-Release number of selected component (if applicable): abrt-* 2.2.1-6 How reproducible: Always Steps to Reproduce: 1. select oops from abrt-gui 2. submit oops Actual results: --- Running report_uReport --- Server responded with an error: 'Validation failed: Element 'frames' is invalid: List element is invalid: Element 'function_name' is missing' reporter-ureport failed with exit code 1 ('report_uReport' exited with 1) --- Running report_EmergencyAnalysis --- Compressing data Sending /var/tmp/oops-2014-07-08-09:32:58-18966-0.tar.gz to https://retrace.fedoraproject.org/faf/dumpdirs/new/ Successfully sent /var/tmp/oops-2014-07-08-09:32:58-18966-0.tar.gz to https://retrace.fedoraproject.org/faf/dumpdirs/new/ Expected results: Oops is correctly reported.
Michal, would it be possible to accept kernel oops ureports with stack trace frames without 'function_name' element? It seems to me that this issue has become too often. Even 'will_oops' on Fedora 20 has a frame without function name.
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.
Moved upstream: https://github.com/abrt/faf/issues/522
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days