Created attachment 316098 [details] Screenshot.png Description of problem: Unable to save traceback using SCP method. Version-Release number of selected component (if applicable): anaconda-11.4.1.32-1.i386 $ /usr/sbin/snake-tree info http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os/ No data source used Name : Fedora development i386 (20080908) Arch : i386 Id : 1220873581.13 Version : development Family : Fedora Variant : Time : 2008-09-08 07:33 EDT URI's : Images : i386 (kernel, initrd, boot.iso), xen (kernel, initrd) How reproducible: 100% Steps to Reproduce: 1. Boot into vmlinuz+initrd.img from http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os 2. Append updates=http://jlaska.fedorapeople.org/traceback.img 3. When traceback dialog presenting, click Save 4. Enter user, passwd, host, filename Actual results: There was a problem writing the system state to the remote host. Expected results: anacdump saved on remote host Additional info: See screenshot * I don't see any additional output written to tty[1-5] when this error message occurs. * I'll attach the anacdump.txt that was used ot trigger the problem, but this will only indicate the expected traceback.
Created attachment 316099 [details] anacdump.txt Attaching expected anacdump.txt file that was manually transferred from tty2 using the `scp` command. Note, this file represents an expected traceback ... I'm just attaching in the event that there is some additional logging data that might help triage.
This will be fixed in the next build of anaconda.