Bug 60162 - RFE: Save backtrace to alternate locations
Summary: RFE: Save backtrace to alternate locations
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2002-02-21 00:30 UTC by Michal Jaegermann
Modified: 2007-04-18 16:40 UTC (History)
0 users

Clone Of:
Last Closed: 2006-04-24 18:35:15 UTC

Attachments (Terms of Use)

Description Michal Jaegermann 2002-02-21 00:30:17 UTC
Description of Problem:

During an attempt to a "minimal" installation which was done by deselecting
_all_ packages save few (like filesystem, bash, grub, ...) and later
accepting "install all packages to resolve dependencies" around 400 MB
was still picked up for an installation.  After installing nearly everything
save few megabytes (hard to tell exactly how many due to subseqent events)
anaconda poped out a bit Python trace window in the middle of the screen
killing mouse in the process.  Some buttons in an attempt to save to a floppy
were reachable from a keyboard but with the final "Confirm" I was not so
lucky and anaconda immediately rebooted the whole setup.

It would be really good to have these backtraces in some file on a ramdisk
instead of a "user-friendly" dialog.  Then I normally have multiple places
to save in a sane way instead of blowing up a diskette which often may
turn out to have errors (this happens more and more often).

Comment 1 Michael Fulbright 2002-02-22 16:33:16 UTC
Any ideas Matt?

Comment 2 Jay Turner 2002-03-20 15:10:23 UTC
Are you seeing the same behavior with Beta 2?

Comment 3 Matt Wilson 2002-03-20 15:16:00 UTC
deferred to next gtk2 based installer

Comment 4 Michael Fulbright 2003-04-16 18:55:24 UTC
Tracebacks will now be written to /tmp/anacdump.txt.

Comment 5 Jeremy Katz 2006-04-24 18:35:15 UTC
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed).  If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.

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