Bug 923815 - Crash reporting
Summary: Crash reporting
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-20 13:59 UTC by Dave P
Modified: 2013-06-24 03:27 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-05 06:48:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
log generated during reporting phase (28.36 KB, text/plain)
2013-03-20 13:59 UTC, Dave P
no flags Details

Description Dave P 2013-03-20 13:59:06 UTC
Created attachment 713254 [details]
log generated during reporting phase

Description of problem: applied new updates. Reboot. crash.


Version-Release number of selected component (if applicable):


How reproducible: Not reproducbile


Steps to Reproduce:
1.
2.
3.
  
Actual results: Tried to report. I forgot my bugzilla password (why do I need one for Fedora to report a bug to Fedora?)


Expected results:


Additional info:

The crash log attached.

Comment 1 Jan Zeleny 2013-04-05 06:07:21 UTC
I'm not sure what is the actual problem reported here. Is it the packages that are not downloaded? Or the fact that something crashed? Or the fact that you need your BZ account to file a bug?

As for the yum side, there is nothing wrong I can see, the issue is clearly on the server side (see those HTTP errors). Reassigning to abrt for further evaluation. I suggest closing as INSUFFICIENT_DATA, as the report is really not clear.

Comment 2 Jiri Moskovcak 2013-04-05 06:10:51 UTC
How do you imagine the reporting to bugzilla should work without a login+password?

Comment 3 Dave P 2013-04-05 06:45:23 UTC
1. Fedora crashed after applying updates. clearly now fixed.

2. When I go to report this (or any other) problem, via the reporting tool
in Fedora, I am required to know the bugzilla logon and password. 
a) I only do this when I have a crash, hence I don't remember the logon/passwd
b) Because of that, I (or the bug reporting tool) is unable to pass on the crash information to Fedora. I think that is a problem? Fedora is losing lots of useful information.

Suggest that if a reporting tool is 'reporting', no logon/pwd is needed. 

HTH

Comment 4 Jiri Moskovcak 2013-04-05 06:48:42 UTC
Your problem has been already reported to this problem tracker: https://retrace.fedoraproject.org/faf/summary/ Reporting to bugzilla can't be done without login and password.


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