Description of problem: trying to do a fresh install, gave code 12 Version-Release number of selected component: anaconda-20.25.15-1.fc20.x86_64 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 138, in install raise exn File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 162, in doInstall payload.install() File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run threading.Thread.run(self, *args, **kwargs) PayloadInstallError: rsync exited with code 12 Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-x86_64-20-1 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 other involved packages: python-libs-2.7.5-9.fc20.x86_64 product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20 Potential duplicate: bug 872926
Created attachment 937724 [details] File: anaconda-tb
Created attachment 937725 [details] File: anaconda.log
Created attachment 937726 [details] File: environ
Created attachment 937727 [details] File: journalctl
Created attachment 937728 [details] File: lsblk_output
Created attachment 937729 [details] File: nmcli_dev_list
Created attachment 937730 [details] File: os_info
Created attachment 937731 [details] File: program.log
Created attachment 937732 [details] File: storage.log
Created attachment 937733 [details] File: ifcfg.log
Created attachment 937734 [details] File: packaging.log
Sep 15 17:14:34 localhost kernel: rsync[2686]: segfault at 4000b11480 ip 000000000040dd81 sp 00007ffff3bb12c8 error 4 in rsync[400000+5d000] Sep 15 17:14:35 localhost abrt-hook-ccpp[2691]: Saved core dump of pid 2686 (/usr/bin/rsync) to /var/tmp/abrt/ccpp-2014-09-15-17:14:34-2686 (68845568 bytes) Sep 15 17:14:36 localhost abrt-server[2692]: Generating core_backtrace Sep 15 17:14:36 localhost abrt-server[2692]: Generating backtrace It looks like rsync crashed.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I don't expect new installation of F20.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.