Bug 1013071 - gnome-abrt considers kernel trace reports with no 'component' to be reportable
Summary: gnome-abrt considers kernel trace reports with no 'component' to be reportable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1008586
TreeView+ depends on / blocked
 
Reported: 2013-09-27 18:48 UTC by Adam Williamson
Modified: 2016-12-01 00:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:25:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
this is one of the problem reports: shows as 'reportable' in gnome-abrt, but it isn't (3.49 KB, application/x-xz)
2013-09-27 18:48 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2013-09-27 18:48:03 UTC
Created attachment 804111 [details]
this is one of the problem reports: shows as 'reportable' in gnome-abrt, but it isn't

My F18 laptop has a whole pile of kernel warning traces - all "WARNING: at drivers/gpu/drm/i915/intel_display.c:979 intel_wait_for_pipe_off". Several of them are considered 'clean' by gnome-abrt (i.e. the Report button is live), but if I try and report them, I get to the 'actually filing a report' stage, and then get this:

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running report_Bugzilla ---
Essential element 'component' is missing, can't continue
('report_Bugzilla' exited with 1)

Seems like gnome-abrt should be able to catch this and not allow me to try and report them.

I'll attach one of the problem oopses for reference.

Comment 1 Jakub Filak 2013-10-17 14:12:35 UTC
Thank you for the report. It seems that abrtd fails to recognize those oopses as detected while computer was shutting down. It would be very helpful if you could attach system logs containing any of those oopses or tell us how was the oops detected and how it was announced (did you see a notification bubble?).

Could you please restart abrtd service and check whether those oopses are still reportable or not?

Comment 2 Fedora End Of Life 2013-12-21 14:37:39 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2014-02-05 22:25:38 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.

Comment 4 Adam Williamson 2014-06-16 22:25:56 UTC
sorry, never got back to this. i'll file again if anything similar comes up again.


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