Bug 923815
| Summary: | Crash reporting | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave P <dave.pawson> | ||||
| Component: | abrt | Assignee: | abrt <abrt-devel-list> | ||||
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | abrt-devel-list, admiller, dvlasenk, emmanuel, ffesti, iprikryl, itamar, jfilak, jmoskovc, jzeleny, mmilata, mtoman, packaging-team-maint, tim.lauridsen, zpavlas | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-04-05 06:48:42 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
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. How do you imagine the reporting to bugzilla should work without a login+password? 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 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. |
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.