Bug 538593 - KerneloopsReporter warns that reports were not sent
Summary: KerneloopsReporter warns that reports were not sent
Keywords:
Status: CLOSED DUPLICATE of bug 533589
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 21:37 UTC by Richard Schwarting
Modified: 2015-02-01 22:49 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-22 19:35:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot of ABRT error (29.00 KB, image/png)
2009-11-18 21:37 UTC, Richard Schwarting
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.