Red Hat Bugzilla – Bug 208725
RFE: give visual feedback during long database update
Last modified: 2010-11-04 21:56:05 EDT
Description of problem: Updating the rpm database at the end of Package Install
for an Upgrade takes a very long time, and there is no visual feedback that the
process is not hung or crashed. For instance, when upgrading from FC5 to FC6Pre
on a PowerPC Apple Macintosh Mini (1.25GHz, 512MB RAM), the text mode install
screen had Package Install at 100% for over 15 minutes. I though it was hung,
but using VT2 to do an strace of anaconda convinced me that it was making slow
progress updating the rpm database (at something like 1 package per second).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use the rescue CD to upgrade from FC5 to FC6Pre.
Package Install apparently finishes (progress bar shows 100% after 2hr45min via
DSL for Basic + Software Development), then sits for over 15 minutes without
change or apparent progress, yet eventually completes.
Something that takes longer than 20 or 30 seconds should have a progress bar, as
an indication that progress is being made, and to allow the user to estimate
when it might complete. In this case, there were about 900 packages, so a
progress bar of about 1/2 the screen width would have done nicely.
User email@example.com's account has been closed
Adding FutureFeature keyword to RFE's.
*** Bug 450343 has been marked as a duplicate of this bug. ***
This should be better in the next build of anaconda, though I haven't been able
to test it as thoroughly as I would like.
Wrt cornering the bug: I believe the long delay occurs only in upgrades, not in
I am in the middle of an upgrade from F12 to F13 and the "Finishing upgrade process. This may take a little while." dialog has been showing for over an hour and counting, with no indication of actual progress (a bar flashing back and forwards only tells me that the install process hasn't locked up, but that's about all).
Surely this bug hasn't actually been fixed -- should it be reopened?
Still not fixed on F12 -> F14 "preupgrade". This should be closed as a dupe of bug 493249, since that seems to have the most current traffic on it.
Note that there are quite a few bugs with this complaint, most closed as dupes of one or two core bugs:
bug 208725 (dups: bug 450343)
this bug [bug 452724] (dups: bug 474460,
bug 493249 (dups: bug 532082, bug 597064