Description of problem: When Anaconda crashes, the only way to save the log is to SCP it to another machine. This makes it impossible to save the log if any of the following are true: *The network hasn't been set up. *The host the user wants to SCP to only allows encrypted connections with public key cryptography. *The user doesn't have anywhere to SCP to. How reproducible: every time How to Reproduce: Reproduce any bug that crashes Anaconda, such as not filling in every field for configuring a networking device to use IPv4 without DHCP. Actual results: A dialog comes up with the error log, and if I click the button to save it, it asks me to SCP it to somewhere. Expected results: I would be able to save the log to a floppy disk, as in previous FC versions. Suggested solution: Allow the user to mount a portable storage device such as a floppy disk or USB drive and save the log to somewhere on that portable storage device.
As long as a floppy drive is detected, you should be given the option to save to a floppy. Can you look through /tmp/anaconda.log and see if there are any messages related to the floppy device?
I was also having troubles with my floppy drive in FC5. I just tried it again and I saw the save to floppy option, so it wasn't a bug in Anaconda. However, I still think there should be another option that lets the user mount another device and save the log to that.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
As this issue is fixed, I'm closing this bug out. There's a separate bug tracking the need to support saving crash data to a USB device.