Red Hat Bugzilla – Bug 627028
Error Installing Package dbus
Last modified: 2012-04-11 11:41:11 EDT
Created attachment 440781 [details]
/tmp/anaconda.log at failure
Description of problem: If the extra repo "Fedora 14-Alpha-i386" is enabled when installing from CD for Fedora 14 Alpha i386, then installation aborts with a graphical message box "Error Installing Package: A fatal error occurred when installing the dbus package. This could indicate errors when reading the installation media. Installation cannot continue. [Exit installer]". Installing without enabling that extra repo (thus using only the default CD repo) succeeds. There is no other indication of error anywhere in any of the log files /tmp/*.
Version-Release number of selected component (if applicable): anaconda-14.15
How reproducible: Every time. I ran 6 installs total: 3 failures when also checking the extra repo "Fedora 14-Alpha-i386" (thus using 2 repos total), 3 successes when using just the default "Installation Repo". Two of each batch of three were done from physical CD-R (CD1 and CD2), one of each batch of three was done from a DVD+R burned from CD1.iso (thus costing a few cents more, but having a higher data rate, different transducer, and different physical placement of bits on the platter.) All media checked OK, both on the drive after burning, and with MediaCheck at install.
Steps to Reproduce:
1. Boot from physical CD-R or DVD+R media of CD1 and CD2.
2. Enable repo "Fedora 14-Alpha-i386" when selecting Packages.
Actual results: Graphical message box "Error Installing Package: A fatal error occurred when installing the dbus package. This could indicate errors when reading the installation media. Installation cannot continue. [Exit installer]".
Expected results: No abort.
Additional info: The package is dbus-1.3.2-0.1.885483.fc14.i686 (504KB) which did _not_ get updated by "yum update" after successful install.
Created attachment 440783 [details]
That error does only occur in pretty limited cases:
# Script errors store whether or not they're fatal in "total". So,
# we should only error out for fatal script errors or the cpio and
# unpack problems.
if what != rpm.RPMCALLBACK_SCRIPT_ERROR or total:
self.messageWindow(_("Error Installing Package"),
_("A fatal error occurred when installing the %s "
"package. This could indicate errors when reading "
"the installation media. Installation cannot "
"continue.") % name,
Scriptlet errors themselves should be in /mnt/sysimage/root/install.log. Can you check there for anything suspicious?
Created attachment 446566 [details]
install.log has 505 lines.
There are 193 warnings, all "%post(<pkgname>) scriptlet failed, exit status 127".
There is one error: %pre(dbus-1:1.3.2-0.1.885483.fc14.i686) scriptlet failed, exit status 127
The lines with "dbus" are:
warning: %post(dbus-libs-1:1.3.2-0.1.885483.fc14.i686) scriptlet failed, exit status 127
warning: %post(dbus-glib-0.86-4.fc14.i686) scriptlet failed, exit status 127
warning: %post(dbus-c++-0.5.0-0.11.20090203git13281b3.fc13.i686) scriptlet failed, exit status 127
error: %pre(dbus-1:1.3.2-0.1.885483.fc14.i686) scriptlet failed, exit status 127
In contrast, when no extra repo is activated then /mnt/sysimage/root/install.log has only one scriptlet error:
warning: %post(plymouth-theme-charge-0.8.4-0.20100723.1.fc14.i686) scriptlet failed, exit status 1
The "Fedora 14-Alpha-i386" repo is just the Fedora repo from the mirror list. "Installation Repo" is the local CD source. If there were some mismatch between the two (think, different versions of a base library in each repo) then that could easily lead to some of these problems.
I'd love to be able to disable those kinds of repos on media installs, but we do not have the information to differentiate them from updates repos and the like.