Red Hat Bugzilla – Bug 865325
bug reporting from text mode doesn't work
Last modified: 2015-02-01 17:55:43 EST
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:
Steps to Reproduce:
- described in #865291
- the exception is just printed on screen, but there is no way to report it to bugzilla
- the report tool kicks in, asks for bz credentials and creates the bz ticket with all required logs
- not sure if this is problem with the new text mode not using the python-meh or in libreport
It was decided that text mode in F18 is really minimalistic and bug reporting will be available in F19.
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.
(In reply to comment #2)
> 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.
'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.
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.
Patches for python-meh and anaconda posted to anaconda-patches.
As it happens, I tried this the other day, and I was able successfully to file a traceback from text mode. Closing.