Bug 538593

Summary: KerneloopsReporter warns that reports were not sent
Product: [Fedora] Fedora Reporter: Richard Schwarting <aquarichy>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anton, dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, mnowak, npajkovs, psj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-22 19:35:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of ABRT error none

Description Richard Schwarting 2009-11-18 21:37:35 UTC
Created attachment 370199 [details]
Screenshot of ABRT error

Description of problem:
After logging into my freshly preupgraded Fedora 12 final this morning, I noticed a number of kerneloops in my ABRT dialogue.  I went to report them, and had to log into Redhat bugzilla (which seemed to work) and then I got an error dialogue telling me that each kerneloops report I tried to send was not sent.

"KerneloopsReporter: CKerneloopsReporter::Report(): Report has not been sent..."

I am connected to the Internet, as well, so it shouldn't be a network issue.

Version-Release number of selected component (if applicable):
abrt-0.0.11-2.fc12

How reproducible:
I had 3 kerneloops, and the same error appeared when I tried to send each of them.

Steps to Reproduce:
1. Obtain a kernel oops (easy with an intel video card :D)
2. Try to send it
3.
  
Actual results:
Dialogue tells me it failed

Expected results:
Dialogue tells me I'm awesome and it succeeded

Additional info:
I had one other ABRT item to report, a crash in gnome-panel, which is still downloading debuginfos to install.  I will try to add whether that succeeded as well.  The error message seems to be Kerneloops specific though.

Comment 1 Richard Schwarting 2009-11-18 21:39:42 UTC
Update >>Einen Bericht erstellen und einreichen ...<<
Warning >>Report(): CKerneloopsReporter::Report(): Report has not been sent...<<
Update >>Reporting via 'KerneloopsReporter' was not successful: CKerneloopsReporter::Report(): Report has not been sent...<<
Our job for UUID 705862969 is done.
Update >>Einen Bericht erstellen und einreichen ...<<
Warning >>Report(): CKerneloopsReporter::Report(): Report has not been sent...<<
Update >>Reporting via 'KerneloopsReporter' was not successful: CKerneloopsReporter::Report(): Report has not been sent...<<
Our job for UUID 1100331017 is done.
Update >>Einen Bericht erstellen und einreichen ...<<
Warning >>Report(): CKerneloopsReporter::Report(): Report has not been sent...<<
Update >>Reporting via 'KerneloopsReporter' was not successful: CKerneloopsReporter::Report(): Report has not been sent...<<
 
This appeared in my .xsession-errors log.

"Einen Bericht erstellen und einreichen" means something like 'Preparing and sending a report'

Comment 2 Richard Schwarting 2009-11-18 22:06:48 UTC
The other report I wanted to send, which was not a kernel oops but a segfault in a GNOME app, failed, but with a different error, described in bug 538602.

Comment 3 Jiri Moskovcak 2009-11-22 19:35:08 UTC

*** This bug has been marked as a duplicate of bug 533589 ***