Bug 980094 - FedUp Progress Bar not moving
Summary: FedUp Progress Bar not moving
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-01 12:10 UTC by Vasilis Keramidas
Modified: 2013-10-10 19:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-10 19:52:04 UTC
Type: Bug


Attachments (Terms of Use)
upgrade log (512.66 KB, text/x-log)
2013-07-02 07:20 UTC, Vasilis Keramidas
no flags Details

Description Vasilis Keramidas 2013-07-01 12:10:09 UTC
Description of problem:
During the upgrade from Fedora 18 to Fedora 19, after the reboot the progress bar during the upgrade was stuck at ~10%. Pressing ESC you could see the upgrade is continuing normally. This may be confusing for the average user, since he may think that the upgrade stuck.

Comment 1 Will Woods 2013-07-01 18:48:41 UTC
Could you attach /var/log/upgrade.log, if it's available?

Does the progress meter *ever* move, or does it stay at 10%(ish) until the upgrade finishes?

Comment 2 Vasilis Keramidas 2013-07-02 07:20:15 UTC
Created attachment 767655 [details]
upgrade log

Comment 3 Vasilis Keramidas 2013-07-02 07:22:40 UTC
At the end of the upgrade, the bar suddenly reaches 100% and the upgrade ends

Comment 4 Will Woods 2013-10-09 19:16:24 UTC
Everything looks normal about the log here.

Was the progress meter the text-mode version or the graphical progress bar with the blinking Fedora logo?

Comment 5 Vasilis Keramidas 2013-10-10 06:53:22 UTC
It have been 3 months since this happened, so i can not recall. I am not able to reproduce this since it requires to reinstall F18 and then upgrade to F19. I am pretty happy with my current setup and i do not want to change it. So, fell free to close this bug.


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