Description of problem:
Anaconda install fails with:
The following error occurred while installing. This is a fatal error
and installation will be aborted.
script error with package [pinentry|ca-certificates]
Press enter to exit.
The package name printed depends on the mix of packages you're
trying to install, but so far I have seen "pinentry" and
There is no other indication about why the script may have
failed. No error appears on screen or in any log file as
far as I can find.
Why are script errors fatal?
Version-Release number of selected component (if applicable):
Anaconda in Fedora 19 ppc64.
Steps to Reproduce:
1. Do a minimal, text install.
Will attach log files.
Created attachment 791384 [details]
Created attachment 791385 [details]
Created attachment 791386 [details]
Created attachment 791387 [details]
Created attachment 791388 [details]
Created attachment 791389 [details]
Created attachment 791390 [details]
Created attachment 791391 [details]
The script errors are fatal because yum is indicating that the script errors are fatal to the transaction. In the ca-certificates case in the attached, the failure is in %pre, so the package is indicating there's something wrong with the system that prevents the package from being installed.
I'm not able to reproduce doing a minimal text install to an LPAR, so I'm not sure whether there's a problem with the ca-certificates or pinentry packages or not. Maybe it's a hardware problem?
Created attachment 839473 [details]
yum transaction file
I can confirm with Fedora 20 graphical installer running under qemu-system-ppc64. I also have used minimal installation. The reproducing can be quite hard - installation preparation took more than two days...
No log files remained on the disk, but I've found yum transaction file. Attached.
The log files are in /tmp during installation. Please attach the files from there, in particular anaconda.log, packaging.log and program.log.
Created attachment 840465 [details]
log files from installation of Fedora 20 PPC64 under qemu
In this case, the problem is with launching of /usr/bin/p11-kit (called from update-ca-trust script).
If I understand the issue correctly, maybe it is more general problem of launching ppc64 binaries? (or maybe only when running under qemu?)
The bug about the chroot binary looks similar: https://bugzilla.redhat.com/show_bug.cgi?id=1045384
The signal 4 error messages indicate an attempt to execute an illegal instruction, so I'm going to say this is a problem with the emulator.
This could be caused by QEMU's lack of support for the VSX SIMD extensions.
*** Bug 1045384 has been marked as a duplicate of this bug. ***