Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 865325 - bug reporting from text mode doesn't work
Summary: bug reporting from text mode doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fedora19rtt
TreeView+ depends on / blocked
 
Reported: 2012-10-11 08:50 UTC by Jiri Moskovcak
Modified: 2015-02-01 22:55 UTC (History)
9 users (show)

Fixed In Version: anaconda-19.2-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-12 17:04:55 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jiri Moskovcak 2012-10-11 08:50:18 UTC 
Description of problem:
Recently i ran into a problem during the installation from text mode and anaconda just died with an exception without giving me a chance to use the reporting tool to report the bug to bugzilla, so I had to do it manually (rhbz#865291)

Version-Release number of selected component (if applicable):
tested with nightly builds:
20121009
20121010

How reproducible:
100%

Steps to Reproduce:
- described in #865291
  
Actual results:
- the exception is just printed on screen, but there is no way to report it to bugzilla

Expected results:
- the report tool kicks in, asks for bz credentials and creates the bz ticket with all required logs

Additional info:
- not sure if this is problem with the new text mode not using the python-meh or in libreport
Comment 1 Vratislav Podzimek 2012-10-11 09:04:16 UTC 
It was decided that text mode in F18 is really minimalistic and bug reporting will be available in F19.
Comment 2 Martin Banas 2012-10-12 08:59:21 UTC 
Hello,

would it be at least possible for F18 not to reboot the machine if traceback happens? If it's not a hard task, it would really help with debugging.

Thanks.
Comment 3 Vratislav Podzimek 2012-10-12 09:09:37 UTC 
(In reply to comment #2)
> Hello,
> 
> would it be at least possible for F18 not to reboot the machine if traceback
> happens? If it's not a hard task, it would really help with debugging.
> 
> Thanks.
'nokill' boot option should prevent reboot. Until we have some better exception handling (with bug reporting) in text mode, I'm afraid this is the only option.
Comment 4 Jesse Keating 2012-10-17 21:21:49 UTC 
We /might/ make textmode default to nokill, because there is no way to report the errors.  Hopefully for F19 we'll have some way to do error reporting in text mode.
Comment 6 Vratislav Podzimek 2013-01-15 13:37:58 UTC 
Patches for python-meh and anaconda posted to anaconda-patches.
Comment 7 Adam Williamson 2013-05-12 17:04:55 UTC 
As it happens, I tried this the other day, and I was able successfully to file a traceback from text mode. Closing.
Note You need to log in before you can comment on or make changes to this bug.