Created attachment 937343 [details]
screenshot of problem
Description of problem:
--- Running report_uReport ---
Server responded with an error: 'Invalid JSON file'
reporter-ureport failed with exit code 1
('report_uReport' exited with 1)
--- Running report_EmergencyAnalysis ---
Sending /var/tmp/oops-2014-09-14-21:39:14-724-0.tar.gz to https://retrace.fedoraproject.org/faf/dumpdirs/new/
Successfully sent /var/tmp/oops-2014-09-14-21:39:14-724-0.tar.gz to https://retrace.fedoraproject.org/faf/dumpdirs/new/
Problem still not fixed :(
(In reply to Mikhail from comment #1)
> Problem still not fixed :(
Unfortunately, the uploaded dump directory has been removed by garbage collection. Could you please attach the dump directory to this bug report?
Created attachment 946483 [details]
Thank you! 'backtrace' file contains some invalid characters but 'dmesg' file is OK, thus I blame abrt-dump-journal-oops from adding these invalid characters.
Please run the following command and attach the resulting file journald-kernel.txt to this bug report:
$ sudo journalctl -o cat SYSLOG_IDENTIFIER=kernel > journald-kernel.txt
*** Bug 1152239 has been marked as a duplicate of this bug. ***
Mikhail, I don't need journald-kernel.txt file, I made same error as here: https://bugzilla.gnome.org/show_bug.cgi?id=709290 https://mail.gnome.org/archives/commits-list/2013-October/msg07813.html
Created attachment 946637 [details]
I've opened upstream pull request for this bug: https://github.com/abrt/abrt/pull/863
Proposed as a Freeze Exception for 21-beta by Fedora user jfilak using the blocker tracking app because:
If this bug is not fixed users of Live CD will not be able to report any Kernel oops.
gnome-abrt-1.0.0-1.fc21,abrt-2.3.0-2.fc21,libreport-2.3.0-2.fc21,satyr-0.15-1.fc21 has been submitted as an update for Fedora 21.
Please, look also that happens here https://bugzilla.redhat.com/show_bug.cgi?id=1152663
Discussed at 2014-10-15 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-15/f21-blocker-review.2014-10-15-16.04.log.txt . Accepted as a freeze exception - problem reporting is significant, and this is one many people are running into. It affects the live images so cannot be fully fixed with an update.
Package gnome-abrt-1.0.0-1.fc21, abrt-2.3.0-2.fc21, libreport-2.3.0-2.fc21, satyr-0.15-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-abrt-1.0.0-1.fc21 abrt-2.3.0-2.fc21 libreport-2.3.0-2.fc21 satyr-0.15-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
The already detected kernel oopses will not be reportable with the updated packages. If you want to report them, you need first to delete them all and then re-detect them:
# delete the detected oopses
$ sudo rm -rf /var/tmp/abrt/oops*
# stop the service
$ sudo systemctl stop abrt-oops
# remove the state file if exists
$ sudo rm -f /var/lib/abrt/abrt-dump-journal-oops.state
# extract oopses from entire journal
$ sudo abrt-dump-journal-oops -Dx
# save cursor to the last kernel message
$ sudo journalctl -n 1 -o verbose SYSLOG_IDENTIFIER=kernel | sed -n 's/^.*\[\(.*\)\].*$/\1/p' | sudo tee /var/lib/abrt/abrt-dump-journal-oops.state
# start the service
$ sudo systemctl start abrt-oops
gnome-abrt-1.0.0-1.fc21, abrt-2.3.0-2.fc21, libreport-2.3.0-2.fc21, satyr-0.15-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.