I strongly suspect that, within the installer, when anaconda makes use of the report library, there is no access to any config files (because there is no root file system to get config files from).
In any case the report library should be able to run even if all it's config files are inaccessible.
To do this we need to make two changes:
all places where config files are read, need to be able to recover if the files are not there, or if the files are unreadable, or any other error reading them.
we need to mark in some machine readable way, the set of 'default' plugins that should be usable (by report) if the primary /etc/report.conf file is not readable. Plugins should only be marked this way if they can be run without
This is fixed in the fedoraproject src repo.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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.
The process we are following is described here: