Bug 532082 - Anaconda remains awfully long in the "Finishing upgrade process. This may take a while." dialog
Summary: Anaconda remains awfully long in the "Finishing upgrade process. This may tak...
Keywords:
Status: CLOSED DUPLICATE of bug 493249
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-30 15:03 UTC by Nils Philippsen
Modified: 2009-10-30 15:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-30 15:29:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nils Philippsen 2009-10-30 15:03:34 UTC
Description of problem:
When upgrading my machine from F-11 with updates to F-12 Beta, about 3000 packages were updated. It took anaconda about 2 hours and 15 minutes to install the new packages during which I could see a progress bar. Then it took another 1 hour and 20 minutes to clean up packages during which it only displayed a dialog sporting "Finishing upgrade process. This may take a while." and a pulsating not-quite-progress bar which gave me no clue how much longer I would have to wait.

Version-Release number of selected component (if applicable):
I suppose anaconda-12.38-1.fc12 since this is the latest version tagged for f12-beta in koji.

How reproducible:
Reproducible I guess (I saw this going from F-10 to F-11).

Steps to Reproduce:
1. Upgrade system
2. Stare at "Finish upgrade process..." dialog and measure how long it's displayed.
  
Actual results:
See description (-> much too long without info about ETA)

Expected results:
Cleanup doesn't take so long (not likely) or user gets info about ETA. I assume that anaconda uses yum for installing so that information should be available somewhere (at least how many cleanup steps need to be done and how many are finished already).

Additional info:

Comment 1 Chris Lumens 2009-10-30 15:29:40 UTC

*** This bug has been marked as a duplicate of bug 493249 ***


Note You need to log in before you can comment on or make changes to this bug.