Bug 525868 - No way to see if kerneloops reporting works
Summary: No way to see if kerneloops reporting works
Keywords:
Status: CLOSED DUPLICATE of bug 528395
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Target
TreeView+ depends on / blocked
 
Reported: 2009-09-26 12:53 UTC by Nicolas Mailhot
Modified: 2015-02-01 22:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-27 15:18:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nicolas Mailhot 2009-09-26 12:53:11 UTC
Description of problem:

I see kerneloops-related activity in system logs

Sep 26 14:14:53  abrtd: Hmm, stray update_client: 'Creating kernel oops crash reports...'
Sep 26 14:14:53  abrt: Kerneloops: Reported 2 kernel oopses to Abrt
Sep 26 14:14:53  abrtd: Directory 'kerneloops-1253967293-2' creation detected
Sep 26 14:14:56  abrtd: Getting local universal unique identification
Sep 26 14:14:56  abrtd: New crash, saving...
Sep 26 14:14:56  abrtd: Directory 'kerneloops-1253967293-1' creation detected
Sep 26 14:14:56  abrtd: Getting local universal unique identification
Sep 26 14:14:56  abrtd: New crash, saving...


but there are no traces at all in abrt-gui if any oops was actually reported and if it was, where on the kerneloops website. At least with the old kerneloops client I got notified when things happened

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

Comment 1 Zack Cerza 2009-10-07 18:54:37 UTC
I'm actually almost certain that the kerneloops scanner isn't working at all. This is unfortunate because I'm getting oopses *constantly* right now.

Comment 2 Jiri Moskovcak 2009-10-08 05:04:21 UTC
Try to run the GUI with root privileges.

Jirka

Comment 3 Christopher Beland 2009-10-27 15:18:10 UTC

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


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