Version-Release number of selected component: anaconda-18.6.7 Additional info: libreport version: 2.0.12 cmdline: ro vnc=1 kernel: 3.6.0-0.rc5.git0.1.fc18.ppc64
Created attachment 615029 [details] File: ifcfg.log
Created attachment 615030 [details] File: anaconda-tb
Created attachment 615031 [details] File: environ
Created attachment 615032 [details] File: type
Created attachment 615033 [details] File: storage.log
Created attachment 615034 [details] File: version
Created attachment 615035 [details] File: program.log
Created attachment 615036 [details] File: product
Created attachment 615037 [details] File: syslog
Created attachment 615038 [details] File: hashmarkername
Created attachment 615039 [details] File: packaging.log
Created attachment 615040 [details] File: anaconda.log
Created attachment 615041 [details] File: release
Created attachment 615042 [details] File: description
If the PPC machine's clock has not been configured (ex: Tue Jun 23 02:46:47 UTC 1970) then this happens when you accept your fate.
(In reply to comment #15) > If the PPC machine's clock has not been configured (ex: Tue Jun 23 02:46:47 > UTC 1970) then this happens when you accept your fate. This is something I didn't expect to happen. My fault, patch posted to anaconda-patches list.
anaconda-18.10-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.10-1.fc18
Package anaconda-18.10-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.10-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14933/anaconda-18.10-1.fc18 then log in and leave karma (feedback).
anaconda-18.11-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.11-1.fc18
anaconda-18.12-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.12-1.fc18
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.